WO2017088476A1 - 同步续传方法、从端设备及系统 - Google Patents

同步续传方法、从端设备及系统 Download PDF

Info

Publication number
WO2017088476A1
WO2017088476A1 PCT/CN2016/087914 CN2016087914W WO2017088476A1 WO 2017088476 A1 WO2017088476 A1 WO 2017088476A1 CN 2016087914 W CN2016087914 W CN 2016087914W WO 2017088476 A1 WO2017088476 A1 WO 2017088476A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
snapshot
slave device
slave
time point
Prior art date
Application number
PCT/CN2016/087914
Other languages
English (en)
French (fr)
Inventor
张富恩
代海军
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2017088476A1 publication Critical patent/WO2017088476A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1458—Management of the backup or restore process
    • G06F11/1464—Management of the backup or restore process for networked environments

Definitions

  • the present invention relates to the field of storage technologies, and in particular, to a synchronous resume transmission method, a slave device, and a system.
  • Figure 1 is a block diagram of the existing synchronous resume process.
  • the data of the primary end needs to be backed up to the secondary end to create a remote replication (English: Pair) configuration.
  • a snapshot will be taken on the primary end (English: Snap) 01, and then the data corresponding to snapshot 01 will be played. Synchronize to the slave at full, get the data (English: Data) 01', and then take snapshot 01' at the slave.
  • the pair will take snapshot 02 on the primary end, and then synchronize the data corresponding to the snapshot 02 to the secondary end to obtain the data 02'.
  • you will split the Pair configuration by user command, cancel the setting of the slave write protection, and then trigger the data rollback from the slave to the previous consistency point snapshot, which does not require master-slave switching.
  • the slave write protection is set again, which again triggers the data rollback from the end to the previous consistency point snapshot 01'.
  • the data in the process of split incremental synchronization to split split configuration will be overwritten by the snapshot data.
  • the data corresponding to snapshot 02 needs to be synchronized from 0 to 100% increments to the slave. This will result in an extended time for the entire synchronization, which reduces the efficiency of synchronous retransmission.
  • the embodiment of the present invention provides a synchronous retransmission method, a slave device, and a system, so as to at least solve the problem that the existing synchronized data is overwritten after the snapshot is rolled back, thereby causing the entire synchronization time to be extended.
  • the embodiment of the present invention provides the following technical solutions:
  • a synchronous resume transmission method comprising:
  • the slave The device records the split data of the synchronized time point at a preset time point, where the split data is data after the slave device synchronizes the data of the incremental synchronization to the fourth snapshot;
  • the slave device rolls back the data of the second snapshot and the split data
  • the slave device obtains the remaining data of the data that the master device synchronizes to the slave device when the data of the third snapshot is incrementally synchronized to the slave device.
  • the synchronized data will be overwritten after the snapshot is rolled back, resulting in an extended synchronization time.
  • the synchronous resume transmission when the synchronous resume transmission is performed, only the portion of the data that is not incrementally synchronized can be synchronized according to the data amount of the last incremental synchronization, thereby reducing the entire synchronization time and improving the efficiency of the synchronous resume transmission.
  • a slave device in a second aspect, includes:
  • An obtaining unit configured to acquire data that the primary device synchronizes the data of the first snapshot to the second device after the slave device synchronizes the full amount of data to the slave device;
  • a recording unit configured to: when the primary device synchronizes the data of the third snapshot to the slave device, record the split data of the synchronized time point at a preset time point, where the split data is the slave end The device will make the data of the incremental synchronization data after the fourth snapshot;
  • a rollback unit configured to roll back data of the second snapshot and split data when the setting unit sets write protection
  • the acquiring unit is further configured to: when the synchronization device resumes the retransmission, obtain the remaining data except the data of the current incremental synchronization when the primary device synchronizes the data of the third snapshot to the slave device.
  • the slave device provided by the embodiment of the present invention can be used to perform the method of the foregoing first aspect, the technical effects that can be obtained by referring to the technical effect of the synchronous resume transmission method performed by the slave device in the foregoing first aspect, I will not repeat them here.
  • the preset time point includes a time point corresponding to when the slave device determines the split remote replication Pair configuration.
  • the preset time point includes a time point corresponding to a preset timer when the master-slave link is interrupted.
  • the preset time point may be other, which is not specifically limited in the embodiment of the present invention.
  • a slave device including: a processor, a memory, a bus, and a communication interface;
  • the memory is used to store computer execution instructions, the processor and the memory are connected by a bus, and when the slave device is operated, the processor executes the memory storage computer to execute the instructions, so that the slave device performs any of the first aspect or the first aspect as described above.
  • a synchronous resume method as described in an alternative manner.
  • the slave device provided by the embodiment of the present invention can be used to perform the synchronous continuous transmission method described in the foregoing first aspect or any one of the foregoing aspects, the technical effects can be obtained by referring to the foregoing.
  • the technical effects of the synchronous resume transmission method described in the first aspect are not described herein again.
  • a readable medium comprising computer-executable instructions, when the slave computer device executes the computer to execute an instruction, the slave device performs any one of the first aspect or the first aspect as described above The synchronous resume method described in the manner.
  • a synchronous retransmission system includes: a primary end device, and the secondary device as described in the foregoing second aspect or the optional aspect of the second aspect;
  • the synchronous retransmission system includes: a primary device and a secondary device as described in the third aspect above.
  • the synchronous retransmission system provided by the embodiment of the present invention includes the slave device as described in the foregoing second aspect or the second aspect, the slave device may be used to perform the foregoing first aspect or the foregoing
  • the synchronous retransmission method described in any of the alternative manners on the one hand, and therefore, the technical effects that can be obtained can refer to the technical effects of the synchronous retransmission method described in the above first aspect, and details are not described herein again.
  • Figure 1 is a block diagram of an existing synchronous resume process
  • FIG. 2 is a block diagram 1 of a synchronous resume transmission process according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram 1 of a synchronous resume transmission according to an embodiment of the present invention.
  • FIG. 4 is a second block diagram of a synchronous resume transmission process according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram 2 of a synchronous resume transmission according to an embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of a synchronous resume transmission method according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram 1 of a slave device according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram 2 of a slave device according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of a synchronous resume transmission system according to an embodiment of the present invention.
  • Take a snapshot specifically refers to quickly backing up data at a specific point in time.
  • Rollback Specifically, the data of the snapshot is backed up again.
  • Full and incremental synchronization are two ways to synchronize the database. Full-time synchronization synchronizes all data at once; incremental synchronization synchronizes only the difference data of two databases at a time, that is, only synchronizes different parts of the two databases.
  • a component can be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread in execution, a program, and/or a computer.
  • an application running on a computing device and the computing device can be a component.
  • One or more components can reside within a process and/or thread of execution, and a component can be located in a computer and/or distributed between two or more computers.
  • these Components can be executed from a variety of computer readable media having various data structures thereon. These components may be passed, for example, by having one or more data packets (eg, data from one component that interacts with the local system, another component of the distributed system, and/or signaled through, such as the Internet) The network interacts with other systems to communicate in a local and/or remote process.
  • data packets eg, data from one component that interacts with the local system, another component of the distributed system, and/or signaled through, such as the Internet
  • the network interacts with other systems to communicate in a local and/or remote process.
  • the application will present various aspects, embodiments, or features in a system that can include multiple devices, components, modules, and the like. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules, etc. discussed in connection with the figures. In addition, a combination of these schemes can also be used.
  • the word "exemplary” is used to mean an example, an illustration, or a description. Any embodiment or design described as “example” in this application should not be construed as preferred or advantageous over other embodiments or designs. Rather, the term use examples is intended to present concepts in a concrete manner.
  • FIG. 6 is a schematic flowchart of a synchronous resume transmission method according to an embodiment of the present invention, including steps S601-S604:
  • the slave device obtains, by the master device, the data of the first snapshot is synchronized to the slave device, and the data of the second snapshot is performed by the slave device.
  • the slave device When the primary device synchronizes the data of the third snapshot to the slave device, the slave device records the split data of the synchronized time point at the preset time point, where the split data is the slave device.
  • the data of the second incremental synchronization hits the data after the fourth snapshot.
  • the slave device obtains the remaining data except the data of the current incremental synchronization when the master device synchronizes the data of the third snapshot to the slave device.
  • the synchronized data will be overwritten after the snapshot is rolled back, resulting in an extended synchronization time.
  • the synchronous resume transmission method provided by the embodiment of the present invention, it can be seen that In the embodiment of the present invention, when the synchronous resume transmission is performed, only the portion that is not incrementally synchronized may be synchronized according to the data amount of the last incremental synchronization, thereby reducing the entire synchronization time and improving the efficiency of the synchronous resume transmission.
  • the preset time point includes a time point corresponding to when the end device determines the split Pair configuration.
  • the preset time point includes a time point corresponding to a preset timer when the master-slave link is interrupted.
  • FIG. 2 is a flow chart of a synchronous resume transmission method according to an embodiment of the present invention.
  • the data of the primary end needs to be backed up to the secondary end, and the configuration of the Pair is created.
  • the first snapshot is taken on the primary end (recorded as: snapshot 01), and then the data corresponding to the snapshot 01 is fully synchronized. From the end, the data 01' is obtained, and a second snapshot is taken at the slave end (denoted as: snapshot 01').
  • the pair will make a third snapshot on the primary end (recorded as: snapshot 02), and then incrementally synchronize the data portion corresponding to snapshot 02 to the secondary end to obtain data 02'.
  • the master will split the Pair configuration by user command, and then cancel the slave write protection from the end, and the slave will return. Roll the data of snapshot 01' to get data 01'.
  • the split data of the synchronized time point is recorded at the slave end (English: SplitData) (indicated as: split data 02'), and the split data 02' is the fourth snapshot after the data 02' of the incremental synchronization is synchronized from the end. The data.
  • the slave write protection will be set again, so that the data of the snapshot 01' and the split data 02' will be triggered by the slave end, and the data 01' and the data 02' are obtained.
  • the slave will acquire the remaining data of the snapshot 02 from the master to the slave, except for the data 02' (denoted as: data 03'), such as in FIG. Synchronize the remaining data to the slave on the basis of 50% and make a fifth snapshot (recorded as: snapshot 02').
  • the data of the first incremental synchronization 50% is taken as an example.
  • the numerical value is only an exemplary description, and may be any 0% to 100% such as 20% and 30%.
  • the data in the embodiment of the present invention is not specifically limited thereto.
  • the interaction diagram of the synchronous retransmission method provided by the embodiment of the present invention is shown in the following, based on the block diagram of the synchronous retransmission method shown in FIG. 2, and the interaction between the primary device and the secondary device is taken as an example. 3, including steps S301-S313:
  • the master device needs to back up directory A and take snapshot 01.
  • the master device synchronizes the data of the snapshot 01 to the slave device.
  • S304 The primary device synchronizes and transmits snapshot 02.
  • the master device incrementally synchronizes the data portion of the snapshot 02 to the slave device.
  • the primary device splits the Pair configuration by using a user command.
  • the split data 02' is the data after the fourth snapshot of the incrementally synchronized data 02' from the end device.
  • the master device synchronizes and transmits the snapshot 02.
  • the master device synchronizes the remaining data of the data of the snapshot 02 except the data 02' to the slave device.
  • the synchronized data will be overwritten after the snapshot is rolled back, resulting in an extended synchronization time.
  • the split Pair configuration may be determined according to the slave device. The amount of data recorded in the last incremental synchronization is only synchronized with the portion that is not incrementally synchronized, thereby reducing the overall synchronization time and improving the efficiency of synchronous resume transmission.
  • FIG. 4 is a flow chart of another method for synchronous resume transmission according to an embodiment of the present invention.
  • the data of the primary end needs to be backed up to the secondary end, and the configuration of the Pair is created.
  • the first snapshot is taken on the primary end (recorded as: snapshot 01), and then the data corresponding to the snapshot 01 is fully synchronized. From the end, the data 01' is obtained, and a second snapshot is taken at the slave end (denoted as: snapshot 01').
  • the pair will make a third snapshot on the primary end (recorded as: snapshot 02), and then incrementally synchronize the data portion corresponding to snapshot 02 to the secondary end to obtain data 02'.
  • the master-slave link is disconnected, and the slave end cannot sense the master side situation, and the slave end can record after the preset timer expires.
  • the split data 02' of the synchronized time point is synchronized, and the split data 02' is the data after the fourth snapshot is taken from the data 02' of the incremental synchronization.
  • the slave write protection When the slave write protection is canceled, in order to be able to take over the service to the slave in the case of the master-slave link disconnection, the slave will roll back the data of the snapshot 01' to obtain the data 01'.
  • the master may need to continue to synchronize the data to the slave.
  • the slave will set the slave write protection again, which will trigger the slave to roll back the snapshot 01' data and split data again. 02', obtain data 01' and data 02'.
  • the slave acquires the data incremented by the master to snapshot 02 to the remaining data except the data 02' (denoted as: data 03'), such as in FIG. Synchronize the remaining data to the slave on the basis of 50% and make a fifth snapshot (recorded as: snapshot 02').
  • the data of the first incremental synchronization 50% is taken as an example.
  • the numerical value is only an exemplary description, and may be any 0% to 100% such as 20% and 30%.
  • the data in the embodiment of the present invention is not specifically limited thereto.
  • the master device needs to back up directory A and take snapshot 01.
  • the master device synchronizes the data of the snapshot 01 to the slave device.
  • S504 The primary device synchronizes and transmits snapshot 02.
  • the master device incrementally synchronizes the data portion of the snapshot 02 to the slave device.
  • the slave end records the split data 02' of the synchronized time point after the preset timer expires.
  • the split data 02' is the data after the fourth snapshot of the incrementally synchronized data 02' from the end device.
  • the master device synchronizes the transmission, and takes snapshot 02.
  • the master device synchronizes the remaining data of the data of the snapshot 02 except the data 02' to the slave device.
  • the synchronized data will be overwritten after the snapshot is rolled back, resulting in an extended synchronization time.
  • the method according to the embodiment of the present invention can be seen that, in the embodiment of the present invention, after the primary-slave link is disconnected, when the synchronous resume transmission is performed, the preset timer can be recorded according to the time-lapse.
  • the amount of data for the last incremental synchronization only synchronizes the portion of the non-incremental synchronization, which reduces the overall synchronization time and improves the efficiency of synchronous retransmission.
  • the embodiment of the present invention provides a slave device 70 for performing the steps performed by the slave device in the synchronous resume transmission method shown in FIG. 3, FIG. 5, or FIG. 6 above.
  • the slave device 70 may include a unit corresponding to the corresponding step.
  • the method may include:
  • the obtaining unit 701 is configured to acquire data that the master device synchronizes the full amount of data of the first snapshot to the secondary device 70 and then plays the second snapshot from the end device 70.
  • the recording unit 702 is configured to: when the primary device synchronizes the data of the third snapshot to the slave device 70, record the split data of the synchronized time point at a preset time point, where the split data is the slave end.
  • the device 70 takes the data of the current incremental synchronization into the data after the fourth snapshot.
  • the setting unit 703 is configured to set write protection.
  • the rollback unit 704 is configured to roll back data of the second snapshot and split data when the setting unit 703 sets the write protection
  • the obtaining unit 701 is further configured to: when the synchronization is resumed again, the acquiring the master device will make a third snapshot.
  • the data increment is synchronized to the remaining data except the data of the current incremental synchronization when the slave device 70 is used.
  • the preset time point includes a time point corresponding to when the end device 70 determines the split Pair configuration.
  • the preset time point includes a time point corresponding to a preset timer when the master-slave link is interrupted.
  • the obtaining unit 701, the recording unit 702, the setting unit 703, and the rollback unit 704 in this embodiment may be a separately set processor, or may be integrated in a processor of the slave device 70.
  • it may also be stored in the memory of the slave device 70 in the form of program code, and the above-mentioned acquisition unit 701, the recording unit 702, the setting unit 703, and the rollback unit 704 are called by the processor of the slave device 70 and executed. The function.
  • the processor described here can be a central processing unit (English name: central processing unit: English abbreviation: CPU), and can also be other general-purpose processors, digital signal processors (English full name: digital signal processing, English abbreviation: DSP ), ASIC (English full name: application specific integrated circuit, English abbreviation: ASIC), field programmable gate array (English full name: field-programmable gate array, English abbreviation: FPGA) or other programmable logic devices, discrete doors or Transistor logic devices, discrete hardware components, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the processor may also be a dedicated processor, which may include at least one of a baseband processing chip, a radio frequency processing chip, and the like. Further, the dedicated processor may also include a chip with other dedicated processing functions of the slave device 70.
  • the slave device 70 of the embodiment of the present invention may correspond to the slave device in the synchronous continuous transmission method shown in FIG. 3, FIG. 5, or FIG. 6, and the slave device 70 in the embodiment of the present invention.
  • the division and/or function of each unit are used to implement the above-mentioned synchronous retransmission method flow shown in FIG. 3, FIG. 5, or FIG. 6.
  • FIG. 3, FIG. 5, or FIG. 6 For brevity, details are not described herein again.
  • the slave device 70 in the embodiment of the present invention can be used to perform the foregoing method, and therefore, the technical effects that can be obtained are also referred to the foregoing method embodiments, and details are not described herein again.
  • an embodiment of the present invention provides a slave device 80, including: a processor 801, a memory 802, a bus 803, and a communication interface 804.
  • the memory 802 is used to store computer execution instructions
  • the processor 801 is connected to the memory 802 via the bus 803, and when the slave device 80 is running, the processor 801 executes the computer execution instructions stored in the memory 802 to cause the slave device 80 to execute as shown in FIG.
  • FIG. 5 or FIG. 6 For a specific synchronous retransmission method, refer to the related description in the foregoing embodiment shown in FIG. 3, FIG. 5, or FIG. 6, and details are not described herein again.
  • the processor 801 in the embodiment of the present invention may be a CPU, or other general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or the like.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the processor 801 can also be a dedicated processor, which can include at least one of a baseband processing chip, a radio frequency processing chip, and the like. Further, the dedicated processor may also include a chip having other dedicated processing functions of the slave device 80.
  • the memory 802 may include a volatile memory (English: volatile memory), such as a random access memory (English name: random-access memory, English abbreviation: RAM); the memory 802 may also include a non-volatile memory (English: non- Volatile memory), such as read-only memory (English full name: read-only memory, English abbreviation: ROM), flash memory (English: flash memory), hard disk (English full name: hard disk drive, English abbreviation: HDD) or solid state drive (English full name: solid-state drive, English abbreviation: SSD); in addition, the memory 802 may also include a combination of the above types of memory.
  • a volatile memory such as a random access memory (English name: random-access memory, English abbreviation: RAM)
  • the memory 802 may also include a non-volatile memory (English: non- Volatile memory), such as read-only memory (English full name: read-only memory, English abbreviation: ROM), flash memory (English: flash memory), hard disk (English
  • the bus 803 can include a data bus, a power bus, a control bus, and a signal status bus. For the sake of clarity in the present embodiment, various buses are illustrated as a bus 803 in FIG.
  • Communication interface 804 may specifically be a transceiver on slave device 80.
  • the transceiver can be a wireless transceiver.
  • the wireless transceiver can be an antenna of the slave device 80 or the like.
  • the processor 801 performs data transmission and reception with other devices, such as the master device, through the communication interface 804.
  • each step in the method flow shown in FIG. 3, FIG. 5, or FIG. 6 can be implemented by the processor 801 in hardware form executing a computer-executed instruction in the form of software stored in the memory 802. To avoid repetition, we will not repeat them here.
  • slave device 80 provided by the embodiment of the present invention can be used to perform the foregoing method, the technical effects can be obtained by referring to the foregoing method embodiments, and details are not described herein again.
  • the embodiment of the present invention further provides a readable medium, including a computer execution instruction,
  • the computer executes the instruction from the processor of the end device
  • the slave device can perform the synchronous resume transmission method as shown in FIG. 3, FIG. 5, or FIG.
  • FIG. 3, FIG. 5, or FIG. 5 For a specific synchronous retransmission method, refer to the related description in the foregoing embodiment shown in FIG. 3, FIG. 5, or FIG. 6, and details are not described herein again.
  • the embodiment of the present invention further provides a synchronous retransmission system 90.
  • the synchronous retransmission system 90 includes: a primary device 901 and a secondary device 902 that can communicate with the primary device 901.
  • the primary device 901 can be the primary device in FIG. 3 or FIG. 5;
  • the secondary device 902 can be the secondary device in FIG. 3 or 5.
  • the primary device 901 refer to the related description of the primary device in the embodiment shown in FIG. 3 or FIG. 5; for the description of the secondary device 902, refer to FIG. 3 or FIG. 5 above.
  • the related description of the slave device in the embodiment is not described herein again.
  • the primary end device 901 performs the synchronous continuous transmission method of the embodiment of the present invention by performing corresponding steps in the method flow shown in FIG. 3 or FIG. 5; correspondingly, the secondary end device The device 902 performs the synchronous resume transmission method of the embodiment of the present invention by performing corresponding steps in the method flow as shown in FIG. 3 or FIG. 5.
  • the master device 901 and the slave device 902 in the synchronous retransmission system 90 provided by the embodiment of the present invention can be used to execute the method flow shown in FIG. 3 or FIG. 5, the technical effects that can be obtained can be referred to the foregoing method. The description in the embodiments is not described herein again.
  • the above described device is only illustrated by the division of the above functional modules. In practical applications, the above functions may be assigned differently according to needs.
  • the function module is completed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • the device and the unit described above refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the modules or units is only a logical function division.
  • there may be another division manner for example, multiple units or components may be used. Combinations can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit if implemented in the form of a software functional unit and sold or used as a standalone product, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential or contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product stored in a storage medium.
  • a number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) or a processor to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, and the like, which can store a program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Telephonic Communication Services (AREA)
  • Retry When Errors Occur (AREA)

Abstract

一种同步续传方法、从端设备及系统，适用于存储技术领域，以至少解决现有的同步续传在快照回滚后已同步数据将被覆盖，从而导致整个同步时间延长的问题。该方法包括：从端设备获取主端设备将打第一快照的数据全量同步至从端设备后从端设备打第二快照的数据（S601）；在主端设备将打第三快照的数据增量同步至从端设备时，从端设备在预设时间点记录已同步时间点的分裂数据，其中，分裂数据为从端设备将本次增量同步的数据打第四快照后的数据（S602）；在从端设备设置写保护时，从端设备回滚打第二快照的数据和分裂数据（S603）；再次同步续传时，从端设备获取主端设备将打第三快照的数据增量同步至从端设备时除所述本次增量同步的数据之外的剩余数据（S604）。

Description

同步续传方法、从端设备及系统 技术领域
本发明涉及存储技术领域，尤其涉及同步续传方法、从端设备及系统。
背景技术
图1为现有的同步续传流程框图。如图1所示，主端的数据需要备份到从端，创建远程复制(英文：Pair)配置，启动同步时，将在主端打快照(英文：Snap)01，然后将打快照01对应的数据全量同步至从端，得到数据(英文：Data)01’，进而在从端打快照01’。
Pair配置在增量同步过程中，将在主端打快照02，然后将打快照02对应的数据增量同步至从端，得到数据02’。当希望切换主从端业务时，将通过用户命令分裂Pair配置，取消设置从端写保护，进而触发从端回滚到前一个一致性点快照的数据01’，在不需要主从切换而希望继续同步的情况下，将再次设置从端写保护，从而再次触发从端回滚到前一个一致性点快照的数据01’。然而，快照回滚后，pair增量同步开始到分裂Pair配置过程中的数据将被快照数据覆盖，再次启动同步时，打快照02对应的数据需从0至100％增量同步至从端，这将导致整个同步的时间延长，从而降低了同步续传的效率。
发明内容
本发明实施例提供同步续传方法、从端设备及系统，以至少解决现有的同步续传在快照回滚后已同步数据将被覆盖，从而导致整个同步时间延长的问题。
为达到上述目的，本发明实施例提供如下技术方案：
第一方面，提供一种同步续传方法，该方法包括：
从端设备获取主端设备将打第一快照的数据全量同步至该从端设备后该从端设备打第二快照的数据；
在该主端设备将打第三快照的数据增量同步至该从端设备时，该从端 设备在预设时间点记录已同步时间点的分裂数据，其中，该分裂数据为该从端设备将本次增量同步的数据打第四快照后的数据；
在该从端设备设置写保护时，该从端设备回滚打第二快照的数据和分裂数据；
再次同步续传时，该从端设备获取该主端设备将打第三快照的数据增量同步至该从端设备时除该本次增量同步的数据之外的剩余数据。
不会像现有技术一样，在快照回滚后已同步数据将被覆盖，从而导致整个同步时间延长。通过上述方法，在进行同步续传时，可以根据上次增量同步的数据量仅同步未增量同步的部分，从而减少了整个同步时间，提高了同步续传的效率。
第二方面，提供一种从端设备，其特征在于，该从端设备包括：
获取单元，用于获取主端设备将打第一快照的数据全量同步至该从端设备后该从端设备打第二快照的数据；
记录单元，用于在该主端设备将打第三快照的数据增量同步至该从端设备时，在预设时间点记录已同步时间点的分裂数据，其中，该分裂数据为该从端设备将本次增量同步的数据打第四快照后的数据；
设置单元，用于设置写保护；
回滚单元，用于在设置单元设置写保护时，回滚打第二快照的数据和分裂数据；
获取单元，还用于再次同步续传时，获取该主端设备将打第三快照的数据增量同步至该从端设备时除该本次增量同步的数据之外的剩余数据。
由于本发明实施例提供的从端设备可以用于执行上述第一方面的方法，因此，其所能获得的技术效果可以参考上述第一方面中从端设备执行的同步续传方法的技术效果，此处不再赘述。
可选的，在上述第一方面或第二方面中，一种可能的实现方式中，所述预设时间点包括所述从端设备确定分裂远程复制Pair配置时对应的时间点。
可选的，在上述第一方面或第二方面中，另一种可能的实现方式中，所述预设时间点包括主从端链路中断后预设定时器到时对应的时间点。
需要说明的是，上述仅是示例性的提供两种可能的预设时间点的实 现，当然，本发明实施例中，预设时间点还可能为其它，本发明实施例对此不作具体限定。
第三方面，提供一种从端设备，该从端设备包括：处理器、存储器、总线和通信接口；
存储器用于存储计算机执行指令，处理器与存储器通过总线连接，当从端设备运行时，处理器执行存储器存储的计算机执行指令，以使从端设备执行如上述第一方面或者第一方面的任意一种可选方式中所述的同步续传方法。
由于本发明实施例提供的从端设备可以用于执行上述第一方面或者第一方面的任意一种可选方式中所述的同步续传方法，因此，其所能获得的技术效果可以参考上述第一方面所述的同步续传方法的技术效果，此处不再赘述。
第四方面，提供一种可读介质，包括计算机执行指令，当从端设备的处理器执行该计算机执行指令时，该从端设备执行如上述第一方面或者第一方面的任意一种可选方式中所述的同步续传方法。
第五方面，提供一种同步续传系统，该同步续传系统包括：主端设备和如上述第二方面或者第二方面的任意一种可选方式中所述的从端设备；
或者，该同步续传系统包括：主端设备和如上述第三方面所述的从端设备。
由于本发明实施例提供的同步续传系统包括如上述第二方面或者第二方面的任意一种可选方式中所述的从端设备，该从端设备可以用于执行上述第一方面或者第一方面的任意一种可选方式中所述的同步续传方法，因此，其所能获得的技术效果可以参考上述第一方面所述的同步续传方法的技术效果，此处不再赘述。
其中，本发明的这些方面或其他方面在以下实施例的描述中会更加简明易懂。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地， 下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为现有的同步续传流程框图；
图2为本发明实施例提供的同步续传流程框图一；
图3为本发明实施例提供的同步续传交互示意图一；
图4为本发明实施例提供的同步续传流程框图二；
图5为本发明实施例提供的同步续传交互示意图二；
图6为本发明实施例提供的同步续传方法流程示意图；
图7为本发明实施例提供的从端设备的结构示意图一；
图8为本发明实施例提供的从端设备的结构示意图二；
图9为本发明实施例提供的同步续传系统结构示意图。
具体实施方式
为了下述各实施例的描述清楚简洁，首先给出相关概念的简要介绍：
打快照：具体是指快速备份一份特定时间点的数据。
打基准快照：具体是指第一次打快照。
回滚：具体是指将打快照的数据重新备份回来。
全量同步与增量同步：全量同步与增量同步是数据库同步的两种方式。全量同步一次性同步全部数据；增量同步一次只同步两个数据库的差异数据，也就是只同步两个数据库中不同的部分。
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述。
如本申请所使用的，术语“组件”、“模块”、“系统”等等旨在指代计算机相关实体，该计算机相关实体可以是硬件、固件、硬件和软件的结合、软件或者运行中的软件。例如，组件可以是，但不限于是：在处理器上运行的处理、处理器、对象、可执行文件、执行中的线程、程序和/或计算机。作为示例，在计算设备上运行的应用和该计算设备都可以是组件。一个或多个组件可以存在于执行中的过程和/或线程中，并且组件可以位于一个计算机中以及/或者分布在两个或更多个计算机之间。此外，这些 组件能够从在其上具有各种数据结构的各种计算机可读介质中执行。这些组件可以通过诸如根据具有一个或多个数据分组(例如，来自一个组件的数据，该组件与本地系统、分布式系统中的另一个组件进行交互和/或以信号的方式通过诸如互联网之类的网络与其它系统进行交互)的信号，以本地和/或远程过程的方式进行通信。
本申请将围绕可包括多个设备、组件、模块等的系统来呈现各个方面、实施例或特征。应当理解和明白的是，各个系统可以包括另外的设备、组件、模块等，并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外，还可以使用这些方案的组合。
另外，在本发明实施例中，“示例的”一词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本发明实施例描述的场景是为了更加清楚的说明本发明实施例的技术方案，并不构成对于本发明实施例提供的技术方案的限定，本领域普通技术人员可知，随着新场景的出现，本发明实施例提供的技术方案对于类似的技术问题，同样适用。
图6为本发明实施例提供的一种同步续传方法流程示意图，包括步骤S601-S604：
S601、从端设备获取主端设备将打第一快照的数据全量同步至从端设备后从端设备打第二快照的数据。
S602、在主端设备将打第三快照的数据增量同步至从端设备时，从端设备在预设时间点记录已同步时间点的分裂数据，其中，该分裂数据为从端设备将本次增量同步的数据打第四快照后的数据。
S603、在从端设备设置写保护时，从端设备回滚打第二快照的数据和分裂数据。
S604、再次同步续传时，从端设备获取主端设备将打第三快照的数据增量同步至从端设备时除所述本次增量同步的数据之外的剩余数据。
不会像现有技术一样，在快照回滚后已同步数据将被覆盖，从而导致整个同步时间延长。基于本发明实施例提供的同步续传方法，可以看出， 本发明实施例中，在进行同步续传时，可以根据上次增量同步的数据量仅同步未增量同步的部分，从而减少了整个同步时间，提高了同步续传的效率。
其中，本发明实施例步骤S602中：
一种可能的实现方式中，所述预设时间点包括从端设备确定分裂Pair配置时对应的时间点。
另一种可能的实现方式中，所述预设时间点包括主从端链路中断后预设定时器到时对应的时间点。
下面将结合这两种可能的实现方式对应的场景对图6所示的同步续传方法进行展开说明。
场景一：图2为本发明实施例提供的一种同步续传方法的流程框图。如图2所示，主端的数据需要备份到从端，创建Pair配置，启动同步时，将在主端打第一快照(记为：打快照01)，然后将打快照01对应的数据全量同步至从端，得到数据01’，进而在从端打第二快照(记为：打快照01’)。Pair配置在增量同步过程中，将在主端打第三快照(记为：打快照02)，然后将打快照02对应的数据部分增量同步至从端，得到数据02’。
若在打快照02对应的数据部分增量同步至从端的过程中，希望切换主从端业务时，主端将通过用户命令分裂Pair配置，进而从端取消设置从端写保护，从端将回滚打快照01’的数据，得到数据01’。同时在从端记录已同步时间点的分裂数据(英文：SplitData)(记为：分裂数据02’)，该分裂数据02’为从端将本次增量同步的数据02’打第四快照后的数据。
在不需要主从切换而希望继续同步的情况下，将再次设置从端写保护，从而将触发从端回滚打快照01’的数据和分裂数据02’，获得数据01’和数据02’。当再次启动同步续传时，从端将获取主端将打快照02的数据增量同步至从端时除数据02’之外的剩余数据(记为：数据03’)，比如图2中在50％的基础上将剩余数据同步到从端，并打第五快照(记为：打快照02’)。
需要说明的是，图2中以第一次增量同步50％的数据为例进行说明，当然，该数值仅是示例性说明，也可以是20％、30％等任意0％到100％之间的数据，本发明实施例对此不作具体限定。
下面将基于图2所示的同步续传方法的流程框图，给出本发明实施例提供的同步续传的方法的交互示意图，以主端设备与从端设备的交互为例进行说明，如图3所示，包括步骤S301-S313：
S301、主端设备需要备份目录A，打快照01。
S302、主端设备将打快照01的数据全量同步至从端设备。
S303、从端设备获得数据01’，打快照01’。
S304、主端设备同步续传，打快照02。
S305、主端设备将打快照02的数据部分增量同步至从端设备。
S306、从端设备获取部分增量同步的数据02’。
S307、主端设备通过用户命令分裂Pair配置。
S308、从端设备确定分裂Pair配置后，记录已同步时间点的分裂数据02’。
其中，分裂数据02’为从端设备将本次增量同步的数据02’打第四快照后的数据。
S309、取消设置写保护时，从端设备回滚打快照01’的数据，获得数据01’。
S310、不需要进行主从切换时，从端设备设置从端写保护时，回滚打快照01’的数据和分裂数据02’，获得数据01’和数据02’。
S311、主端设备同步续传，打快照02。
S312、主端设备将打快照02的数据中除数据02’之外的剩余数据增量同步至从端设备。
S313、从端设备获取增量同步的数据03’，并打快照02’。
至此，整个同步续传过程结束。
不会像现有技术一样，在快照回滚后已同步数据将被覆盖，从而导致整个同步时间延长。基于本发明实施例提供的同步续传方法，可以看出，本发明实施例中，在主端设备通过用户命令分裂Pair配置之后，在进行同步续传时，可以根据从端设备确定分裂Pair配置时记录的上次增量同步的数据量仅同步未增量同步的部分，从而减少了整个同步时间，提高了同步续传的效率。
场景二：图4为本发明实施例提供的另一种同步续传方法的流程框图。 如图4所示，主端的数据需要备份到从端，创建Pair配置，启动同步时，将在主端打第一快照(记为：打快照01)，然后将打快照01对应的数据全量同步至从端，得到数据01’，进而在从端打第二快照(记为：打快照01’)。Pair配置在增量同步过程中，将在主端打第三快照(记为：打快照02)，然后将打快照02对应的数据部分增量同步至从端，得到数据02’。
若在打快照02对应的数据部分增量同步至从端的过程中，主从端链路断开，此时从端将无法感知到主端情况，从端可以在预设定时器到时后记录已同步时间点的分裂数据02’，该分裂数据02’为从端将本次增量同步的数据02’打第四快照后的数据。
当取消设置从端写保护时，为了能在主从端链路断开情况向从端接管业务，从端将回滚打快照01’的数据，得到数据01’。
此时若主从端链路恢复，主端可能需要继续将数据同步到从端，此时从端将再次设置从端写保护，从而再次触发从端回滚打快照01’的数据和分裂数据02’，获得数据01’和数据02’。当再次启动同步续传时，从端将获取主端将打快照02的数据增量同步至从端时除数据02’之外的剩余数据(记为：数据03’)，比如图4中在50％的基础上将剩余数据同步到从端，并打第五快照(记为：打快照02’)。
需要说明的是，图4中以第一次增量同步50％的数据为例进行说明，当然，该数值仅是示例性说明，也可以是20％、30％等任意0％到100％之间的数据，本发明实施例对此不作具体限定。
下面将基于图4所示的同步续传方法的流程框图，给出本发明实施例提供的同步续传的方法的交互示意图，以主端设备与从端设备的交互为例进行说明，如图5所示，包括步骤S501-S514：
S501、主端设备需要备份目录A，打快照01。
S502、主端设备将打快照01的数据全量同步至从端设备。
S503、从端设备获得数据01’，打快照01’。
S504、主端设备同步续传，打快照02。
S505、主端设备将打快照02的数据部分增量同步至从端设备。
S506、从端设备获取部分增量同步的数据02’。
S507、主从端链路断开。
S508、从端在预设定时器到时后记录已同步时间点的分裂数据02’。
其中，分裂数据02’为从端设备将本次增量同步的数据02’打第四快照后的数据。
S509、取消设置写保护时，从端设备回滚打快照01’的数据，获得数据01’。
S510、主从链路恢复。
S511、从端设备设置从端写保护时，回滚打快照01’的数据和分裂数据02’，获得数据01’和数据02’。
S512、主端设备同步续传，打快照02。
S513、主端设备将打快照02的数据中除数据02’之外的剩余数据增量同步至从端设备。
S514、从端设备获取增量同步的数据03’，并打快照02’。
至此，整个同步续传过程结束。
不会像现有技术一样，在快照回滚后已同步数据将被覆盖，从而导致整个同步时间延长。基于本发明实施例提供的同步续传方法，可以看出，本发明实施例中，在主从端链路断开后，在进行同步续传时，可以根据预设定时器到时后记录的上次增量同步的数据量仅同步未增量同步的部分，从而减少了整个同步时间，提高了同步续传的效率。
如图7所示，本发明实施例提供一种从端设备70，用于执行以上图3、图5、或图6所示的同步续传方法中从端设备所执行的步骤。该从端设备70可以包括相应步骤所对应的单元，示例的，可以包括：
获取单元701，用于获取主端设备将打第一快照的数据全量同步至从端设备70后从端设备70打第二快照的数据。
记录单元702，用于在主端设备将打第三快照的数据增量同步至从端设备70时，在预设时间点记录已同步时间点的分裂数据，其中，所述分裂数据为从端设备70将本次增量同步的数据打第四快照后的数据。
设置单元703，用于设置写保护。
回滚单元704，用于在设置单元703设置写保护时，回滚打第二快照的数据和分裂数据；
获取单元701，还用于再次同步续传时，获取主端设备将打第三快照 的数据增量同步至从端设备70时除该本次增量同步的数据之外的剩余数据。
可选的，一种可能的实现方式中，所述预设时间点包括从端设备70确定分裂Pair配置时对应的时间点。
可选的，另一种可能的实现方式中，所述预设时间点包括主从端链路中断后预设定时器到时对应的时间点。
需要说明的是，本实施例中的获取单元701、记录单元702、设置单元703以及回滚单元704具体可以为单独设立的处理器，也可以集成在从端设备70的某一个处理器中实现，此外，也可以以程序代码的形式存储于从端设备70的存储器中，由从端设备70的某一个处理器调用并执行以上获取单元701、记录单元702、设置单元703以及回滚单元704的功能。这里所述的处理器可以是一个中央处理器(英文全称：central processing unit，英文缩写：CPU)，还可以为其他通用处理器、数字信号处理器(英文全称：digital signal processing，英文缩写：DSP)、专用集成电路(英文全称：application specific integrated circuit，英文缩写：ASIC)、现场可编程门阵列(英文全称：field-programmable gate array，英文缩写：FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。另外，该处理器还可以为专用处理器，该专用处理器可以包括基带处理芯片、射频处理芯片等中的至少一个。进一步地，该专用处理器还可以包括具有从端设备70其他专用处理功能的芯片。
可以理解，本发明实施例的从端设备70可对应于上述图3、图5、或图6所示的同步续传方法中的从端设备，并且本发明实施例的从端设备70中的各个单元的划分和/或功能等均是为了实现上述图3、图5、或图6所示的同步续传方法流程，为了简洁，在此不再赘述。
由于本发明实施例中的从端设备70可以用于执行上述方法流程，因此，其所能获得的技术效果也可参考上述方法实施例，本发明实施例在此不再赘述。
如图8所示，本发明实施例提供一种从端设备80，包括：处理器801、存储器802、总线803和通信接口804。
存储器802用于存储计算机执行指令，处理器801与存储器802通过总线803连接，当从端设备80运行时，处理器801执行存储器802存储的计算机执行指令，以使从端设备80执行如图3、图5、或图6所示的同步续传方法。具体的同步续传方法可参见上述如图3、图5、或图6所示的实施例中的相关描述，此处不再赘述。
其中，本发明实施例中的处理器801可以为CPU，或者其他通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
处理器801还可以为专用处理器，该专用处理器可以包括基带处理芯片、射频处理芯片等中的至少一个。进一步地，该专用处理器还可以包括具有从端设备80其他专用处理功能的芯片。
存储器802可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文全称：random-access memory，英文缩写：RAM)；存储器802也可以包括非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文全称：read-only memory，英文缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文全称：hard disk drive，英文缩写：HDD)或固态硬盘(英文全称：solid-state drive，英文缩写：SSD)；另外，存储器802还可以包括上述种类的存储器的组合。
总线803可以包括数据总线、电源总线、控制总线和信号状态总线等。本实施例中为了清楚说明，在图8中将各种总线都示意为总线803。
通信接口804具体可以是从端设备80上的收发器。该收发器可以为无线收发器。例如，无线收发器可以是从端设备80的天线等。处理器801通过通信接口804与其他设备，例如主端设备之间进行数据的收发。
在具体实现过程中，上述如图3、图5、或图6所示的方法流程中的各步骤均可以通过硬件形式的处理器801执行存储器802中存储的软件形式的计算机执行指令实现。为避免重复，此处不再赘述。
由于本发明实施例提供的从端设备80可用于执行上述方法流程，因此其所能获得的技术效果可参考上述方法实施例，此处不再赘述。
可选的，本发明实施例还提供一种可读介质，包括计算机执行指令， 当从端设备的处理器执行该计算机执行指令时，该从端设备可以执行如图3、图5、或图6所示的同步续传方法。具体的同步续传方法可参见上述如图3、图5、或图6所示的实施例中的相关描述，此处不再赘述。
本发明实施例还提供一种同步续传系统90，如图9所示，该同步续传系统90包括：主端设备901和与主端设备901可以相互通信的从端设备902。该主端设备901可以为图3或图5中的主端设备；该从端设备902可以为图3或图5中的从端设备。其中，对于主端设备901的描述具体可参考上述图3或图5所示的实施例中对主端设备的相关描述；对于从端设备902的描述具体可参考上述图3或图5所示的实施例中对从端设备的相关描述，此处不再赘述。
本发明实施例提供的同步续传系统90中，主端设备901通过执行如图3或图5所示的方法流程中的相应步骤完成本发明实施例的同步续传方法；相应的，从端设备902通过执行如图3或图5所示的方法流程中的相应步骤完成本发明实施例的同步续传方法。
由于本发明实施例提供的同步续传系统90中的主端设备901和从端设备902可用于执行如图3或图5所示的方法流程，因此其所能获得的技术效果可参考上述方法实施例中的描述，本发明实施例在此不再赘述。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的装置，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述模块或单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本发明各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本发明揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本发明的保护范围之内。因此，本发明的保护范围应以所述权利要求的保护范围为准。

Claims (9)

  1. 一种同步续传方法，其特征在于，所述方法包括：
    从端设备获取主端设备将打第一快照的数据全量同步至所述从端设备后所述从端设备打第二快照的数据；
    在所述主端设备将打第三快照的数据增量同步至所述从端设备时，所述从端设备在预设时间点记录已同步时间点的分裂数据，其中，所述分裂数据为所述从端设备将本次增量同步的数据打第四快照后的数据；
    在所述从端设备设置写保护时，所述从端设备回滚所述打第二快照的数据和所述分裂数据；
    再次同步续传时，所述从端设备获取所述主端设备将所述打第三快照的数据增量同步至所述从端设备时除所述本次增量同步的数据之外的剩余数据。
  2. 根据权利要求1所述的方法，其特征在于，所述预设时间点包括所述从端设备确定分裂远程复制Pair配置时对应的时间点。
  3. 根据权利要求1所述的方法，其特征在于，所述预设时间点包括主从端链路中断后预设定时器到时对应的时间点。
  4. 一种从端设备，其特征在于，所述从端设备包括：
    获取单元，用于获取主端设备将打第一快照的数据全量同步至所述从端设备后所述从端设备打第二快照的数据；
    记录单元，用于在所述主端设备将打第三快照的数据增量同步至所述从端设备时，在预设时间点记录已同步时间点的分裂数据，其中，所述分裂数据为所述从端设备将本次增量同步的数据打第四快照后的数据；
    设置单元，用于设置写保护；
    回滚单元，用于在所述设置单元设置写保护时，回滚所述打第二快照的数据和所述分裂数据；
    所述获取单元，还用于再次同步续传时，获取所述主端设备将所述打第三快照的数据增量同步至所述从端设备时除所述本次增量同步的数据之外的剩余数据。
  5. 根据权利要求4所述的从端设备，其特征在于，所述预设时间点包括所述从端设备确定分裂远程复制Pair配置时对应的时间点。
  6. 根据权利要求4所述的从端设备，其特征在于，所述预设时间点包括主从端链路中断后预设定时器到时对应的时间点。
  7. 一种从端设备，其特征在于，所述从端设备包括：处理器、存储器、总线和通信接口；
    所述存储器用于存储计算机执行指令，所述处理器与所述存储器通过所述总线连接，当所述从端设备运行时，所述处理器执行所述存储器存储的所述计算机执行指令，以使所述从端设备执行如权利要求1-3任一项所述的同步续传方法。
  8. 一种可读介质，包括计算机执行指令，当从端设备的处理器执行该计算机执行指令时，所述从端设备执行如权利要求1-3任一项所述的同步续传方法。
  9. 一种同步续传系统，其特征在于，所述同步续传系统包括：主端设备和如权利要求4-6任一项所述的从端设备；或者，
    所述同步续传系统包括：主端设备和如权利要求7所述的从端设备。
PCT/CN2016/087914 2015-11-27 2016-06-30 同步续传方法、从端设备及系统 WO2017088476A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510849526.1 2015-11-27
CN201510849526.1A CN106815091B (zh) 2015-11-27 2015-11-27 同步续传方法、从端设备及系统

Publications (1)

Publication Number Publication Date
WO2017088476A1 true WO2017088476A1 (zh) 2017-06-01

Family

ID=58762960

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/087914 WO2017088476A1 (zh) 2015-11-27 2016-06-30 同步续传方法、从端设备及系统

Country Status (2)

Country Link
CN (1) CN106815091B (zh)
WO (1) WO2017088476A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108322533A (zh) * 2018-01-31 2018-07-24 广州鼎甲计算机科技有限公司 基于操作日志的分布式集群节点间配置同步方法
CN111625605A (zh) * 2020-06-02 2020-09-04 北京金堤科技有限公司 信息同步方法和装置、以及存储介质和电子设备
CN112272196A (zh) * 2020-03-09 2021-01-26 上海曼恒数字技术股份有限公司 一种系统去服务器方法及系统
CN117596256A (zh) * 2024-01-19 2024-02-23 济南浪潮数据技术有限公司 数据同步方法、装置、系统、电子设备及可读存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111209343B (zh) * 2020-01-22 2022-02-22 腾讯科技（深圳）有限公司 节点数据同步方法、装置、设备以及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7330997B1 (en) * 2004-06-03 2008-02-12 Gary Odom Selective reciprocal backup
CN101419564A (zh) * 2008-12-11 2009-04-29 杭州华三通信技术有限公司 一种采用快照恢复数据的方法和装置
CN102801754A (zh) * 2011-05-24 2012-11-28 英业达集团(天津)电子技术有限公司 一种断点续传的方法及系统
CN103645967A (zh) * 2013-11-26 2014-03-19 华为技术有限公司 一种只读快照回滚方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6728736B2 (en) * 2001-03-14 2004-04-27 Storage Technology Corporation System and method for synchronizing a data copy using an accumulation remote copy trio
GB2411030B (en) * 2002-11-20 2006-03-22 Filesx Ltd Fast backup storage and fast recovery of data (FBSRD)
CN100456255C (zh) * 2007-04-29 2009-01-28 华为技术有限公司 一种取快照数据的装置及方法
CN102999400A (zh) * 2012-11-22 2013-03-27 中国电信股份有限公司云计算分公司 一种云存储系统数据备份方法及装置
CN104484242B (zh) * 2014-12-10 2018-06-22 上海爱数信息技术股份有限公司 一种写时拷贝快照备份过程中可断点传输的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7330997B1 (en) * 2004-06-03 2008-02-12 Gary Odom Selective reciprocal backup
CN101419564A (zh) * 2008-12-11 2009-04-29 杭州华三通信技术有限公司 一种采用快照恢复数据的方法和装置
CN102801754A (zh) * 2011-05-24 2012-11-28 英业达集团(天津)电子技术有限公司 一种断点续传的方法及系统
CN103645967A (zh) * 2013-11-26 2014-03-19 华为技术有限公司 一种只读快照回滚方法及装置

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108322533A (zh) * 2018-01-31 2018-07-24 广州鼎甲计算机科技有限公司 基于操作日志的分布式集群节点间配置同步方法
CN108322533B (zh) * 2018-01-31 2019-02-19 广州鼎甲计算机科技有限公司 基于操作日志的分布式集群节点间配置同步方法
CN112272196A (zh) * 2020-03-09 2021-01-26 上海曼恒数字技术股份有限公司 一种系统去服务器方法及系统
CN111625605A (zh) * 2020-06-02 2020-09-04 北京金堤科技有限公司 信息同步方法和装置、以及存储介质和电子设备
CN111625605B (zh) * 2020-06-02 2024-05-10 北京金堤科技有限公司 信息同步方法和装置、以及存储介质和电子设备
CN117596256A (zh) * 2024-01-19 2024-02-23 济南浪潮数据技术有限公司 数据同步方法、装置、系统、电子设备及可读存储介质
CN117596256B (zh) * 2024-01-19 2024-03-22 济南浪潮数据技术有限公司 数据同步方法、装置、系统、电子设备及可读存储介质

Also Published As

Publication number Publication date
CN106815091B (zh) 2020-02-14
CN106815091A (zh) 2017-06-09

Similar Documents

Publication Publication Date Title
WO2017088476A1 (zh) 同步续传方法、从端设备及系统
CN106610876B (zh) 数据快照的恢复方法及装置
EP3213212B1 (en) Point in time database restore from storage snapshots
US9575849B2 (en) Synchronized backup and recovery of database systems
US10678663B1 (en) Synchronizing storage devices outside of disabled write windows
US11080148B2 (en) Method and system for star replication using multiple replication technologies
US20160147813A1 (en) Distributed transaction commit protocol
US9251230B2 (en) Exchanging locations of an out of synchronization indicator and a change recording indicator via pointers
US20150347250A1 (en) Database management system for providing partial re-synchronization and partial re-synchronization method of using the same
JP6455898B2 (ja) データ複製の方法、一次データストレージコントローラ、装置、システム、及びプログラム
US20120101999A1 (en) Performing a background copy process during a backup operation
US10049020B2 (en) Point in time recovery on a database
US20170168756A1 (en) Storage transactions
JP2012517042A (ja) Ｉ／ｏを中断しないマルチサーバ・アプリケーション同期の方法、プログラム、及び、システム
JP6457633B2 (ja) データベース・クラスタのデータ管理方法、ノード、及びシステム
US10235145B1 (en) Distributed scale-out replication
WO2012050904A2 (en) Host based write ordering for asynchronous replication
US20150378840A1 (en) Ensuring the same completion status for transactions after recovery in a synchronous replication environment
JP2012510094A5 (zh)
CN104182297A (zh) 用于从主存储卷的故障中恢复的方法和系统
US8250036B2 (en) Methods of consistent data protection for multi-server applications
CN103970834A (zh) 一种异构数据库同步系统中增量数据同步故障的恢复方法
CN111984474B (zh) 一种双控集群故障恢复的方法、系统及设备
CN107621994B (zh) 一种数据快照创建的方法及装置
US10860540B1 (en) Method and system for synchronizing backup and cloning schedules

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16867703

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16867703

Country of ref document: EP

Kind code of ref document: A1