CN113806145A - Backup recovery method and device of OpenStack virtualization platform based on Ceph storage - Google Patents
Backup recovery method and device of OpenStack virtualization platform based on Ceph storage Download PDFInfo
- Publication number
- CN113806145A CN113806145A CN202111063396.0A CN202111063396A CN113806145A CN 113806145 A CN113806145 A CN 113806145A CN 202111063396 A CN202111063396 A CN 202111063396A CN 113806145 A CN113806145 A CN 113806145A
- Authority
- CN
- China
- Prior art keywords
- data
- backup
- ceph
- snapshot
- openstack
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 36
- 238000011084 recovery Methods 0.000 title claims description 46
- 230000005540 biological transmission Effects 0.000 claims abstract description 34
- 239000012634 fragment Substances 0.000 claims abstract description 21
- 230000008569 process Effects 0.000 claims abstract description 13
- 238000012545 processing Methods 0.000 claims abstract description 9
- 230000008859 change Effects 0.000 claims description 9
- 238000010586 diagram Methods 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 2
- 238000013467 fragmentation Methods 0.000 description 2
- 238000006062 fragmentation reaction Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
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/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- 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
- G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
- G06F16/128—Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a backup method of an OpenStack virtualization platform based on Ceph storage, which comprises the following steps: b1, obtaining a backup task, and determining a to-be-backed-up example in the OpenStack virtualization platform corresponding to the backup task and backing up target end Ceph platform information; b2, calling an OpenStack API, and creating a snapshot for the to-be-backed-up instance; b3, determining effective backup data to be copied to a target Ceph storage; b4, slicing the effective backup data to be copied; b5, generating a plurality of processes according to the number of the fragments, and processing the transmission of each data in parallel; b6, calling a Ceph storage bottom API interface, transmitting backup data to a target Ceph block storage, after creating a snapshot for the OpenStack instance, calling the Ceph bottom API interface, directly writing the snapshot data into the Ceph target block storage, and transferring the snapshot data without a local temporary file, so that the snapshot data copying time can be better saved, and the backup efficiency is improved.
Description
Technical Field
The invention relates to the technical field of OpenStack virtualization platforms based on Ceph storage, in particular to a backup recovery method and device of OpenStack virtualization platforms based on Ceph storage.
Background
OpenStack is an open-source cloud computing management platform project, covers various aspects of networks, virtualization, operating systems, servers and the like, provides scalable and elastic cloud computing services for private clouds and public clouds, Ceph is a uniform distributed storage system, has the advantages of high expansibility, high performance, high reliability and the like, can provide block storage service (rbd), object storage service (rgw) and file system storage service (cephfs), is combined with OpenStack to provide backend storage for OpenStack virtualization platforms, and has gradually become a mainstream cloud computing platform solution in the market, with the rapid development of cloud computing technology, people also increasingly pay attention to backup protection for virtualization and platforms to ensure data security and prevent data loss and damage, although OpenStack has become mature from birth to the present, in its own framework, the circbackup service can be used to backup protection for instances in the virtualization platforms, still there are many limitations and problems, for example, in the backup process, the backup snapshot stored in the OpenStack instance block needs to be copied to the local temporary file first, then the Ceph upper layer command is called to obtain the snapshot from the temporary file and copy the snapshot to the target Ceph block for storage, so that the backup process needs to copy twice, the processing time is long, the efficiency is low, and when the network environment is unstable, once the copy is interrupted, the copy needs to be restarted, furthermore, when the recovery is performed, the first full-volume backup snapshot data needs to be restored to the OpenStack target instance as a whole, then the 2 nd, 3 rd, and 4 … … th snapshot points are restored in sequence, the manner of restoring the snapshot points one by one can cause repeated reading and writing of a large amount of repeated data, the network bandwidth occupation of the transmission of the recovery data is greatly wasted, and the recovery efficiency is low, when the snapshot at a certain point in the middle is deleted, and the recovery is performed, the method needs to spend a large amount of resources for snapshot integration, is time-consuming and labor-consuming, and is the first problem to be solved by the method, namely how to improve backup and recovery efficiency and reduce network bandwidth resource waste.
Disclosure of Invention
The invention provides a backup recovery method and device of an OpenStack virtualization platform based on Ceph storage, which can effectively solve the problems that the efficiency of the backup and recovery process of an OpenStack instance is low and a large amount of repeated data is wasted on network bandwidth resources due to repeated reading and writing in the background technology.
In order to achieve the purpose, the invention provides the following technical scheme: the backup method of the OpenStack virtualization platform based on the Ceph storage comprises the following steps:
b1, obtaining a backup task, and determining a to-be-backed-up example in the OpenStack virtualization platform corresponding to the backup task and backing up target end Ceph platform information;
b2, calling an OpenStack API, and creating a snapshot for the to-be-backed-up instance;
b3, slicing the effective backup data to be copied;
b4, determining effective backup data to be copied to a target Ceph storage;
b5, generating a plurality of processes according to the number of the fragments, and processing the transmission of each data in parallel;
b6, calling a Ceph storage bottom layer API interface, and transmitting the backup data to the target Ceph block storage.
According to the above technical solution, the step B4 further includes:
b41, judging whether the snapshot created for the OpenStack instance to be backed up is a first snapshot, if so, determining the snapshot as effective backup data to be copied, and executing B4; if not, executing B42;
b42, calling a Ceph API interface, obtaining the difference incremental data of the current snapshot compared with the previous snapshot, and determining the difference incremental data as the effective backup data to be copied.
According to the above technical solution, the number of the slices mentioned in step B3 can be flexibly set, and can be set according to the number of CPU cores of the OpenStack instance, that is, the slice data to be transmitted can be uniformly distributed to different CPUs for parallel processing.
According to the above technical solution, in step B5, each process marks the start address and the end address of the fragment data at the source end, the target Ceph storage end, and the currently transmitted data location address, so as to ensure that parallel transmission of the fragments is not affected each other, and when the network environment fluctuates to cause transmission interruption, the data transmission can be continued from the transmission breakpoint location after the network is restored.
According to the technical scheme, the backup recovery method of the OpenStack virtualization platform based on the Ceph storage comprises the following steps:
r1, setting a recovery target instance parameter;
r2, selecting a snapshot point to be restored;
r3, calling a Ceph API interface, comparing the difference data with the previous snapshot in sequence from the backup point to be restored, and calculating effective restoration data;
r4, calling OpenStack API, and creating a recovery target instance;
r5, transmitting the valid data to the recovery target instance.
According to the above technical solution, the valid recovery data mentioned in the step R3 refers to: and comparing the difference data of each data block with the previous snapshot in sequence based on the selected snapshot data of the backup point to be restored, if the data block has the latest change, taking the latest change data to be put into the effective data to be restored, and if the data block is compared to the first snapshot point and still has no change, putting the first snapshot point data into the effective data to be restored to obtain the final effective restoration data.
According to the technical scheme, the backup recovery device of the OpenStack virtualization platform based on the Ceph storage is a device manufactured according to any one of the steps.
Compared with the prior art, the invention has the beneficial effects that:
1. after the snapshot is created for the OpenStack instance, a Ceph bottom API interface can be called, snapshot data are directly written into a Ceph target block storage, transfer is not needed through a local temporary file, the snapshot data copying time can be better saved, and the backup efficiency is improved.
2. And comparing the newly created snapshot with the previous snapshot to obtain difference incremental data, and only transmitting the difference incremental data to a Ceph target block for storage, so that the data transmission amount is reduced, and the backup efficiency is improved.
3. Before snapshot data transmission, fragmentation processing can be carried out on the snapshot effective backup data to generate a plurality of processes, and each piece of data is transmitted to the target Ceph block storage in parallel, so that the backup efficiency can be further improved.
4. In the transmission process of the backup snapshot data, the currently transmitted data address is marked, and when the transmission interruption occurs due to the fluctuation of the network environment, the transmission can be continued from the breakpoint after the network is restored, so that the whole backup snapshot does not need to be retransmitted, and the backup efficiency is improved.
5. When a snapshot is restored, the difference data is compared with the previous snapshot in sequence from the backup point to be restored, the effective restoration data is calculated, and the effective restoration data can be transmitted to the restoration target example only by once copying, so that the transmission quantity of the network data can be reduced, the network bandwidth can be saved, and the restoration efficiency can be greatly improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention and not to limit the invention.
In the drawings:
fig. 1 is a flowchart of a backup method for OpenStack backend storage based on Ceph according to an embodiment of the present invention;
fig. 2 is a schematic diagram of obtaining valid backup data according to an embodiment of the present invention.
Fig. 3 is a mapping relationship diagram of effective backup data fragment transmission at a source end and a target end according to an embodiment of the present invention;
fig. 4 is a schematic diagram of effective transmission breakpoint resuming of backup data according to an embodiment of the present invention;
fig. 5 is a flowchart of a recovery method for OpenStack backend storage based on Ceph according to an embodiment of the present invention;
fig. 6 is a schematic diagram of obtaining valid recovery data according to an embodiment of the present invention.
Detailed Description
The preferred embodiments of the present invention will be described in conjunction with the accompanying drawings, and it will be understood that they are described herein for the purpose of illustration and explanation and not limitation.
Example (b):
referring to fig. 1-5, the invention provides a backup recovery method for OpenStack backend storage based on Ceph, which is used for solving the problems that the efficiency of backup and recovery processes for OpenStack instances is low in the prior art, and network bandwidth resources are wasted due to repeated reading and writing of a large amount of repeated data, so that the data volume of backup recovery transmission is reduced, the occupation of bandwidth resources by data transmission during backup recovery is reduced, the backup recovery time is shortened, and the overall efficiency of backup recovery is improved.
Fig. 1 is a flowchart of a backup method for OpenStack backend storage based on Ceph according to an embodiment of the present invention;
as shown in fig. 1, the method comprises the following steps:
b1, obtaining a backup task, and determining a to-be-backed-up example in the OpenStack virtualization platform corresponding to the backup task and backing up target end Ceph platform information;
b2, calling an OpenStack API, and creating a snapshot for the to-be-backed-up instance;
b3, slicing the effective backup data to be copied;
b4, determining effective backup data to be copied to a target Ceph storage;
b5, generating a plurality of processes according to the number of the fragments, and processing the transmission of each data in parallel;
b6, calling a Ceph storage bottom layer API interface, and transmitting the backup data to the target Ceph block storage.
Fig. 2 is a schematic diagram illustrating obtaining effective backup data according to an embodiment of the present invention.
The RBD source volume of the OpenStack instance to be backed up is composed of a plurality of Object file objects with fixed unit sizes, for example, each Object has a size of 4MB, and when calculating valid backup data of a current snapshot, it is necessary to compare whether each Object has data change with a previous snapshot.
Specifically, the step B3 further includes:
b41, judging whether the snapshot created for the OpenStack instance to be backed up is a first snapshot, if so, determining the snapshot as effective backup data to be copied, and executing B4; if not, executing B42;
b42, calling a Ceph API interface, obtaining a difference increment data range of the current snapshot compared with the previous snapshot, wherein the difference data range comprises a starting address and a length in an OpenStack instance RBD source volume, extracting the difference increment data in the range, and determining the difference increment data as the effective backup data to be copied.
As shown in fig. 3, a mapping relationship diagram of the transmission of the valid backup data fragments at the source end and the target end is shown.
In the present invention, the data fragmentation mentioned in step B3 is to divide the RBD source volume of the entire OpenStack backup instance into multiple fragments, and distinguish different fragments by identifying the start address and the end address of each fragment in the RBD source volume.
Optionally, the number of the fragments may be flexibly set, for example, the number of the CPU cores in the OpenStack instance may be set, that is, the fragment data to be transmitted may be uniformly distributed to different CPUs for parallel processing, and if the priority of the front-end service is guaranteed, the number of the fragments may be set to be reduced.
In the invention, each process in step B5 corresponds to a certain data fragment to be transmitted, and processes a data transmission task, where the process content includes a start address and an end address of the fragment in an OpenStack instance RBD source volume, a target end Ceph storage RBD backup volume, data to be transmitted in the fragment, and a currently transmitted data location address.
The data to be transmitted in each slice refers to the valid backup data calculated in step B3.
Optionally, the start-stop addresses of the segments are independent from each other, and the data transmission processes of the segments are not affected by each other.
Fig. 4 is a schematic diagram illustrating breakpoint continuous transmission of effective backup data transmission.
In the invention, when each process in step B5 performs fragmented data transmission, a variable current _ position is set to record the position address of the data to be transmitted currently in the OpenStack instance block storage, and if transmission is interrupted due to network environment fluctuation, after the network is restored, retransmission from the fragmented start address is not required, and the breakpoint position marked by the variable current _ position can be obtained to continue data transmission.
Fig. 5 is a flowchart of a recovery method for OpenStack backend storage based on Ceph, as shown in fig. 5, including the following steps:
r1, setting a recovery target instance parameter;
r2, selecting a snapshot point to be restored;
r3, calling a Ceph API interface, comparing the difference data with the previous snapshot in sequence from the backup point to be restored, and calculating effective restoration data;
r4, calling OpenStack API, and creating a recovery target instance;
r5, transmitting the valid data to the recovery target instance.
In the present invention, the recovery target instance parameters mentioned in step R1 include OpenStack platform information, instance metadata configuration information, and RBD recovery target volume.
Fig. 6 is a schematic diagram illustrating obtaining valid recovery data according to an embodiment of the present invention.
The backup snappoints in the present invention are differential incremental data based on a previous snappoint.
In the present invention, before performing the recovery step, it is necessary to calculate the data information of the source volume corresponding to the snapshot point time at this time, that is, the valid recovery data mentioned in step R3.
Specifically, the step R3 of calculating valid recovery data further includes:
r31, sequentially retrieving each data block corresponding to the snapshot point to be restored from the starting address to the ending address;
r32, calling a Ceph API interface, and comparing the difference data with the previous snapshot in sequence;
if a data change is retrieved, then R33 is executed;
if the first snapshot point is traced back, and no data change is retrieved yet, executing R34;
r33, stopping the backtracking comparison of the previous snapshot, and marking the newer data corresponding to the data block as valid recovery data;
r34, this data block is marked as invalid data.
In summary, according to the backup recovery method and device for the OpenStack virtualization platform based on Ceph storage, when performing backup protection on the RBD source volume of the OpenStack virtualization platform instance, the difference incremental data of the snapshot point created each time based on the previous snapshot can be calculated, effective backup data can be obtained, the transmission amount of the backup data can be reduced, and the transmission efficiency of the backup data can be improved. When recovering, effective recovery data can be calculated, the transmission quantity and recovery time of the recovery data are greatly reduced, and network bandwidth resources are saved.
Finally, it should be noted that: although the present invention has been described in detail with reference to the foregoing embodiments, it will be apparent to those skilled in the art that changes may be made in the embodiments and/or equivalents thereof without departing from the spirit and scope of the invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (7)
1. The backup method of the OpenStack virtualization platform based on the Ceph storage is characterized by comprising the following steps of: the method comprises the following steps:
b1, obtaining a backup task, and determining a to-be-backed-up example in the OpenStack virtualization platform corresponding to the backup task and backing up target end Ceph platform information;
b2, calling an OpenStack API, and creating a snapshot for the to-be-backed-up instance;
b3, slicing the effective backup data to be copied;
b4, determining effective backup data to be copied to a target Ceph storage;
b5, generating a plurality of processes according to the number of the fragments, and processing the transmission of each data in parallel;
b6, calling a Ceph storage bottom layer API interface, and transmitting the backup data to the target Ceph block storage.
2. The method for backing up an OpenStack virtualization platform based on Ceph storage according to claim 1, wherein the step B4 further comprises:
b41, judging whether the snapshot created for the OpenStack instance to be backed up is a first snapshot, if so, determining the snapshot as effective backup data to be copied, and executing B4; if not, executing B42;
b42, calling a Ceph API interface, obtaining the difference incremental data of the current snapshot compared with the previous snapshot, and determining the difference incremental data as the effective backup data to be copied.
3. The method for backing up an OpenStack virtualization platform based on Ceph storage according to claim 1, wherein the number of fragments in step B3 can be flexibly set, and can be set according to the number of CPU cores of an OpenStack instance, that is, fragment data to be transmitted can be uniformly distributed to different CPUs for parallel processing.
4. The method for backing up an OpenStack virtualization platform based on Ceph storage according to claim 1, wherein in step B5, each process marks a start address and an end address of fragment data at a source end, a target Ceph storage end, and a currently transmitted data location address, so as to ensure that parallel transmission of fragments is not affected by each other, and when transmission is interrupted due to network environment fluctuation, data transmission can continue from a transmission breakpoint location after the network is recovered.
5. The backup recovery method of the OpenStack virtualization platform based on the Ceph storage is characterized by comprising the following steps of:
r1, setting a recovery target instance parameter;
r2, selecting a snapshot point to be restored;
r3, calling a Ceph API interface, comparing the difference data with the previous snapshot in sequence from the backup point to be restored, and calculating effective restoration data;
r4, calling OpenStack API, and creating a recovery target instance;
r5, transmitting the valid data to the recovery target instance.
6. The recovery method for the OpenStack virtualization platform based on Ceph storage according to claim 5, wherein the valid recovery data mentioned in the step R3 refers to: and comparing the difference data of each data block with the previous snapshot in sequence based on the selected snapshot data of the backup point to be restored, if the data block has the latest change, taking the latest change data to be put into the effective data to be restored, and if the data block is compared to the first snapshot point and still has no change, putting the first snapshot point data into the effective data to be restored to obtain the final effective restoration data.
7. A backup recovery device for OpenStack virtualization platform based on Ceph storage, characterized by being made according to the steps of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111063396.0A CN113806145A (en) | 2021-09-10 | 2021-09-10 | Backup recovery method and device of OpenStack virtualization platform based on Ceph storage |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111063396.0A CN113806145A (en) | 2021-09-10 | 2021-09-10 | Backup recovery method and device of OpenStack virtualization platform based on Ceph storage |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113806145A true CN113806145A (en) | 2021-12-17 |
Family
ID=78895025
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111063396.0A Pending CN113806145A (en) | 2021-09-10 | 2021-09-10 | Backup recovery method and device of OpenStack virtualization platform based on Ceph storage |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113806145A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110716829A (en) * | 2019-10-10 | 2020-01-21 | 浪潮云信息技术有限公司 | Block storage backup method, terminal and storage medium based on Ceph technology |
| US20200409803A1 (en) * | 2019-06-27 | 2020-12-31 | Netapp Inc. | Incremental restore of a virtual machine |
| CN112527562A (en) * | 2020-12-15 | 2021-03-19 | 北京华胜天成科技股份有限公司 | Data backup method and device of distributed storage system and computer equipment |
-
2021
- 2021-09-10 CN CN202111063396.0A patent/CN113806145A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20200409803A1 (en) * | 2019-06-27 | 2020-12-31 | Netapp Inc. | Incremental restore of a virtual machine |
| CN110716829A (en) * | 2019-10-10 | 2020-01-21 | 浪潮云信息技术有限公司 | Block storage backup method, terminal and storage medium based on Ceph technology |
| CN112527562A (en) * | 2020-12-15 | 2021-03-19 | 北京华胜天成科技股份有限公司 | Data backup method and device of distributed storage system and computer equipment |
Non-Patent Citations (1)
| Title |
|---|
| 杨皓森;胡晓勤;黄传波;: "面向OpenStack/Ceph的虚拟机备份系统研究", 计算机系统应用, no. 11, 14 November 2018 (2018-11-14) * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11327799B2 (en) | Dynamic allocation of worker nodes for distributed replication | |
| US11010240B2 (en) | Tracking status and restarting distributed replication | |
| US20200348852A1 (en) | Distributed object replication architecture | |
| US11349915B2 (en) | Distributed replication and deduplication of an object from a source site to a destination site | |
| US11334522B2 (en) | Distributed write journals that support fast snapshotting for a distributed file system | |
| US10817386B2 (en) | Virtual machine recovery method and virtual machine management device | |
| CN102594849B (en) | Data backup and recovery method and device, virtual machine snapshot deleting and rollback method and device | |
| US11741046B2 (en) | Method and apparatus for creating system disk snapshot of virtual machine | |
| US8527990B1 (en) | Systems and methods for migrating virtual machines | |
| AU2011256912B2 (en) | Systems and methods for providing increased scalability in deduplication storage systems | |
| US8224874B2 (en) | Systems and methods for removing unreferenced data segments from deduplicated data systems | |
| US9785643B1 (en) | Systems and methods for reclaiming storage space in deduplicating data systems | |
| WO2019001521A1 (en) | Data storage method, storage device, client and system | |
| US10620871B1 (en) | Storage scheme for a distributed storage system | |
| US8572338B1 (en) | Systems and methods for creating space-saving snapshots | |
| US10795579B2 (en) | Methods, apparatuses, system and computer program products for reclaiming storage units | |
| US8565545B1 (en) | Systems and methods for restoring images | |
| EP3147797A1 (en) | Data management method, node and system for database cluster | |
| EP3449372B1 (en) | Fault-tolerant enterprise object storage system for small objects | |
| US8612702B1 (en) | Systems and methods for performing optimized backups of multiple volumes | |
| CN111143113A (en) | Method, electronic device and computer program product for copying metadata | |
| US9921918B1 (en) | Cloud-based data backup and management | |
| US8595271B1 (en) | Systems and methods for performing file system checks | |
| CN113806145A (en) | Backup recovery method and device of OpenStack virtualization platform based on Ceph storage | |
| CN113626251A (en) | Method, apparatus and computer program product for migrating backup systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |