CN111913832A - A data backup method and data backup device - Google Patents

Abstract

The invention provides a data backup method and a data backup device. The data backup method, applied to a second backup device, where the second backup device is a virtual block device, includes: receiving first backup data sent by the first backup device, wherein the first backup data is the first backup device through the block level Continuous data protection CDP backup is obtained by backing up data in the first target device, where the first backup data includes at least one data block; the first backup data is backed up to object storage to obtain second backup data, and the second backup data includes At least one data object, and each data block corresponds to one data object. The invention saves the data that needs to be backed up in the electronic device in the first backup device in the form of block-level CDP backup, and then backs up the backup data to the virtual block device, which has high storage expansibility and strong performance. When recovery occurs, recovery is fast and at the same time, it helps to reduce costs.

Description

A data backup method and data backup device

technical field

The invention relates to the technical field of computers, and in particular, to a data backup method and a data backup device.

Background technique

Disaster recovery system refers to the establishment of two or more sets of data backup centers in distant places. When a data backup center stops working due to an accident (such as fire, earthquake, etc.), data recovery can be performed through other data backup systems. , to avoid data loss.

In the current backup and disaster recovery market, data backup solutions are usually stored and backed up through block storage. Block storage provides high-performance random I/O (input/output ports) and data throughput under certain network conditions. However, the method for disaster recovery based on the storage of block storage devices is expensive and not easy to expand.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a data backup method and a data backup device, so as to solve the problem that the existing disaster recovery backup device has high success and is not easy to expand.

In a first aspect, an embodiment of the present invention provides a data backup method, which is applied to a second backup device, where the second backup device is a virtual block device, and the data backup method includes the following steps:

Receive the first backup data sent by the first backup device, where the first backup data is obtained by the first backup device backing up the data in the first target device through block-level continuous data protection CDP backup, and the The first backup data includes at least one data block;

The first backup data is backed up to an object storage to obtain second backup data, the second backup data includes at least one data object, and each of the data blocks corresponds to one of the data objects.

Optionally, the second backup device includes a snapshot bucket and a configuration bucket, and the backup of the first backup data to the object storage includes:

saving each of the data blocks in the first backup data to the snapshot bucket;

Recording the correspondence between each of the data blocks saved in the snapshot bucket and each of the data objects, and the location of each of the data blocks as a snapshot mapping item corresponding to each of the data blocks;

recording each of the snapshot mapping items into a snapshot mapping configuration, and inserting the identification code of the snapshot mapping configuration into the snapshot history;

Save the snapshot mapping configuration and the snapshot history to the configuration bucket.

Optionally, after the snapshot mapping configuration and the snapshot history are saved in the configuration bucket, the method further includes:

In the case of receiving a first restore instruction, send the snapshot mapping configuration to a second target device according to the first restore instruction, where the second target device is the same device as the first target device or a different device, the first restoration instruction includes a snapshot mapping configuration selection instruction for the first target device;

In the case of receiving a second restoration instruction, the snapshot history corresponding to the first target device is sent to the second target device, wherein the second restoration instruction includes a snapshot history of the first target device select command;

sending the snapshot mapping configuration to the second target device in the case of receiving a third restoration instruction, wherein the third restoration instruction includes a selection instruction for a snapshot mapping configuration in the snapshot history;

Deduplication of the snapshot mapping configuration determined by the third restoration instruction according to the identification code of the snapshot mapping configuration;

The corresponding data object is sent to the second target device according to the deduplicated snapshot mapping configuration, so that the second target device writes the data object into a data block.

In a second aspect, an embodiment of the present invention provides a data backup method, which is applied to a first backup device, and the data backup method includes the following steps:

The first backup device backs up data in the first target device through block-level CDP backup to obtain first backup data, where the first backup data includes at least one data block;

Send the first backup data to a second backup device, so that the second backup device backs up the first backup data to object storage and obtains second backup data, where the second backup data includes at least one A data object, each of the data blocks corresponds to one of the data objects, wherein the second backup device is a virtual block device.

In a third aspect, an embodiment of the present invention provides a data backup device, the backup device is a second backup device, and the second backup device is a virtual block device, and the second backup device includes:

a receiving module, configured to receive the first backup data sent by the first backup device, wherein the first backup data is obtained by the first backup device backing up the data in the first target device through block-level CDP backup, The first backup data includes at least one data block;

A backup module, configured to back up the first backup data to the object storage to obtain second backup data, where the second backup data includes at least one data object, and each of the data blocks corresponds to one of the data objects .

Optionally, the second backup device includes a snapshot bucket and a configuration bucket, and the backup module includes:

a first saving submodule, configured to save each of the data blocks in the first backup data to the snapshot bucket;

A recording submodule, configured to record the correspondence between each of the data blocks saved in the snapshot bucket and each of the data objects, and the location of each of the data blocks as a snapshot map corresponding to each of the data blocks item;

an inserting module for recording each of the snapshot mapping items into a snapshot mapping configuration, and inserting the identification code of the snapshot mapping configuration into the snapshot history;

The second saving sub-module is configured to save the snapshot mapping configuration and the snapshot history to the configuration bucket.

Optionally, it further includes: a first sending module, configured to send the snapshot mapping configuration to the second target device according to the first restoration instruction in the case of receiving the first restoration instruction, wherein the first restoration instruction The second target device is the same device as the first target device or a different device, and the first restoration instruction includes a snapshot mapping configuration selection instruction for the first target device;

A second sending module, configured to send the snapshot history corresponding to the first target device to the second target device when a second restoration instruction is received, wherein the second restoration instruction includes The selection instruction of the snapshot history of the first target device;

A third sending module, configured to send the snapshot mapping configuration to the second target device when a third restoration instruction is received, wherein the third restoration instruction includes a snapshot of the snapshot in the snapshot history Mapping configuration selection directive;

A deduplication module, configured to deduplicate the snapshot mapping configuration determined by the third restoration instruction according to the identification code of the snapshot mapping configuration;

The fourth sending module is configured to send the corresponding data object to the second target device according to the deduplicated snapshot mapping configuration, so that the second target device can write the data object into a data block.

In a fourth aspect, an embodiment of the present invention provides a data backup device, the data backup device is a first backup device, and the data backup device includes:

a backup module, used for the first backup device to back up data in the first target device through block-level CDP backup to obtain first backup data, where the first backup data includes at least one data block;

A sending module, configured to send the first backup data to a second backup device, so that the second backup device can back up the first backup data to object storage and obtain second backup data, the second backup data The backup data includes at least one data object, each of the data blocks corresponds to one of the data objects, wherein the second backup device is a virtual block device.

In a fifth aspect, an embodiment of the present invention provides an electronic device, including a processor, a memory, and a computer program stored on the memory and executable on the processor, where the computer program is executed by the processor When implementing the steps of the message push display method described in any of the above.

In a sixth aspect, an embodiment of the present invention provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, implements the steps of the data backup method described in any one of the preceding claims.

The invention saves the data that needs to be backed up in the electronic device in the first backup device in the form of block-level CDP backup, and then backs up the backup data to the virtual block device, which has high storage expansibility and strong performance. When recovery occurs, recovery is fast and at the same time, it helps to reduce costs.

Description of drawings

In order to illustrate the technical solutions of the embodiments of the present invention more clearly, the following briefly introduces the accompanying drawings that need to be used in the description of the embodiments of the present invention. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without any creative effort.

1 is a flowchart of a data backup method provided by an embodiment of the present invention;

Fig. 2 is the schematic diagram of data block in block storage;

Figure 3 is a schematic diagram of a bucket in object storage;

4 is another flowchart of a data backup method provided by an embodiment of the present invention;

5 is a schematic diagram of a snapshot file in an embodiment of the present invention;

6 is another flowchart of a data backup method provided by an embodiment of the present invention;

7 is another flowchart of a data backup method provided by an embodiment of the present invention;

8 is another flowchart of a data backup method provided by an embodiment of the present invention;

9 is a structural diagram of a second backup device provided by an embodiment of the present invention;

10 is another structural diagram of a second backup device provided by an embodiment of the present invention;

11 is another structural diagram of a second backup device provided by an embodiment of the present invention;

12 is a structural diagram of a first backup device provided by an embodiment of the present invention;

FIG. 13 is a structural diagram of a data backup system provided by an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

An embodiment of the present invention provides a data backup method, which is applied to a second backup device.

The second backup device is a virtual block device, that is to say, the second backup device itself is not a block device but an object storage, and virtualized as a block device by means of virtualization, and the second backup device can use existing Some object storage servers, and then virtualize them as block devices, or directly use the object storage services provided by existing cloud service providers, and then virtualize them as block devices as the second backup device used in data backup .

As shown in Figure 1, the data backup method includes the following steps:

Step 101: Receive first backup data sent by a first backup device.

The first backup data in this embodiment is obtained by the first backup device backing up the data in the first target device through block-level CDP (Continuous Data Protection, continuous data protection) backup.

Here, the first target device refers to the device where the original data to be backed up is located. After the data is backed up by the block-level CDP in the first target device, the data is sent to the second backup device, so that the first backup data can be backed up by the second backup device. Backup again.

The CDP backup in this embodiment is a block-level CDP backup, so the first backup data obtained from the backup is composed of one or more data blocks.

As shown in Figure 2, Figure 2 represents a piece of data in the block storage, each small box in Figure 2 represents a data block 201, and the data on the block storage is divided into equal-sized blocks with a fixed value, called Data block 201.

Step 102: Back up the first backup data to an object storage to obtain second backup data, where the second backup data includes at least one data object, and each of the data blocks corresponds to one of the data objects.

The first backup data is stored in the form of object storage (or called object-based storage) in the second backup device. As shown in Figure 3, the object storage is composed of two levels: bucket 300 and object 301 (or called data object). , and each bucket includes multiple objects 301 . The process of backing up the first backup data to the object storage, that is, moving the data in each data block to each data object.

In this way, the original data in the first target device actually has two backups, one of which is the first backup data located in the first backup device, and the other is the second backup located in the second backup device data.

Existing block devices have high cost, poor scalability, and relatively complex technology.

The invention saves the data to be backed up in the electronic device in the first backup device in the form of block-level CDP backup, and then backs up the backup data to the object storage in the virtual block device.

Since object storage has a unified standard, for example, the existing object storage is based on the unified standard of RESTful API (Representational State Transfer, characterization; Application Programming Interface, application programming interface), so the support functions of different manufacturers for object storage are basically the same, On this basis, it can be used as a unified object storage backup gateway, and can support almost all object storages on the market as the second backup storage for disaster recovery backup. Therefore, this scheme has high versatility and scalability.

At the same time, object storage services are provided by cloud vendors. For example, cloud services provided by existing vendors are selected. They have nearly unlimited capacity and pay-as-you-go features, which are more flexible in use, more scalable, and relatively low in cost. .

In addition, the object storage of the second backup device is a virtual block-level device, and the first backup device is also a block-level device, so the first backup data can be backed up without major adjustments to the backup architecture of the first backup data To the second backup data, it is more convenient and quick.

Optionally, in a specific implementation manner, as shown in FIG. 4 , the foregoing step 102 includes:

Step 1021: Save each of the data blocks in the first backup data to the snapshot bucket.

When saving each data block in the first backup data in the snapshot bucket, it needs to ensure that the data in each data block is saved in the snapshot bucket. If it is the first backup, you need to save the data in all data blocks (or the full amount of data) into the snapshot bucket. If it is not the first backup, you only need to increase the data in the period between this backup and the previous backup. You can save the corresponding data blocks to the snapshot bucket.

As shown in Figure 5, the left side of Figure 5 represents the data that needs to be backed up at different times, and the right side represents the data that needs to be saved to the snapshot bucket during backup. The data at time t0 is A0, B0, C0, D0, E0, F0, G0, H0, then the data to be backed up for the first time is A0, B0, C0, D0, E0, F0, G0, H0; at time t1, the data changes If the data is A1, B1, C1, D1, E0, F0, G0, H0, then at t1, only the changed data A1, B1, C1, D1 needs to be backed up, while the unchanged data E0, F0, G0, H0, do not need to be re-saved to the snapshot bucket, and so on.

Step 1022: Record the correspondence between each of the data blocks saved in the snapshot bucket and each of the data objects, and the location of each of the data blocks as a snapshot map item corresponding to each of the data blocks.

Snapshot mapping items are used to index the correspondence between data blocks and data objects. Therefore, according to each snapshot mapping item, the unique mapping relationship between data blocks, data objects and the location of the database can be determined, so as to achieve the second backup device. Determine the directory and location of the data. In this way, the incremental data in the data block can be determined according to a snapshot map entry.

Step 1023: Record each of the snapshot mapping items into a snapshot mapping configuration, and insert the identification code (ID, identification) of the snapshot mapping configuration into the snapshot history.

The data increment during each backup may include one or more data blocks, therefore, multiple snapshot mapping items will be generated correspondingly during each backup. In this way, a snapshot mapping configuration including all snapshot mapping items generated in a backup actually includes all data increments in this backup.

Step 1024: Save the snapshot mapping configuration and the snapshot history to the configuration bucket.

The object storage of the second backup device includes two buckets, a configuration bucket and a snapshot bucket, wherein the configuration bucket is used for storing configuration file objects, and the snapshot bucket is used for storing snapshot data objects.

The number of snapshot data objects is usually very large, so it may affect the read and write performance of the configuration file objects. Storing configuration file objects and snapshot data objects in different buckets helps improve the read and write performance of object storage.

As shown in FIG. 6 , it can be summarized as follows: after receiving the backup instruction, first search for a virtual block device, that is, the above-mentioned second backup device, if the virtual block device is not found, create a snapshot, if no virtual block device is found. block device, then directly save the backup data to the object storage.

In the process of creating a snapshot, if the file is copied for the first time, the latest data of the backup is determined, that is, all data. If the file is not copied for the first time, that is, there is a previously created snapshot, only the time of the latest snapshot is copied. The newly added data from the point to the current time point, or incremental data. After the snapshot is created, the data block and related information are received. Here, the data block and related information refer to the data block and related information where the data to be backed up is located.

Further, calling the API to upload the data object, that is, backing up the data in each data block to the data object. Then, it is recorded as a snapshot mapping item according to the data block and the corresponding data object. Repeat this step until the snapshot mapping items corresponding to all data blocks are recorded, and then save all snapshot mapping items into a mapping configuration and add them to the historical snapshots. After calling the API to upload the snapshot history and snapshot mapping files, the process of Data backup is performed in the second backup device.

Optionally, after the above step 1024, the method further includes:

The snapshot map configuration is sent to the second target device according to the first restoration instruction in the case of receiving the first restoration instruction.

In some cases, it may be necessary to restore data to a second target device, where the second target device is the same device as the first target device or a different device. It should be understood that if the data in the original first target device is lost, the backup data can be directly restored to the original first target device. In this case, the first target device and the second target device are the same device.

If the first target device is unavailable, such as irreparable physical damage caused by fire or other factors, or a new device is replaced due to equipment upgrade, in this case, the second target device and the first target device are different devices .

The first restoration instruction includes a snapshot mapping configuration selection instruction for the first target device, that is, the first restoration instruction is used to determine the original device of the data to be restored.

For example, multiple devices are backed up in the second backup device, including the first server, the second server, and the third server. Due to the device update of the second server, the original data in the second server needs to be restored to the fourth server. , then the second server is the above-mentioned first target device, that is, the original device, and the fourth server is the second target device, and the first restoration instruction includes actually selecting the snapshot mapping configuration of the second server from these three servers. Select the command.

In the case of receiving the second restoration instruction, the snapshot history corresponding to the first target device is sent to the second target device.

The second restoration instruction includes a selection instruction for the snapshot history of the first target device, which can be understood as the second restoration instruction is used to select a snapshot for restoration.

For example, the snapshots related to the second server in the second backup device include three snapshots: the first snapshot, the second snapshot and the third snapshot, which correspond to different time points respectively. In this recovery process, the third snapshot of the latest backup needs to be recovered , the selection instruction included in the second restoration instruction is actually an instruction to select the third snapshot from the three snapshots.

The snapshot map configuration is sent to the second target device upon receipt of a third restore instruction.

The third restoration instruction includes an instruction for selecting a snapshot mapping configuration in the snapshot history, where the snapshot mapping configuration refers to the snapshot mapping configuration generated in the above step 1023, and a corresponding snapshot mapping file can be obtained according to the determined snapshot mapping configuration , which implements a call to the snapshot for data recovery.

The snapshot mapping configuration determined by the third restoration instruction is deduplicated according to the identification code of the snapshot mapping configuration.

In a range of snapshots, there may be multiple data objects in the same data block location from snapshots at different times, so the data objects need to be deduplicated.

The deduplication process can deduplicate by retrieving whether the same snapshot map entry exists.

In a specific implementation manner, deduplication is achieved through a B+ tree.

Specifically, during implementation, the index of the data block is used as the key (key), and the snapshot mapping item and the snapshot ID are used as the value (value) to form a B+ tree. Traverse all snapshots in the selected range and traverse each snapshot map entry in the snapshot map configuration corresponding to each snapshot, and insert each snapshot map entry into the B+ tree.

There may be two situations in the insertion process: first, the index of the current data block does not exist in the B+ tree, then the index of the data block is used as the key, and the snapshot mapping item and the snapshot ID are used as the value to insert into the B+ tree. . Second, the index of the current data block exists in the B+ tree, then compare the snapshot ID of the snapshot mapping item to be inserted and the snapshot ID in the value in the B+ tree. If the snapshot ID of the snapshot mapping item to be inserted is newer, then Replace the value of the same key, otherwise no need to insert.

The corresponding data object is sent to the second target device according to the deduplicated snapshot mapping configuration, so that the second target device writes the data object into a data block.

After the construction of the B+ tree is completed, the snapshot mapping items in the leaf nodes correspond to the data objects of the data blocks in different positions in the object storage, and these data objects are the data of the latest state at the time of creation of the specified snapshot. Traverse the snapshot map items in the leaf node, obtain the data object corresponding to the data object ID through the object storage API, forward the data through the IO service (Input/Output, input and output service), and finally complete the recovery operation.

As shown in FIG. 7 , it can be summarized that, after receiving the recovery instruction, the API is firstly called to download the device list in the object storage server, and the list includes devices that can perform data recovery. After receiving the command to execute the device for restoration, call the API to download the snapshot history of the device to be restored. Further, after receiving the command to specify the snapshot for restoration, call the API to download the first snapshot to the specified snapshot range The snapshot mapping file in the specified snapshot mapping file, that is, the snapshot mapping file corresponding to all the data backed up before the time node corresponding to the specified snapshot.

After obtaining the snapshot mapping file, deduplicate the snapshot mapping file. Taking the B+ tree deduplication as an example, the snapshot mapping items (or mapping items) in the snapshot mapping file are continuously added to the B+ tree. After all the mapping items, get a leaf node, then call the API to download the data object associated with the mapping item in the leaf node, write the data object into the data block, and continuously obtain the leaf node. When all the nodes are processed, the data is completed. recovery.

The embodiment of the present invention also provides a data backup method, which is applied to the first backup device.

The first backup device may be the first backup device in the above embodiment. As shown in FIG. 8 , the data backup method includes the following steps:

Step 801: the first backup device backs up data in the first target device through block-level CDP backup to obtain first backup data, where the first backup data includes at least one data block;

Step 802: Send the first backup data to a second backup device, so that the second backup device backs up the first backup data to object storage and obtains second backup data, the second backup data It includes at least one data object, each of the data blocks corresponds to one of the data objects, wherein the second backup device is a virtual block device.

In this embodiment, for the block-level CDP backup process, reference may be made to the existing and possible block-level CDP backup process, and in step 802, after the first backup data is sent to the second backup data, reference may be made to the above-mentioned embodiment, Various technical effects described in the above embodiments can be achieved, and details are not repeated here.

An embodiment of the present invention provides a data backup device. The backup device is a second backup device 900, and the second backup device 900 is a virtual block device. As shown in FIG. 9, the second backup device 900 include:

A receiving module 901, configured to receive first backup data sent by a first backup device, wherein the first backup data is obtained by the first backup device backing up data in a first target device through block-level CDP backup , the first backup data includes at least one data block;

The backup module 902 is configured to back up the first backup data to object storage to obtain second backup data, where the second backup data includes at least one data object, and each of the data blocks is associated with one of the data objects. correspond.

Optionally, as shown in FIG. 10 , the second backup device 900 includes a snapshot bucket and a configuration bucket, and the backup module 902 includes:

a first saving submodule 9021, configured to save each of the data blocks in the first backup data to the snapshot bucket;

Recording sub-module 9022, configured to record the correspondence between each of the data blocks saved in the snapshot bucket and each of the data objects, and the position of each of the data blocks as a snapshot corresponding to each of the data blocks mapping item;

an inserting module 9023, configured to record each of the snapshot mapping items into a snapshot mapping configuration, and insert the identification code of the snapshot mapping configuration into the snapshot history;

The second saving sub-module 9024 is configured to save the snapshot mapping configuration and the snapshot history to the configuration bucket.

Optionally, as shown in FIG. 11 , it further includes: a first sending module 903, configured to send the snapshot mapping configuration to the second target according to the first restoration instruction in the case of receiving the first restoration instruction device, wherein the second target device is the same device as the first target device or a different device, and the first restoration instruction includes a snapshot mapping configuration selection instruction for the first target device;

The second sending module 904 is configured to send the snapshot history corresponding to the first target device to the second target device when a second restoration instruction is received, wherein the second restoration instruction includes Describe the selection instruction of the snapshot history of the first target device;

The third sending module 905 is configured to send the snapshot mapping configuration to the second target device in the case of receiving a third restoration instruction, wherein the third restoration instruction includes Selection directive for snapshot mapping configuration;

A deduplication module 906, configured to deduplicate the snapshot mapping configuration determined by the third restoration instruction according to the identification code of the snapshot mapping configuration;

The fourth sending module 907 is configured to send the corresponding data object to the second target device according to the deduplicated snapshot mapping configuration, so that the second target device can write the data object into a data block .

The invention saves the data that needs to be backed up in the electronic device in the first backup device in the form of block-level CDP backup, and then backs up the backup data to the virtual block device, which has high storage expansibility and strong performance. When recovery occurs, recovery is fast and at the same time, it helps to reduce costs.

An embodiment of the present invention provides a data backup device. The data backup device is a first backup device 1200. As shown in FIG. 12, the first backup device 1200 includes:

The backup module 1201 is used for the first backup device to back up data in the first target device through block-level CDP backup to obtain first backup data, where the first backup data includes at least one data block;

The sending module 1202 is configured to send the first backup data to a second backup device, so that the second backup device can back up the first backup data to object storage and obtain second backup data, and the first backup data can be obtained by the second backup device. The second backup data includes at least one data object, each of the data blocks corresponds to one of the data objects, wherein the second backup device is a virtual block device.

The invention saves the data that needs to be backed up in the electronic device in the first backup device in the form of block-level CDP backup, and then backs up the backup data to the virtual block device, which has high storage expansibility and strong performance. When recovery occurs, recovery is fast and at the same time, it helps to reduce costs.

As shown in FIG. 13 , the data backup system in this embodiment includes an IO module, a CDP module, a virtual block-level device and an API calling module, wherein the IO module provides data writing and reading services, and the CDP module is equivalent to the above-mentioned first A backup device, the virtual block-level device is actually equivalent to the above-mentioned second backup device, and the API calling module is used to call the API interface of the object storage service.

By performing the steps of the data backup method in the above embodiment, data backup and recovery can be realized. In the present invention, the data that needs to be backed up in the electronic device is stored in the first backup device in the form of block-level CDP backup, and then The backup data is then backed up to a virtual block device, which has high storage scalability and high performance. When recovery is required, the recovery speed is fast, and at the same time, it helps to reduce costs.

An embodiment of the present invention provides an electronic device, including a processor, a memory, and a computer program stored on the memory and executable on the processor, where the computer program is executed by the processor to achieve the above The steps of any one of the data backup methods.

An embodiment of the present invention provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, implements the steps of the data backup method described in any one of the preceding claims.

Since the technical solutions in this embodiment can implement all the technical solutions of the above data backup method embodiments, at least all the above technical effects can be achieved, which will not be repeated here.

The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited to this. Any person skilled in the art who is familiar with the technical scope disclosed by the present invention can easily think of changes or replacements, which should cover within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims (11)

1. A data backup method is applied to a second backup device, and is characterized in that the second backup device is a virtual block device, and the data backup method comprises the following steps:

receiving first backup data sent by first backup equipment, wherein the first backup data is obtained by the first backup equipment through backing up data in first target equipment through block-level continuous data protection CDP backup, and the first backup data comprises at least one data block;

and backing up the first backup data to an object storage to obtain second backup data, wherein the second backup data comprises at least one data object, and each data block corresponds to one data object.

2. The data backup method of claim 1, wherein the second backup device comprises a snapshot bucket and a configuration bucket, and wherein backing up the first backup data to an object store comprises:

saving each data block in the first backup data to the snapshot bucket;

recording the corresponding relation between each data block saved in the snapshot bucket and each data object and the position of each data block as a snapshot mapping item corresponding to each data block;

recording each snapshot mapping item to a snapshot mapping configuration, and inserting an identification code of the snapshot mapping configuration into a snapshot history;

saving the snapshot mapping configuration and the snapshot history to the configuration bucket.

3. The data backup method of claim 2, wherein after saving the snapshot map configuration and the snapshot history to the configuration bucket, the method further comprises:

under the condition that a first recovery instruction is received, sending the snapshot mapping configuration to second target equipment according to the first recovery instruction, wherein the second target equipment is the same equipment as the first target equipment or different equipment, and the first recovery instruction comprises a snapshot mapping configuration selection instruction of the first target equipment;

under the condition that a second recovery instruction is received, sending the snapshot history corresponding to the first target equipment to the second target equipment, wherein the second recovery instruction comprises a selection instruction of the snapshot history of the first target equipment;

under the condition that a third recovery instruction is received, sending the snapshot mapping configuration to the second target equipment, wherein the third recovery instruction comprises a selection instruction of the snapshot mapping configuration in the snapshot history;

removing the duplicate of the snapshot mapping configuration determined by the third recovery instruction according to the identification code of the snapshot mapping configuration;

and sending the corresponding data object to the second target equipment according to the deduplicated snapshot mapping configuration so that the second target equipment can write the data object into a data block.

4. A data backup method is applied to a first backup device, and is characterized by comprising the following steps:

the first backup device backs up data in a first target device through block-level CDP backup to obtain first backup data, wherein the first backup data comprises at least one data block;

and sending the first backup data to a second backup device so that the second backup device backs up the first backup data to an object for storage and obtains second backup data, wherein the second backup data comprises at least one data object, each data block corresponds to one data object, and the second backup device is a virtual block device.

5. A data backup device, wherein the backup device is a second backup device, and the second backup device is a virtual block device, the second backup device comprising:

a receiving module, configured to receive first backup data sent by a first backup device, where the first backup data is obtained by the first backup device backing up data in a first target device through block-level CDP backup, and the first backup data includes at least one data block;

and the backup module is used for backing up the first backup data to an object for storage so as to obtain second backup data, the second backup data comprises at least one data object, and each data block corresponds to one data object.

6. The data backup device of claim 5 wherein the second backup device comprises a snapshot bucket and a configuration bucket, the backup module comprising:

the first saving submodule is used for saving each data block in the first backup data to the snapshot bucket;

a recording submodule, configured to record a correspondence between each data block saved in the snapshot bucket and each data object, and a position of each data block as a snapshot mapping item corresponding to each data block;

the inserting module is used for recording each snapshot mapping item to a snapshot mapping configuration and inserting the identification code of the snapshot mapping configuration into snapshot history;

a second saving submodule, configured to save the snapshot mapping configuration and the snapshot history to the configuration bucket.

7. The data backup device of claim 6, further comprising:

a first sending module, configured to send the snapshot mapping configuration to a second target device according to a first recovery instruction when the first recovery instruction is received, where the second target device is the same device as or different from the first target device, and the first recovery instruction includes a snapshot mapping configuration selection instruction for the first target device;

a second sending module, configured to send, when a second recovery instruction is received, the snapshot history corresponding to the first target device to the second target device, where the second recovery instruction includes a selection instruction of the snapshot history of the first target device;

a third sending module, configured to send the snapshot mapping configuration to the second target device when a third recovery instruction is received, where the third recovery instruction includes a selection instruction of the snapshot mapping configuration in the snapshot history;

the duplication removing module is used for removing the duplication of the snapshot mapping configuration determined by the third recovery instruction according to the identification code of the snapshot mapping configuration;

and the fourth sending module is used for sending the corresponding data object to the second target equipment according to the snapshot mapping configuration after the duplication is removed so that the second target equipment can write the data object into a data block.

8. A data backup device, wherein the data backup device is a first backup device, the data backup device comprising:

the first backup device is used for backing up data in the first target device through block-level CDP backup to obtain first backup data, and the first backup data comprises at least one data block;

the sending module is configured to send the first backup data to a second backup device, so that the second backup device backs up the first backup data to an object for storage, and obtains second backup data, where the second backup data includes at least one data object, and each data block corresponds to one data object, where the second backup device is a virtual block device.

9. An electronic device comprising a processor, a memory and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the data backup method according to any one of claims 1 to 3.

10. An electronic device comprising a processor, a memory, and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the data backup method of claim 4.

11. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the data backup method of any one of claims 1 to 4.

Images