WO2018120844A1 - Procédé et dispositif de sauvegarde de données différentielles - Google Patents

Procédé et dispositif de sauvegarde de données différentielles Download PDF

Info

Publication number
WO2018120844A1
WO2018120844A1 PCT/CN2017/096782 CN2017096782W WO2018120844A1 WO 2018120844 A1 WO2018120844 A1 WO 2018120844A1 CN 2017096782 W CN2017096782 W CN 2017096782W WO 2018120844 A1 WO2018120844 A1 WO 2018120844A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
snapshot
numbers
backup
production volume
Prior art date
Application number
PCT/CN2017/096782
Other languages
English (en)
Chinese (zh)
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 WO2018120844A1 publication Critical patent/WO2018120844A1/fr

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
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • 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/1469—Backup restoration techniques

Definitions

  • Embodiments of the present invention relate to the field of storage technologies, and in particular, to a differential data backup method and a differential data backup device.
  • a typical data disaster recovery system includes a production center and a disaster recovery center.
  • hosts and storage arrays are deployed for normal service operations.
  • hosts and storage arrays are deployed to take over the services after a disaster occurs in the production center.
  • the storage array of the production center or the disaster recovery center includes multiple data volumes, and the data volume is a logical storage space mapped by physical storage space. After the data generated by the service of the production center is written to the production array, it can be backed up to the disaster recovery center through the DR link and written to the disaster recovery array. To ensure that the data of the disaster recovery center can support the service takeover after the disaster occurs, the data backed up to the disaster recovery array must ensure consistency.
  • Assuring data consistency essentially means that there is a dependency write request, and the dependency needs to be guaranteed.
  • Applications, operating systems, and databases all rely on this logic of writing data request dependencies to run their services. For example, the write data request 1 is completed first, and the write data request 2 is completed. The order is fixed. That is to say, the system will ensure that the write data request 1 is sent after the write data request 1 is completely returned successfully. Therefore, it is possible to rely on an inherent method to recover the service when a failure causes the execution process to be interrupted. Otherwise, such a situation may occur. For example, when reading data, the data stored in the write data request 2 can be read, but the data stored in the write data request 1 cannot be read, which will cause the service to be unrecoverable.
  • a snapshot is an image of data at a certain point in time (the point in time when the copy begins).
  • the purpose of the snapshot is to create a state view for the data volume at a specific point in time. Only the data volume can be seen at the time of creation. After this time point, the data volume is modified (new data is written). Will not be reflected in the snapshot view. With this snapshot view, you can make a backup of the data.
  • the production center since the snapshot data is “stationary”, the production center can back up the snapshot data to the disaster recovery center after snapshotting the data at each time point, and can complete remote data backup without The effect continues to execute write data requests at the production center.
  • data consistency requirements can also be met. For example, the data of the data request 2 is successfully backed up to the disaster recovery center, and the data of the data request 1 is not successfully backed up. The data of the disaster recovery center can be restored to the previous state by using the snapshot data before the data request 2.
  • the production array needs to hang the write data request before creating the snapshot to prevent the changed data from being recorded in the snapshot, thus causing data and disaster recovery in the production array.
  • the data in the array is inconsistent.
  • hanging write data requests often affects the efficiency of the production array processing data.
  • the present application proposes a differential data backup method and a differential data backup device, which can avoid hanging write data requests and improve data processing efficiency.
  • the first aspect of the present application provides a differential data backup method, which is applied to a storage system.
  • the storage system includes a processor, a production volume, and a target volume.
  • the processor acquires a record of the difference data between the two numbers.
  • the number is used to identify the time period during which data is written to the production volume.
  • the first number of the two numbers is a number assigned to the data received by the production volume last time before the first snapshot of the production volume is created.
  • the second of the two numbers is the number assigned to the data received last time for the production volume after the second snapshot of the production volume was created.
  • the record of the difference data includes a logical place of the difference data received within a time period identified by a number between the two numbers site.
  • the processor reads backup data from the second snapshot according to a logical address of the difference data, the backup data being a subset of the difference data.
  • the processor then sends the backup data to the target volume.
  • the processor acquires a record of the two numbered difference data, and reads the backup data from the second snapshot according to the logical address of the difference data. Since the first number of the two numbers is a number assigned to the data received last time for the production volume before the first snapshot of the production volume is created, and the second number of the two numbers is a creation The number of data that was last received for the production volume after the second snapshot of the production volume, so the difference data is more than the backup data. Then, in the differential backup process provided by the first aspect, there is no need to hang the write data request, and the difference data between the two snapshots can still be backed up to the target volume, thereby ensuring data consistency between the production volume and the target volume. Since there is no need to hang write data requests, the efficiency of data processing can be improved.
  • all numbers between the two numbers are changed according to a set condition including a preset backup period arrival or creation of the production A snapshot of the volume. Thereby, the time period in which the data is written to the production volume by the number is realized.
  • the second snapshot is a next snapshot of the first snapshot. Since the second snapshot is the next snapshot of the first snapshot, it is guaranteed that the data of each backup is slightly more than the difference data between the adjacent two snapshots, and less than the difference data between the two snapshots that are not adjacent. Reduce the amount of data per backup as much as possible.
  • the method further includes the processor transmitting a logical address of the backup data to the target volume .
  • the number between the two numbers does not include the second number. Since the second number is the starting number of the next backup, the second number may not be included in the current backup to reduce the amount of data backed up.
  • the second aspect of the present application provides a differential data backup apparatus for performing a differential data backup method provided by the first method.
  • a third aspect of the present application provides a storage system, including a processor, a production volume, and a target volume, where the processor is configured to perform the differential data backup method provided by the first aspect.
  • a fourth aspect of the present application provides a storage system including a processor, a memory, a production volume, and a target volume, the processor invoking a program in the memory to execute a differential data backup method provided by the first aspect.
  • the present application also provides a computer program product comprising a computer readable storage medium storing program code, the program code comprising instructions executable by the storage system of the third aspect or the fourth aspect, and for performing the above At least one method on the one hand.
  • the above computer program product provided by the application of the present invention can not hang the write data request during the backup process, thereby improving the efficiency of data processing.
  • FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present invention.
  • FIG. 3 is a structural diagram of a storage device according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a differential data backup method according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of changes in numbers during execution of a differential data backup method according to an embodiment of the present invention.
  • FIG. 6 is a structural diagram of a differential data backup apparatus according to an embodiment of the present invention.
  • the embodiment of the invention provides a data backup method and a storage system, which can avoid hanging write data requests, thereby improving the efficiency of data processing.
  • FIG. 1 depicts a composition diagram of a storage system 10 according to an embodiment of the present invention.
  • the storage system 10 shown in FIG. 1 includes one or more hosts 40 and a storage device 20.
  • the host can be a computing device, such as a terminal device such as a server or a desktop computer.
  • the storage device 20 may be a storage device based on data block data, such as a Storage Area Networking (SAN) device, or a storage device including a file system, such as a Network Attached Storage (NAS) device. This embodiment does not limit the type of the storage device.
  • SAN Storage Area Networking
  • NAS Network Attached Storage
  • This embodiment does not limit the type of the storage device.
  • the network file system (NFS)/Common Internet File System (CIFS) protocol or Fibre Channel (Fiber Channel, FC) can be used.
  • the protocol communicates.
  • the storage device 20 includes at least one controller 21 and a plurality of hard disks 22.
  • Controller 21 can include any computing device such as a server, desktop computer, or the like. Inside the controller, an operating system and other applications are installed.
  • the controller 21 can send an input/output (I/O) request to the hard disk 22. For example, a write data request is sent to the hard disk 22 such that the hard disk 22 writes the data to be written carried in the write data request into its storage medium.
  • I/O input/output
  • the hard disk 22 can be a plurality of types of hard disks, such as Solid State Drive (SSD) or Serial Attached SCSI (SAS) or Fibre Channel (FC) hard disk drives (Hard Disk Drive, HDD). ), where SCSI (Small Computer System Interface) is the abbreviation of the minicomputer system interface or Serial Advanced Technology Attachment (SATA) or Near Line (NL) Serial Attached SCSI (Serial Attached SCSI) , SAS) HDD, not limited here.
  • SCSI Small Computer System Interface
  • SATA Serial Advanced Technology Attachment
  • NL Near Line
  • Serial Attached SCSI Serial Attached SCSI
  • SAS Serial Attached SCSI
  • a Logic Unit (LU) is a logical storage space distributed over one or more hard disks 22, such as production volume 23 and target volume 24 shown in FIG.
  • the host 40 can send a write data request to the storage system 10, the write data request carrying data to be written to the storage system 10, the data can be block data or a file.
  • the controller 21 receives the data and then writes it into the logical unit of the storage device 20.
  • data needs to be backed up. For example, the data in the production volume 23 is backed up to the target volume 24. When the data in the production volume 23 is damaged, the data stored in the target volume 24 can be used for recovery.
  • FIG. 2 depicts a composition diagram of another storage system 10 that includes one or more hosts 40, a storage device 20, and a storage device 30.
  • the storage device 30 is similar to the storage device 20 and includes at least one controller 31 and a plurality of hard disks 32.
  • the structure and function of the controller 31 are similar to those of the controller 21 of FIG. 1.
  • the structure and function of the hard disk 32 are similar to those of the hard disk 22 of FIG. 1, and will not be described herein.
  • the difference from the application scenario described in FIG. 1 is that the backup in FIG. 1 refers to a backup in one storage device, and the backup in FIG. 2 refers to a backup between two storage devices.
  • storage device 20 needs to back up data on its production volume to target volume 33 of storage device 30.
  • the controller 21 may use data when backing up data in one LU (referred to as a production volume) to another LU (referred to as a target volume).
  • the method of full backup can also adopt the method of incremental backup.
  • a full backup is a full backup of all the data on the production volume. Incremental backups are backups since the last full backup or Data modified since the incremental backup (whichever is later). Because it is limited to backing up modified data (also known as differential data), this backup is very fast and saves storage space.
  • FIG. 3 depicts a composition diagram of the controller 21 provided by the embodiment of the present invention.
  • the controller 21 includes at least an interface 211, a processor 212, and a memory 213.
  • the interface 211 is configured to communicate with the host 40 or the hard disk 22 or the storage device 30.
  • the processor 212 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention.
  • the processor 212 can be used to process input/output (I/O) requests to the hard disk 22, back up data in the production volume to the target volume, and the like.
  • the controller 21 can implement functions such as IO operation, data backup, and the like.
  • the processor 212 is configured to execute the program 214, and specifically, the related steps in the following method embodiments may be performed.
  • the memory 213 is configured to store the program 214.
  • the memory 213 may include a cache memory, may also include a high speed RAM memory, and may also include a non-volatile memory, such as at least one hard disk memory. It can be understood that the memory 213 can be a random access memory (RAM), a magnetic disk, a hard disk, or a solid state disk (SSD).
  • RAM random access memory
  • SSD solid state disk
  • the memory 213 can also be used to cache data received from the host 40 or data read from the hard disk 22.
  • Program 214 can include an operating system, a file system, and other software modules.
  • FIG. 4 is a flowchart of a data backup method provided by this embodiment, and the steps shown in FIG. 4 are performed by the processor 212 shown in FIG.
  • FIG. 5 which reflects the change of the number in the following backup process.
  • step S101 the storage device 20 receives one or more write data requests.
  • Each write data request includes data to be written (referred to as data) and a logical address of the data to be written.
  • the logical address includes an identifier of a volume, a logical block address (English: logic block address), and a length (English: length).
  • the volume of the volume is used to indicate the volume to be written by the data.
  • the volume to be written by the data is the production volume as an example.
  • the logical block address indicates the location of the data at the volume, the length representing the size of the data.
  • step S102 the storage device 20 allocates a number for each write data request, and the number is used to identify a time period for receiving the write data request.
  • the storage device 20 includes a number table in which a plurality of numbers are included, and each number is sequentially incremented in ascending order. For example, the plurality of numbers are 0, 1, 2, 3, 4, ..., respectively.
  • Write data requests received during a certain period of time are all assigned the same number. Assume that the initial value of the number is the first number 0. When the specific condition is satisfied, the storage device 20 sets the first number to the second number 1, and the second number 1 is the next number of the first number 0. Then the write data request received in the next time period is assigned the second number 1.
  • the storage device 20 maintains a number generator in which the initial value of the number is recorded, assuming that the initial value of the number is the first number 0.
  • the write data request received during a certain period of time is assigned the first number 0.
  • the number initial value in the number generator is subjected to an operation of incrementing by 1, so that the next number of the first number 0 is the second number 1.
  • the write data request received in the next time period is assigned the second number 1.
  • Specific conditions here include the arrival of a preset backup cycle or the creation of a snapshot of the production volume.
  • each write data request is assigned the first number 0 in step S102.
  • the storage device 20 records the correspondence between the first number 0 and the logical address included in each write data request.
  • the storage device 20 receives three write data requests.
  • the data to be written carried by the first write data request is written to the volume A, the logical block address is 00001, the length of the data is 8 bytes, and the second write data request carries the data to be written.
  • the length of the data is 8 bytes.
  • Step S103 when the preset backup period arrives, the storage device 20 performs a data backup operation.
  • the data in the production volume is sent to the target volume through a number of backup cycles, which are preset for a length of time. If it is the first backup cycle, then storage device 20 needs to send all of the data in the production volume to the target volume, a process also referred to as full backup. If it is not the first backup cycle, storage device 20 may send all of the data in the production volume to the target volume, or may only send the difference data to the target volume.
  • the storage device 20 Since the storage device 20 is in the process of transmitting data to the target volume, the storage device 20 also continues to receive the write data request. Therefore, the data in the production volume and the data in the target volume are inconsistent. In order to ensure data consistency between the production volume and the target volume, the storage device 20 uses the number to distinguish the write data request before the backup cycle arrives from the write data request after the backup cycle arrives. Also, the storage device 20 does not directly read data from the production volume and sends it to the target volume, but creates a snapshot of the production volume from which data is read and sent to the target volume.
  • the storage device 20 performs the following operations:
  • the storage device 20 will modify the number again. For example, after creating the first snapshot of the production volume, the second number 1 is modified to a third number 2. Then, for the write data request received before the next modification number (when the next backup period arrives) after the second number is changed to the third number, the third number 2 is assigned. However, after the first snapshot of the production volume is created, the write data request received by the storage device 20 is still assigned the second number 1 during the period before the second number is modified to the third number, and the writes are still performed. The data carried by the data request is not recorded in the first snapshot. Therefore, the first snapshot includes data stored in a logical address corresponding to the first number 0 and data stored in a logical address corresponding to the second second number 1.
  • the storage device 20 reads the first snapshot of the production volume, and sends the data included in the first snapshot and the logical address of the data to the target volume.
  • the backed up data includes data stored in a logical address corresponding to the first number 0 and data stored in a logical address corresponding to a portion of the second number 1.
  • the storage device 20 completes a full backup.
  • the process of incremental backup is described below.
  • step S103 After the second number is changed to the third number, all the write data requests received by the storage device 20 are assigned the third number 2. These write data requests may contain write data requests that modify the data in the production volume. As shown in table 2:
  • storage device 20 receives three write data requests.
  • the data to be written carried by the first write data request is written to volume A, the logical block address is 00001, and the length of the data is 8 bytes. Since the logical block address and length of the data carried by the write data request are the same as the logical block address and length of the data carried by the first write data request shown in Table 1, the write data request carries The data is used to cover the data carried by the first write data request shown in Table 1.
  • the data to be written carried by the second write data request will be written to volume A with a logical block address of 00002 and a length of 8 bytes.
  • the write data request carries The data is used to cover the data carried by the second write data request shown in Table 1.
  • the data to be written carried by the third write data request is newly written data, which will be written to volume A, whose logical block address is 00004, and the length of the data is 8 bytes.
  • step S103 the following steps are further included.
  • Step S104 When the backup period arrives, the storage device 20 modifies the third number to the fourth number. As described earlier, the number assigned to each write data request in step S103 is the third number 2. Then, when the current backup period arrives, the storage device 20 modifies the third number 2 to the fourth number 3, and the fourth number 3 is the number after the third number 2. Then, the write data request received later will be assigned the fourth number 3.
  • Step S105 Create a snapshot of the production volume.
  • the snapshot here is referred to as a second snapshot.
  • the point in time for each snapshot is the data consistency point for the production and target volumes.
  • the data consistency point is the point in time at which the data of the production volume is consistent with the data of the target volume.
  • Step S106 Modify the fourth number to the fifth number.
  • the storage device 20 will modify the number again. For example, the fourth number 3 is modified to the fifth number 4. Then, after the fourth number 3 is changed to the fifth number 4, the write data request received before the next modification number (when the next backup period arrives) is assigned the fifth number 4. However, after the second snapshot of the production volume is created, the write data request received by the storage device 20 is still assigned the fourth number 3 during the period before the fourth number 3 is modified to the fifth number 4. The data carried by these write data requests is not recorded in the second snapshot.
  • the second snapshot includes data stored in a logical address corresponding to the first number 0, data stored in a logical address corresponding to the second number 1, data stored in a logical address corresponding to the third number 2, and a portion fourth.
  • Step S107 Determine the logical address of the difference data after the second number up to and before the fifth number.
  • the difference data includes the difference data received in the time period identified by the second number 1, the difference data received in the time period identified by the third number 2, and the difference data received in the time period identified by the fourth number 3, but The difference data received during the time period identified by the fifth number 4 is not included.
  • the second number is the number assigned last time for the write data request before the first snapshot is created
  • the fifth number is the number assigned last time for the write data request after the second snapshot is created. Therefore, the difference data after the second number until before the fifth number is more than the data after the first snapshot is created until the second snapshot is created.
  • the record of the difference data after the second number up to and before the fifth number is as shown in Table 3.
  • Step S108 Read backup data from the second snapshot according to the logical address of the difference data.
  • the backup data read from the second snapshot may be the difference data or a subset of the difference data. Since only the data stored in the logical address corresponding to the fourth fourth number 3 is recorded in the second snapshot, the storage device 20 may not be able to obtain all the difference data recorded in step S107. For example, assume that within the time period identified by number 3, storage device 20 receives two write data requests. The first write data request is received before the second snapshot is created, and the logical block address of the data carried is 00008 and the length is 4 bytes. The second write data request is received after the second snapshot is created, and the data carried by the logical block address is 00004 and the length is 8 bytes.
  • the storage device 20 can only obtain the data carried by the first write data request from the storage device 20, and the data stored in the second snapshot by the logical address of the second write data request.
  • the second write data request carries 45600000
  • the logical block address is 00004
  • the length is 8 bytes.
  • the data of the logical block address and length in the second snapshot is 12300000. Therefore, storage device 20 still backs up 123000000 to the target volume.
  • Step S109 Send the backup data to the target volume.
  • the storage device 20 may further send the logical address of the backup data to the target volume, such that the location where the backup data is saved in the target volume and the location where the backup data is saved in the production volume Consistent.
  • the storage device 20 completes an incremental backup. Since the storage device 20 records more difference data than the backup data, the storage device 20 does not need to hang the write data request when performing the incremental backup, and can still guarantee Backing up the difference data between the two snapshots to the target volume ensures data consistency between the production volume and the target volume.
  • This embodiment also provides a difference data backup device 66.
  • the device 66 is located in a storage system that includes a production volume and a target volume. As shown in FIG. 6, the device 66 includes a reading module 661 and a transmitting module 662.
  • the reading module 661 is configured to obtain a record of difference data between two numbers, and the number is used to identify a time period in which data is written into the production volume, wherein the first number of the two numbers is to create the The number assigned to the data received by the production volume most recently before the first snapshot of the production volume, the second number of the two numbers being the last time the second volume of the production volume was created to receive the production volume a data allocation number, the record of the difference data including a logical address of the difference data received within the time period identified by the number between the two numbers, all numbers between the two numbers not including the a second number; and reading backup data from the second snapshot based on the logical address of the difference data, the backup data being a subset of the difference data.
  • the reading module 661 can be referred to the description of step S101 to step S108, and details are not described herein again.
  • the reading module 661 may be the processor 212 shown in FIG. 3 calling the program 214 in the memory 213.
  • the processor 212 is a CPU.
  • the reading module 661 can also be implemented independently by the processor 212.
  • the processor 212 is a Field-Programmable Gate Array (FPGA) or other processing chip.
  • FPGA Field-Programmable Gate Array
  • the sending module 662 is configured to send the backup data to the target volume.
  • the sending module 662 may be the processor 212 shown in FIG. 3 calling the program 214 in the memory 213.
  • the processor 212 is a CPU.
  • the transmitting module 662 can also be implemented by the processor 212 independently.
  • the processor 212 is a Field-Programmable Gate Array (FPGA) or other processing chip.
  • FPGA Field-Programmable Gate Array
  • all the numbers between the two numbers are changed according to a setting condition, that the preset backup period arrives or a snapshot of the production volume is created.
  • the second snapshot is the next snapshot of the first snapshot.
  • the sending module 662 is further configured to send the logical address of the backup data to the target volume.
  • the number between the two numbers does not include the second number.
  • the differential data backup apparatus since the first number of the two numbers is the number assigned to the data received by the production volume last time before the first snapshot of the production volume is created, The second number in the two numbers is the number assigned to the data received last time for the production volume after the second snapshot of the production volume is created, so the difference data is more than the backup data. Therefore, the differential data backup device provided in this embodiment does not need to suspend the write data request, and can still ensure that the difference data between the two snapshots is backed up to the target volume, thereby ensuring data consistency between the production volume and the target volume. Since there is no need to hang write data requests, the efficiency of data processing can be improved.
  • aspects of the present invention, or possible implementations of various aspects may be embodied as a system, method, or computer program product.
  • aspects of the invention, or possible implementations of various aspects may be in the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, etc.), or a combination of software and hardware aspects, They are collectively referred to herein as "circuits," “modules,” or “systems.”
  • aspects of the invention, or possible implementations of various aspects may take the form of a computer program product, which is a computer readable program code stored in a computer readable medium.
  • Computer readable media include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or devices, or any suitable combination of the foregoing, such as random access memory (RAM), read only memory (ROM), erasable Programmable read only memory (EPROM), optical disc.
  • RAM random access memory
  • ROM read only memory
  • EPROM erasable Programmable read only memory
  • the processor in the computer reads the computer readable program code stored in the computer readable medium such that the processor can perform the functional actions specified in each step or combination of steps in the flowchart.
  • the computer readable program code can execute entirely on the user's computer, partly on the user's computer, as a separate software package, partly on the user's computer and partly on the remote computer, or entirely on the remote computer or server.
  • the functions noted in the various steps in the flowcharts or in the blocks in the block diagrams may not occur in the order noted. For example, two steps, or two blocks, shown in succession may be executed substantially concurrently or the blocks may be executed in the reverse order.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Retry When Errors Occur (AREA)

Abstract

L'invention concerne un procédé de sauvegarde de données différentielles, ainsi qu'un dispositif de sauvegarde de données différentielles et un système de stockage. Le système de stockage comprend un processeur, un volume de production et un volume cible. Le processeur acquiert un enregistrement de données différentielles entre deux nombres, lesdits nombres étant utilisés pour signaler une période pendant laquelle des données sont écrites dans le volume de production. Un premier nombre parmi les deux nombres est un nombre attribué aux données reçues le plus récemment par le volume de production avant de créer un premier instantané du volume de production. Un second nombre parmi les deux nombres est un nombre attribué aux données reçues le plus récemment par le volume de production après avoir créé un second instantané du volume de production. L'enregistrement de données différentielles comprend les adresses logiques des données différentielles reçues pendant les périodes signalées par tous les nombres entre les deux nombres. Le processeur acquiert des données de sauvegarde à partir du second instantané conformément à l'enregistrement de données différentielles, puis envoie les données de sauvegarde au volume cible. L'invention permet d'empêcher la suspension d'une demande d'écriture de données, ce qui permet d'augmenter l'efficacité du traitement de données dans le système de stockage.
PCT/CN2017/096782 2016-12-29 2017-08-10 Procédé et dispositif de sauvegarde de données différentielles WO2018120844A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611249975.3A CN106776147B (zh) 2016-12-29 2016-12-29 一种差异数据备份方法和差异数据备份装置
CN201611249975.3 2016-12-29

Publications (1)

Publication Number Publication Date
WO2018120844A1 true WO2018120844A1 (fr) 2018-07-05

Family

ID=58927958

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/096782 WO2018120844A1 (fr) 2016-12-29 2017-08-10 Procédé et dispositif de sauvegarde de données différentielles

Country Status (2)

Country Link
CN (1) CN106776147B (fr)
WO (1) WO2018120844A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110442476A (zh) * 2019-06-25 2019-11-12 平安科技（深圳）有限公司 数据快照方法、装置、设备及存储介质
CN111026755A (zh) * 2019-12-06 2020-04-17 中国银行股份有限公司 基于全量序号发生器的交易序号获取方法及装置
CN113094207A (zh) * 2019-12-23 2021-07-09 华为技术有限公司 数据备份方法及系统
CN114697351A (zh) * 2020-12-30 2022-07-01 华为技术有限公司 一种存储管理方法、设备及介质

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106776147B (zh) * 2016-12-29 2020-10-09 华为技术有限公司 一种差异数据备份方法和差异数据备份装置
CN108733513A (zh) * 2018-05-07 2018-11-02 杭州宏杉科技股份有限公司 一种数据更新方法及装置
CN109614055B (zh) * 2018-12-21 2022-11-04 杭州宏杉科技股份有限公司 快照创建方法、装置、电子设备及机器可读存储介质
EP3896571B1 (fr) * 2018-12-29 2023-10-04 Huawei Technologies Co., Ltd. Procédé, appareil et système de sauvegarde de données

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103649901A (zh) * 2013-07-26 2014-03-19 华为技术有限公司 数据发送方法、数据接收方法和存储设备
US8832027B1 (en) * 2014-03-28 2014-09-09 Storagecraft Technology Corporation Change tracking between snapshots of a source storage
CN105607968A (zh) * 2015-12-17 2016-05-25 浙江大华技术股份有限公司 一种增量备份方法及设备
US20160283148A1 (en) * 2015-03-24 2016-09-29 Nec Corporation Backup control device, backup control method, and recording medium
CN106776147A (zh) * 2016-12-29 2017-05-31 华为技术有限公司 一种差异数据备份方法和差异数据备份装置

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TW201227268A (en) * 2010-12-20 2012-07-01 Chunghwa Telecom Co Ltd Data backup system and data backup and retrival method
US8965850B2 (en) * 2011-11-18 2015-02-24 Dell Software Inc. Method of and system for merging, storing and retrieving incremental backup data
US9218255B2 (en) * 2012-08-27 2015-12-22 International Business Machines Corporation Multi-volume instant virtual copy freeze
CN104572340A (zh) * 2013-10-18 2015-04-29 宇宙互联有限公司 增量备份系统及方法
CN103699459A (zh) * 2013-12-31 2014-04-02 汉柏科技有限公司 基于qcow2快照的虚拟机数据增量备份方法及系统
CN104536846A (zh) * 2014-12-17 2015-04-22 杭州华为数字技术有限公司 一种备份数据的方法及装置
CN105138426B (zh) * 2015-08-20 2018-04-13 浪潮(北京)电子信息产业有限公司 一种基于快照的业务级数据一致性保护方法及装置
CN105162869B (zh) * 2015-09-18 2019-01-18 久盈世纪（北京）科技有限公司 一种用于数据备份管理的方法与设备
CN105389230B (zh) * 2015-10-21 2018-06-22 上海爱数信息技术股份有限公司 一种结合快照技术的持续数据保护系统及方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103649901A (zh) * 2013-07-26 2014-03-19 华为技术有限公司 数据发送方法、数据接收方法和存储设备
US8832027B1 (en) * 2014-03-28 2014-09-09 Storagecraft Technology Corporation Change tracking between snapshots of a source storage
US20160283148A1 (en) * 2015-03-24 2016-09-29 Nec Corporation Backup control device, backup control method, and recording medium
CN105607968A (zh) * 2015-12-17 2016-05-25 浙江大华技术股份有限公司 一种增量备份方法及设备
CN106776147A (zh) * 2016-12-29 2017-05-31 华为技术有限公司 一种差异数据备份方法和差异数据备份装置

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110442476A (zh) * 2019-06-25 2019-11-12 平安科技（深圳）有限公司 数据快照方法、装置、设备及存储介质
CN111026755A (zh) * 2019-12-06 2020-04-17 中国银行股份有限公司 基于全量序号发生器的交易序号获取方法及装置
CN111026755B (zh) * 2019-12-06 2023-05-02 中国银行股份有限公司 基于全量序号发生器的交易序号获取方法及装置
CN113094207A (zh) * 2019-12-23 2021-07-09 华为技术有限公司 数据备份方法及系统
CN113094207B (zh) * 2019-12-23 2023-11-03 华为技术有限公司 数据备份方法及系统
CN114697351A (zh) * 2020-12-30 2022-07-01 华为技术有限公司 一种存储管理方法、设备及介质
CN114697351B (zh) * 2020-12-30 2023-03-10 华为技术有限公司 一种存储管理方法、设备及介质

Also Published As

Publication number Publication date
CN106776147A (zh) 2017-05-31
CN106776147B (zh) 2020-10-09

Similar Documents

Publication Publication Date Title
WO2018120844A1 (fr) Procédé et dispositif de sauvegarde de données différentielles
US10977124B2 (en) Distributed storage system, data storage method, and software program
US8521685B1 (en) Background movement of data between nodes in a storage cluster
US9690666B1 (en) Incremental backup operations in a transactional file system
US9703816B2 (en) Method and system for forward reference logging in a persistent datastore
WO2018076633A1 (fr) Procédé de duplication de données à distance, dispositif de stockage et système de stockage
CN111164584B (zh) 用于管理针对低延迟存储装置的分布式快照的方法及其设备
US10095585B1 (en) Rebuilding data on flash memory in response to a storage device failure regardless of the type of storage device that fails
US10394491B2 (en) Efficient asynchronous mirror copy of thin-provisioned volumes
US8140886B2 (en) Apparatus, system, and method for virtual storage access method volume data set recovery
US20180260281A1 (en) Restoring a storage volume from a backup
WO2019080370A1 (fr) Procédé et appareil de lecture et d'écriture de données, et serveur de stockage
US11327844B1 (en) Automated cloud recovery to provide a full usable application image
WO2020087930A1 (fr) Procédé et appareil de protection de données, et système
US10983930B1 (en) Efficient non-transparent bridge (NTB) based data transport
US8595454B1 (en) System and method for caching mapping information for off-host backups
WO2015035814A1 (fr) Procédé d'écriture de données et dispositif de stockage
US10503426B2 (en) Efficient space allocation in gathered-write backend change volumes
JPWO2018051505A1 (ja) ストレージシステム
US9619336B2 (en) Managing production data
US10740189B2 (en) Distributed storage system
US8880939B2 (en) Storage subsystem and method for recovering data in storage subsystem
US10929255B2 (en) Reducing the size of fault domains
WO2018055686A1 (fr) Système de traitement d'informations
US9703497B2 (en) Storage system and storage control method

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: 17887521

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: 17887521

Country of ref document: EP

Kind code of ref document: A1