CN112463450A - Incremental backup management method, system, electronic equipment and storage medium - Google Patents
Incremental backup management method, system, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112463450A CN112463450A CN202011363433.5A CN202011363433A CN112463450A CN 112463450 A CN112463450 A CN 112463450A CN 202011363433 A CN202011363433 A CN 202011363433A CN 112463450 A CN112463450 A CN 112463450A
- Authority
- CN
- China
- Prior art keywords
- backup
- incremental
- deleted
- incremental backup
- parent
- 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.)
- Granted
Links
- 238000007726 management method Methods 0.000 title claims abstract description 37
- 238000012217 deletion Methods 0.000 claims description 58
- 230000037430 deletion Effects 0.000 claims description 58
- 230000001419 dependent effect Effects 0.000 claims description 20
- 238000004590 computer program Methods 0.000 claims description 9
- 238000000034 method Methods 0.000 abstract description 34
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 230000006870 function Effects 0.000 description 14
- 230000008569 process Effects 0.000 description 12
- 230000008676 import Effects 0.000 description 11
- 238000013461 design Methods 0.000 description 9
- 230000007704 transition Effects 0.000 description 6
- 230000009471 action Effects 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 5
- 238000012423 maintenance Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 238000011084 recovery Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 241000700605 Viruses Species 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000008014 freezing Effects 0.000 description 1
- 238000007710 freezing Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000010076 replication Effects 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/1448—Management of the data involved in backup or backup restore
- G06F11/1453—Management of the data involved in backup or backup restore using de-duplication of the data
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
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)
Abstract
The application discloses an incremental backup management method, which comprises the following steps: receiving a backup deleting instruction, and determining incremental backups to be deleted according to the backup deleting instruction; judging whether the incremental backup to be deleted has a sub-backup; if yes, updating the dependency relationship of the child backup according to the dependency relationship of the incremental backup to be deleted and the parent backup, and deleting the incremental backup to be deleted; and if not, deleting the incremental backup to be deleted. The method and the device can reduce the occupation of the incremental backup on the storage resources. The application also discloses an incremental backup management system, an electronic device and a storage medium, which have the beneficial effects.
Description
Technical Field
The present application relates to the field of data storage technologies, and in particular, to a method and a system for incremental backup management, an electronic device, and a storage medium.
Background
Backup is a mechanism for data protection, and is generally used to protect core data or personally important data generated by a business system. A general backup system is usually combined with a hardware storage device to form a backup scheme.
Incremental backups are an implementation of the backup function, and the current deletion logic for incremental backups is: the cloud platform issues an instruction for deleting a certain designated incremental backup, database record query is firstly carried out, if a sub-backup based on the incremental backup to be deleted does not exist, the incremental backup can be successfully deleted, otherwise, the deletion of the incremental backup to be deleted is forbidden. In the above incremental backup deletion scheme, the incremental backup of the existing sub-backup cannot be deleted, so that the incremental backup occupies too much storage resources.
Therefore, how to reduce the occupation of storage resources by incremental backup is a technical problem that needs to be solved by those skilled in the art at present.
Disclosure of Invention
The application aims to provide an incremental backup management method, an incremental backup management system, an electronic device and a storage medium, which can reduce the occupation of incremental backup on storage resources.
In order to solve the above technical problem, the present application provides an incremental backup management method, including:
receiving a backup deleting instruction, and determining incremental backups to be deleted according to the backup deleting instruction;
judging whether the incremental backup to be deleted has a sub-backup;
if yes, updating the dependency relationship of the child backup according to the dependency relationship of the incremental backup to be deleted and the parent backup, and deleting the incremental backup to be deleted;
and if not, deleting the incremental backup to be deleted.
Optionally, if the backup deletion instruction is a non-concurrent incremental backup deletion instruction, updating the dependency relationship of the child backup according to the dependency relationship between the incremental backup to be deleted and the parent backup, including:
querying the first incremental backup and the second incremental backup; the first incremental backup is a parent backup of the incremental backup to be deleted, and the second incremental backup is a child backup of the incremental backup to be deleted;
setting a parent backup ID variable of the second incremental backup as a backup ID of the first incremental backup, and updating a dependency relationship between the first incremental backup and the second incremental backup;
and determining the difference data between the incremental backup to be deleted and the first incremental backup, and importing the difference data into the second incremental backup.
Optionally, if the backup deletion instruction is a concurrent incremental backup deletion instruction, updating the dependency relationship of the child backup according to the dependency relationship between the incremental backup to be deleted and the parent backup, including:
acquiring a backup dependent dictionary; wherein the backup dependency dictionary comprises dependencies between all incremental backups;
setting the incremental backup to be deleted as the current level incremental backup;
querying a parent backup of the current level incremental backup according to the backup dependent dictionary;
judging whether the parent backup of the current level incremental backup is deleted;
if so, setting the father backup of the current hierarchy incremental backup as a new current hierarchy incremental backup, and executing the operation of inquiring the father backup of the current hierarchy incremental backup according to the backup dependent dictionary;
if not, setting the parent backup of the current level incremental backup as a third incremental backup, and updating a fourth incremental backup by using the third incremental backup; and the fourth incremental backup is a sub-backup of the incremental backup to be deleted.
Optionally, updating a fourth incremental backup with the third incremental backup includes:
setting a parent backup ID variable of the fourth incremental backup as a backup ID of the third incremental backup, and updating a dependency relationship between the third incremental backup and the fourth incremental backup;
and determining difference data between the incremental backup to be deleted and the third incremental backup, and importing the difference data into the fourth incremental backup.
Optionally, after deleting the incremental backup to be deleted, the method further includes:
and updating the dependency relationship among all incremental backups in the backup dependency dictionary.
Optionally, after querying a parent backup of the current-level incremental backup according to the backup dependent dictionary, the method further includes:
and if the third incremental backup is not inquired after traversing the backup dependent dictionary, deleting the incremental backup to be deleted.
Optionally, after determining that the incremental backup to be deleted has the child backup, the method further includes:
judging whether the incremental backup to be deleted is the incremental backup which is firstly created by the system; if so, deleting the incremental backup to be deleted; and if not, executing the operation of updating the dependency relationship of the child backup according to the dependency relationship of the incremental backup to be deleted and the parent backup.
The present application further provides an incremental backup management system, including:
the to-be-deleted incremental backup determining module is used for receiving a backup deleting instruction and determining to-be-deleted incremental backups according to the backup deleting instruction;
the sub-backup judging module is used for judging whether the incremental backup to be deleted has a sub-backup;
the first deleting module is used for updating the dependency relationship of the child backup according to the dependency relationship between the incremental backup to be deleted and the parent backup and deleting the incremental backup to be deleted if the incremental backup to be deleted has the child backup;
and the second deleting module is used for deleting the incremental backup to be deleted if the incremental backup to be deleted does not have the child backup.
The application also provides a storage medium, on which a computer program is stored, and the computer program realizes the steps executed by the incremental backup management method when executed.
The application also provides an electronic device, which comprises a memory and a processor, wherein the memory stores a computer program, and the processor realizes the steps executed by the incremental backup management method when calling the computer program in the memory.
The application provides an incremental backup management method, which comprises the following steps: receiving a backup deleting instruction, and determining incremental backups to be deleted according to the backup deleting instruction; judging whether the incremental backup to be deleted has a sub-backup; if yes, updating the dependency relationship of the child backup according to the dependency relationship of the incremental backup to be deleted and the parent backup, and deleting the incremental backup to be deleted; and if not, deleting the incremental backup to be deleted.
After receiving the backup deleting instruction, the method and the device determine the incremental backup to be deleted according to the backup deleting instruction. And if the incremental backup to be deleted comprises the child backup, updating the dependency relationship of the child backup according to the dependency relationship between the incremental backup to be deleted and the parent backup. When the dependency relationship of the child backup is updated, the parent backup ID of the child backup may be updated from the incremental backup to be deleted to the parent backup. After the dependency relationship of the sub-backups is updated, deleting the incremental backup to be deleted does not cause storage abnormity, so that the method and the device can delete the incremental backup of the existing sub-backups, and reduce the occupation of the incremental backup on storage resources. The application also provides an incremental backup management system, an electronic device and a storage medium, which have the beneficial effects and are not repeated herein.
Drawings
In order to more clearly illustrate the embodiments of the present application, the drawings needed for the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained by those skilled in the art without inventive effort.
Fig. 1 is a flowchart of an incremental backup management method according to an embodiment of the present application;
fig. 2 is a flowchart of a backup management method based on a multi-architecture distributed cloud platform according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an incremental backup management system according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a flowchart of an incremental backup management method according to an embodiment of the present disclosure.
The specific steps may include:
s101: receiving a backup deleting instruction, and determining incremental backups to be deleted according to the backup deleting instruction;
the embodiment can be applied to a multi-architecture distributed cloud platform based on Openstack, which is an open source cloud platform software technology, provides an operating platform and a tool set for deploying a cloud, is a cloud platform for comprehensively providing virtualized computing service, storage service and network service for users, has a reliable cloud deployment scheme and good expansibility, and is an operating system in the cloud computing era. The multi-architecture distributed cloud platform can be provided with a backup system for data backup, one of the most important functions of the backup system is timeline version freezing and backtracking, and an important design idea is a design around recovery. Backup copies data from one node, one system to another node, and the other system, thereby avoiding the possibility that hardware and software have problems in the same period; backup systems typically add a high level of redundancy configuration, or redundancy replication, or low cost arithmetic redundancy data distribution to the data store. The backup system further avoids the problems of data loss, addition, modification and the like caused by various intentional or unintentional data reading and writing actions (such as manual operation, system faults, software defects, hacker intrusion, viruses, natural disasters and the like) through time versioning and spatial redundancy distribution. When the backup system software has problems, the data can be restored back through a certain flow. After a business system has a problem, the multiple backups can be independently restored in a selected database table or a certain 1 file; if the data adopts a mixed cloud mode, the data can be restored to the business system in an extremely short time.
Distributed storage is used as a supporting scheme for backing up a back-end system, and after the OpenStack cloud platform is docked, the implemented incremental backup native logic is as follows: (1) when the incremental backup base _1 is created at the 1 st time, the incremental backup base _1 is automatically converted into full backup, a temporary snapshot a and a base data volume of the cloud hard disk at the current moment are generated, and a snapshot a of the cloud hard disk (only the name of the cloud hard disk is the same as that of the snapshot a, but the meaning of the cloud hard disk is different from that of the snapshot a), and the cloud platform generates a unique ID number in the current cloud platform for the incremental backup base _1 in the creating process: bak _1. id; (2) when an incremental backup base _2 is created at the 2 nd time, a backup is created based on the incremental backup created at the 1 st time, firstly, a temporary snapshot B of the cloud hard disk at the current moment is generated, a distributed storage bottom layer command is utilized to export the data difference between the cloud hard disk snapshot B and the snapshot a into a temporary file diff _ a _ B, the difference data in the diff _ a _ B is immediately imported into a base volume, and a snapshot B (the meaning of which is the same as 1) of the base volume is synchronously generated, during the creation process, the cloud platform generates a unique ID number in the current cloud platform for the incremental backup base _ 2: bak _2.ID, and meanwhile, generating a father ID record, wherein the father ID number is bak _1.ID, which indicates that the incremental backup bak _2 to be deleted is generated based on bak _ 1; (3) when the incremental backup base _3 is created for the 3 rd time, the incremental backup created for the 2 nd time is performed, firstly, a temporary snapshot C of the cloud hard disk at the current moment is generated, a distributed storage bottom layer command is used for exporting data difference between the cloud hard disk snapshot C and the snapshot B into a temporary file diff _ B _ C, the difference data in the diff _ B _ C is immediately imported into a base volume, the snapshot C of the base volume is synchronously generated (the meaning is the same as the two steps), and the cloud platform generates a unique ID number in the current cloud platform for the incremental backup base _3 in the creation process: bak _3.ID, and meanwhile, generating a father ID record, wherein the father ID number is bak _2.ID, which indicates that the incremental backup bak _3 to be deleted is generated based on bak _ 2; the subsequent multiple incremental backup creation process is the same as (2) (3).
After receiving the backup deletion instruction, the embodiment may analyze the backup deletion instruction, and determine the incremental backup to be deleted corresponding to the backup deletion instruction according to the analysis result. In this embodiment, the number of incremental backups to be deleted is not limited, and one backup deletion instruction may delete any number of incremental backups to be deleted.
S102: judging whether the incremental backup to be deleted has a sub-backup; if yes, entering S103; if not, entering S104;
in this step, it may be determined whether a child backup exists in the incremental backup to be deleted by querying the database, where the parent backup is a parent backup of the incremental backup to be deleted, the child backup is a child backup of the incremental backup to be deleted, and the child backup stores difference data, where the difference data is difference data between a snapshot corresponding to the child backup and a snapshot corresponding to the incremental backup to be deleted. If the incremental backup to be deleted does not have the sub-backup, the incremental sub-backup to be deleted can be directly deleted; if the incremental backup to be deleted has the sub backup, the backup system will output abnormal refusal deletion when the backup system inquires the sub backup depending on the incremental backup to be deleted when the incremental backup to be deleted is directly deleted. In this embodiment, the dependency relationship of the child backup is updated according to the dependency relationship between the incremental backup to be deleted and the parent backup through the operation of S103, so that the parent backup of the child backup is updated to the parent backup of the incremental backup to be deleted, so that the child backup and the incremental backup to be deleted do not have a dependency relationship, and the incremental backup can be deleted.
As a possible implementation manner, after determining that the incremental backup to be deleted has the child backup, it may also be determined whether the incremental backup to be deleted is an incremental backup that is created by the system for the first time; if so, deleting the incremental backup to be deleted; if not, the operation of updating the dependency relationship of the child backup according to the dependency relationship between the incremental backup to be deleted and the parent backup in the step S103 is executed.
S103: updating the dependency relationship of the child backup according to the dependency relationship between the incremental backup to be deleted and the parent backup, and deleting the incremental backup to be deleted;
the method comprises the following steps that the step is established on the basis that the incremental backup to be deleted has the child backup, and the parent backup of the child backup can be updated to the parent backup of the incremental backup to be deleted from the incremental backup to be deleted according to the dependency relationship between the incremental backup to be deleted and the parent backup. After updating the dependency relationship of the child backup, the embodiment may delete the incremental backup to be deleted.
The above process is illustrated by way of example: incremental backup B1-B2-B3-B4 is sequentially created for the cloud hard disk v1, B1 is a parent backup of B2, B2 is a parent backup of B3, and B3 is a parent backup of B4. If B4 is deleted, firstly, whether a child backup with the parent backup ID of B4 exists is inquired through a database, and if not, the incremental backup B4 can be directly deleted; if B3 is deleted, the parent backup ID of incremental backup B4 can be B3 through database queries, at which point the exception is thrown directly because B3 has child backup B4, which prohibits deletion. By the processing method of the embodiment, before the B3 is deleted, the parent backup of the B4 can be updated to B2, and at this time, the B3 deletion will not be abnormal, so that the B3 can be deleted. In a large cloud platform, a backup system generally has a scheme design for performing backup at regular time, and in order to save and reasonably utilize storage resources, a timing design for creating incremental backups is generally adopted, so that the incremental backups accumulated for a long time are more in quantity, and a plurality of intermediate incremental backups are not necessarily used, so that the query is troublesome. From the convenience of use, a user generally wants to keep the latest backup data and the data for guaranteeing the historical backup is also available during recovery, and incremental backups created in other periods can be merged and deleted according to actual requirements. The design scheme of the backup management function based on the multi-architecture distributed cloud platform can enrich the management mechanism of cloud platform backup data protection and improve the convenience and reliability of the cloud platform.
S104: and deleting the incremental backup to be deleted.
After receiving the backup deletion instruction, the embodiment determines the incremental backup to be deleted according to the backup deletion instruction. And if the incremental backup to be deleted comprises the child backup, updating the dependency relationship of the child backup according to the dependency relationship between the incremental backup to be deleted and the parent backup. When the dependency relationship of the child backup is updated, the parent backup ID of the child backup may be updated from the incremental backup to be deleted to the parent backup. After the dependency relationship of the sub-backup is updated, deleting the incremental backup to be deleted does not cause storage abnormity, so that the embodiment can delete the incremental backup of the existing sub-backup, and reduce the occupation of the incremental backup on storage resources.
As a further description of the embodiment corresponding to fig. 1, if the backup deletion instruction received in S101 is a non-concurrent incremental backup deletion instruction, incremental backups are deleted one by one in the backup system, that is, the deletion operation of the next incremental backup is performed after the incremental backup to be deleted is deleted. Therefore, when a non-concurrent incremental backup deletion instruction is received, the embodiment may update the dependency relationship of the child backup in the following ways, including:
step A1: querying the first incremental backup and the second incremental backup;
the first incremental backup is a parent backup of the incremental backup to be deleted, and the second incremental backup is a child backup of the incremental backup to be deleted;
step A2: setting a parent backup ID variable of the second incremental backup as a backup ID of the first incremental backup, and updating a dependency relationship between the first incremental backup and the second incremental backup;
in this step, the parent backup ID variable of the second incremental backup is set as the backup ID of the first incremental backup, so that the parent backup of the second incremental backup is adjusted from the incremental backup to be deleted to the first incremental backup, that is, the dependency relationship between the first incremental backup and the second incremental backup is updated.
Step A3: and determining difference data between the incremental backup to be deleted and the first incremental backup, and importing the difference data into the second incremental backup.
In order to avoid the loss of the difference data caused by deleting the incremental backup to be deleted, the difference data of the incremental backup to be deleted and the first incremental backup is determined first, and the difference data is imported into the second incremental backup, so that the difference data of the incremental backup to be deleted and the first incremental backup is stored in the second incremental backup.
The embodiment provides an implementation mode for deleting incremental backups in a non-concurrent incremental backup deletion scene, and the method comprises the steps of firstly recording parent backup IDs and child backup IDs of the incremental backups to be deleted; if the sub-backup ID does not exist, the incremental backup to be deleted is directly deleted; and if so, assigning the parent backup ID to the parent backup ID variable of the child backup, and updating the database. Exporting the difference data diff _ data export between the incremental backup to be deleted and the parent backup thereof to a transition temporary file, importing the diff _ data import to the child backup thereof, and generating a new child backup, so that when the new child backup is used for restoring, the intermediate data is not lost, and then the incremental backup to be deleted is directly deleted.
In the above embodiment, the parent backup ID variable of the second incremental backup is set as the backup ID of the first incremental backup, and the dependency relationship of the first incremental backup is updated to the second incremental backup, so that the deletion operation of the incremental backup to be deleted can be realized. The embodiment also leads the difference data between the incremental backup to be deleted and the first incremental backup into the second incremental backup, so that the intermediate data is not lost. After the relevant operations of steps A1-A3 are performed, the incremental backup to be deleted can be deleted directly.
As a further description of the embodiment corresponding to fig. 1, if the backup deletion instruction received in S101 is a concurrent incremental backup deletion instruction, the incremental backup is concurrently deleted in the backup system, that is, there may be an operation in which a plurality of incremental backups to be deleted are deleted simultaneously. Therefore, when a concurrent incremental backup deletion instruction is received, the embodiment may update the dependency relationship of the child backup in the following ways, including:
step B1: acquiring a backup dependent dictionary;
the backup dependency dictionary comprises dependency relationships among all incremental backups, and the dependency relationships are relationships among parent backups and child backups.
Step B2: setting the incremental backup to be deleted as the current level incremental backup;
step B3: querying a parent backup of the current level incremental backup according to the backup dependent dictionary;
step B4: judging whether the parent backup of the current level incremental backup is deleted; if yes, go to step B5; if not, go to step B6;
this step is used to query whether the parent backup of the current hierarchical incremental backup is deleted, and if so, the parent backup of the parent backup is continuously queried upwards through step B5.
Step B5: setting the parent backup of the current level incremental backup as a new current level incremental backup, and proceeding to step B3;
step B6: setting a parent backup of a current level incremental backup as a third incremental backup, and updating a fourth incremental backup by using the third incremental backup;
and the fourth incremental backup is a sub-backup of the incremental backup to be deleted. Specifically, the process of updating the fourth incremental backup by using the third incremental backup includes: setting a parent backup ID variable of the fourth incremental backup as a backup ID of the third incremental backup, and updating a dependency relationship between the third incremental backup and the fourth incremental backup; and determining the difference data between the incremental backup to be deleted and the third incremental backup, importing the difference data into the fourth incremental backup so as to ensure that the intermediate data is not lost, and then directly deleting the incremental backup to be deleted.
After step B6 is executed, the present embodiment may delete the incremental backup to be deleted, and update the dependency relationships between all the incremental backups in the backup dependency dictionary.
Further, after querying a parent backup of the current-level incremental backup according to the backup dependent dictionary, if the third incremental backup (i.e., the parent backup of the current-level incremental backup that is not deleted) is not queried after traversing the backup dependent dictionary, the incremental backup to be deleted may be deleted.
The above embodiments provide a scheme for deleting an incremental backup in a concurrent incremental backup deletion scenario. Under the concurrent deletion scene, the existing risk problem is as follows: when the intermediate incremental backups are deleted in batches, the parent backup of the current backup to be deleted may be deleted, and if the current incremental backup to be deleted has a child backup and is not deleted, the newly assigned parent backup ID of the child backup will become meaningless. To solve the above problem, the present embodiment provides the following mechanism to ensure that the dependent corresponding parent backup ID can be found by the undeleted incremental backup to show the dependency relationship, and the implementation logic of this mechanism is as follows: constructing an incremental backup ID maintenance FUNCTION Bak _ ID _ FUNCTION, inquiring the association relation between each backup ID and the parent backup ID through a database, and storing in a backup dependency dictionary form, wherein a key-value storage form is as follows: { backup ID: parent backup ID }. The corresponding parent backup ID value can be found from the recorded ID value of each incremental backup. Before deleting the incremental backup to be deleted, calling a current FUNCTION Bak _ ID _ FUNCTION, and updating and saving the current FUNCTION Bak _ ID _ FUNCTION into the backup dependent dictionary ID _ Dict. When a plurality of incremental backups are deleted, if the parent backup of the incremental backup to be deleted is deleted, the parent backup ID of the child backup is updated to the parent backup ID value of the parent backup of the incremental backup to be deleted or the parent backup ID value of the previous level until the parent backup ID value is found. After finding out the parent backup, the ID value of the parent backup can be updated and stored in a database, then the diff _ data export of the difference data between the current backup and the newly inquired parent backup is exported to a transition temporary file, and the diff _ data import is imported to the child backup to obtain a new child backup, so that when the new child backup is used for restoring, the middle data is not lost, and then the deletion action of the incremental backup to be deleted is started. If the parent backup and the child backup of the incremental backup to be deleted both exist, the backup ID of the parent backup is directly assigned to the parent ID variable of the child backup, and then the new dependency relationship is updated to the database. And then exporting the difference data diff _ data export between the incremental backup to be deleted and the parent backup thereof to a transition temporary file, importing the diff _ data import to the child backup thereof, and generating a new child backup, thereby ensuring that the intermediate data is not lost when the new child backup is used for recovery.
The flow described in the above embodiment is explained below by an embodiment in practical use. Referring to fig. 2, fig. 2 is a flowchart of a backup management method based on a multi-architecture distributed cloud platform according to an embodiment of the present disclosure, where the embodiment is applicable to multiple cloud platform infrastructures such as X86, ARM, MIPS, and the process is as follows: a user pre-issues a request for deleting incremental backup; and judging whether the current scene belongs to a concurrent deletion scene. If the current incremental backup is not the concurrent deletion scene, judging whether a sub-backup exists in the current incremental backup to be deleted (namely the incremental backup to be deleted); if the sub backup does not exist, deleting the current incremental backup; if the child backup exists, updating the parent ID value of the child backup to the parent backup ID value of the incremental backup to be deleted currently, exporting diff _ data export of difference data between the current backup and the parent backup to a temporary file, importing diff _ data import to the child backup to obtain a new child backup, and finally deleting the current incremental backup.
And if the current incremental backup is a concurrent deletion scene, calling an incremental backup ID maintenance function to obtain a maintenance record ID _ Dict between the parent backup ID and the child backup ID, and judging whether the current incremental backup has the child backup. And if the sub backup does not exist, deleting the current incremental backup. If the child backup exists, judging whether a parent backup of the current incremental backup exists; if the parent backup exists, updating the parent ID value of the child backup to the parent backup ID value of the current incremental backup to be deleted, exporting the difference data diff _ data export between the current backup and the latest parent backup inquired by the current backup to a temporary file, importing the diff _ data import to the child backup to obtain a new child backup, and finally deleting the current incremental backup. If the parent backup of the current incremental backup does not exist, executing the following cycle operation:
step C1, acquiring a parent backup ID value of a parent backup of the incremental backup to be deleted currently in the ID _ Dict dictionary;
step C2, whether the latest parent backup inquired currently exists; if yes, entering step C4, otherwise entering step C3;
step C3, acquiring the father backup ID value of the current latest father backup, searching the father backup ID according to the current latest father backup ID value, and entering the step C2;
step C4, the parent ID value of the child backup is updated to the parent ID value of the current incremental backup to be deleted, the diff _ data export of the difference data between the current backup and the latest parent backup queried by the current backup is exported to a temporary file, the diff _ data import is imported to the child backup to obtain the new child backup, and finally the current incremental backup is deleted.
The corresponding embodiment of fig. 2 is premised on: the current backup storage back end supports incremental backup, and the cloud platform has a plurality of incremental backups based on the same source cloud hard disk. The embodiment corresponding to fig. 2 provides a new cloud platform cloud hard disk backup management function scheme design, and the backup deletion management function is optimally designed for the back end of the storage backup, so that any single or batch incremental backup is supported to be deleted, and the integrity of data restored based on the current backup time is not affected.
And initiating an incremental backup deletion request after a user logs in the cloud platform, and executing incremental backup deletion operations of a non-concurrent deletion scene and a concurrent deletion scene according to the incremental backup deletion scene.
In a non-concurrent deletion scenario, i.e., when any one of the intermediate incremental backups is deleted, the operation implements logic: recording a parent backup ID value and a child backup ID of a current incremental backup in advance, updating the parent ID value of the child backup into a parent backup ID value of the current incremental backup to be deleted, updating the parent ID value of the current incremental backup into a database, exporting diff _ data export of difference data between the current backup and the parent backup to a transition temporary file, importing the diff _ data import into the child backup, and generating a new child backup.
In a concurrent deletion scenario, i.e., when multiple incremental backups are deleted simultaneously, the operation implements the logic: calling an incremental backup ID maintenance FUNCTION Bak _ ID _ FUNCTION, saving the ID value dependency relationship among all incremental backups into a dictionary ID _ Dict, and then starting to delete the current incremental backup: if the current incremental backup does not contain the sub backup, directly deleting the current incremental backup, and then finishing the deleting; if the current incremental backup has a child backup, further judging whether a parent backup which needs to delete the current incremental backup exists: if the difference data exists, the ID value is directly assigned to a parent ID variable of a child backup based on the current incremental backup to be deleted, then the difference data diff _ data export between the current backup and the parent backup is updated to a database, then the diff _ data import is exported to a transition temporary file, the diff _ data import is imported to the child backup, and a new child backup is generated, so that when the new child backup is used for restoring, the intermediate data is not lost, and finally the restoration is finished; if not, based on the parent backup ID value of the record of the incremental backup to be deleted currently, the ID-Dict dictionary is used for obtaining the parent backup ID value of the parent backup of the incremental backup to be deleted currently, and further judging whether the parent backup of the incremental backup to be deleted currently exists or not, if not, the value of the ID-Dict dictionary is continuously taken until a existed father backup is found, the ID value of the father backup is assigned to the father ID variable of the son backup which needs to delete the incremental backup at present, then updating the data into the database, continuously exporting the difference data diff _ data export between the current backup and the latest queried parent backup to a transition temporary file, and imports diff _ data import into its child backup, generates a new child backup, therefore, when the new sub backup is used for recovery, the intermediate data is not lost, and then the current incremental backup is deleted.
The embodiment provides a core implementation logic for the management process and the data operation during deletion, and optimization based on native logic can support deletion of any single or batch incremental backup without affecting the integrity of data restored based on the current backup time. The embodiment provides a design of a backup management mechanism of a multi-architecture cloud platform, and provides a framework design idea that the multi-architecture cloud platform supports backup cloud disk management of the existing backup. The method has the advantages of openness and optimized design based on the native interface.
Referring to fig. 3, fig. 3 is a schematic structural diagram of an incremental backup management system according to an embodiment of the present application;
the system may include:
the incremental backup to be deleted determining module 100 is configured to receive a backup deletion instruction, and determine an incremental backup to be deleted according to the backup deletion instruction;
a sub-backup judging module 200, configured to judge whether a sub-backup exists in the incremental backup to be deleted;
a first deleting module 300, configured to, if the incremental backup to be deleted has a child backup, update a dependency relationship of the child backup according to a dependency relationship between the incremental backup to be deleted and a parent backup, and delete the incremental backup to be deleted;
a second deleting module 400, configured to delete the incremental backup to be deleted if there is no child backup for the incremental backup to be deleted.
After receiving the backup deletion instruction, the embodiment determines the incremental backup to be deleted according to the backup deletion instruction. And if the incremental backup to be deleted comprises the child backup, updating the dependency relationship of the child backup according to the dependency relationship between the incremental backup to be deleted and the parent backup. When the dependency relationship of the child backup is updated, the parent backup ID of the child backup may be updated from the incremental backup to be deleted to the parent backup. After the dependency relationship of the sub-backup is updated, deleting the incremental backup to be deleted does not cause storage abnormity, so that the embodiment can delete the incremental backup of the existing sub-backup, and reduce the occupation of the incremental backup on storage resources.
Further, the first deletion module 300 includes:
the non-concurrent deletion processing unit is used for inquiring the first incremental backup and the second incremental backup if the backup deletion instruction is a non-concurrent incremental backup deletion instruction; the first incremental backup is a parent backup of the incremental backup to be deleted, and the second incremental backup is a child backup of the incremental backup to be deleted; the second incremental backup is also used for setting a parent backup ID variable of the second incremental backup as a backup ID of the first incremental backup and updating the dependency relationship between the first incremental backup and the second incremental backup; and the incremental backup management module is further used for determining the difference data between the incremental backup to be deleted and the first incremental backup, and importing the difference data into the second incremental backup.
Further, the first deletion module 300 includes:
the concurrent deletion processing unit is configured to, if the backup deletion instruction is a concurrent incremental backup deletion instruction, update the dependency relationship of the child backup according to the dependency relationship between the incremental backup to be deleted and the parent backup, and includes: the method is also used for obtaining a backup dependent dictionary; wherein the backup dependency dictionary comprises dependencies between all incremental backups; the incremental backup to be deleted is set as the current hierarchy incremental backup; the backup dependency dictionary is also used for inquiring a parent backup of the current level incremental backup according to the backup dependency dictionary; the method is also used for judging whether the parent backup of the current level incremental backup is deleted; if so, setting the father backup of the current hierarchy incremental backup as a new current hierarchy incremental backup, and executing the operation of inquiring the father backup of the current hierarchy incremental backup according to the backup dependent dictionary; if not, setting the parent backup of the current level incremental backup as a third incremental backup, and updating a fourth incremental backup by using the third incremental backup; and the fourth incremental backup is a sub-backup of the incremental backup to be deleted.
Further, the process of updating the fourth incremental backup by the concurrent deletion processing unit using the third incremental backup includes:
setting a parent backup ID variable of the fourth incremental backup as a backup ID of the third incremental backup, and updating a dependency relationship between the third incremental backup and the fourth incremental backup;
and determining difference data between the incremental backup to be deleted and the third incremental backup, and importing the difference data into the fourth incremental backup.
Further, the method also comprises the following steps:
and the dictionary updating module is used for updating the dependency relationship among all the incremental backups in the backup dependency dictionary after the incremental backups to be deleted are deleted.
Further, the method also comprises the following steps:
and the backup deleting module is used for deleting the incremental backup to be deleted if the third incremental backup is not inquired after traversing the backup dependent dictionary after inquiring the parent backup of the current level incremental backup according to the backup dependent dictionary.
Further, the method also comprises the following steps:
the first-time creation incremental backup processing module is used for judging whether the incremental backup to be deleted is the incremental backup which is created for the first time by the system or not after judging that the incremental backup to be deleted has the sub-backup; if so, deleting the incremental backup to be deleted; and if not, executing the operation of updating the dependency relationship of the child backup according to the dependency relationship of the incremental backup to be deleted and the parent backup.
Since the embodiment of the system part corresponds to the embodiment of the method part, the embodiment of the system part is described with reference to the embodiment of the method part, and is not repeated here.
The present application also provides a storage medium having a computer program stored thereon, which when executed, may implement the steps provided by the above-described embodiments. The storage medium may include: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The application further provides an electronic device, which may include a memory and a processor, where the memory stores a computer program, and the processor may implement the steps provided by the foregoing embodiments when calling the computer program in the memory. Of course, the electronic device may also include various network interfaces, power supplies, and the like.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. For the system disclosed by the embodiment, the description is relatively simple because the system corresponds to the method disclosed by the embodiment, and the relevant points can be referred to the method part for description. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (10)
1. An incremental backup management method, comprising:
receiving a backup deleting instruction, and determining incremental backups to be deleted according to the backup deleting instruction;
judging whether the incremental backup to be deleted has a sub-backup;
if yes, updating the dependency relationship of the child backup according to the dependency relationship of the incremental backup to be deleted and the parent backup, and deleting the incremental backup to be deleted;
and if not, deleting the incremental backup to be deleted.
2. The incremental backup management method according to claim 1, wherein if the backup deletion instruction is a non-concurrent incremental backup deletion instruction, updating the dependency relationship of the child backup according to the dependency relationship between the incremental backup to be deleted and the parent backup, including:
querying the first incremental backup and the second incremental backup; the first incremental backup is a parent backup of the incremental backup to be deleted, and the second incremental backup is a child backup of the incremental backup to be deleted;
setting a parent backup ID variable of the second incremental backup as a backup ID of the first incremental backup, and updating a dependency relationship between the first incremental backup and the second incremental backup;
and determining the difference data between the incremental backup to be deleted and the first incremental backup, and importing the difference data into the second incremental backup.
3. The incremental backup management method according to claim 1, wherein if the backup deletion instruction is a concurrent incremental backup deletion instruction, updating the dependency relationship of the child backup according to the dependency relationship between the incremental backup to be deleted and the parent backup, including:
acquiring a backup dependent dictionary; wherein the backup dependency dictionary comprises dependencies between all incremental backups;
setting the incremental backup to be deleted as the current level incremental backup;
querying a parent backup of the current level incremental backup according to the backup dependent dictionary;
judging whether the parent backup of the current level incremental backup is deleted;
if so, setting the father backup of the current hierarchy incremental backup as a new current hierarchy incremental backup, and executing the operation of inquiring the father backup of the current hierarchy incremental backup according to the backup dependent dictionary;
if not, setting the parent backup of the current level incremental backup as a third incremental backup, and updating a fourth incremental backup by using the third incremental backup; and the fourth incremental backup is a sub-backup of the incremental backup to be deleted.
4. The incremental backup management method of claim 3 wherein updating a fourth incremental backup with said third incremental backup comprises:
setting a parent backup ID variable of the fourth incremental backup as a backup ID of the third incremental backup, and updating a dependency relationship between the third incremental backup and the fourth incremental backup;
and determining difference data between the incremental backup to be deleted and the third incremental backup, and importing the difference data into the fourth incremental backup.
5. The incremental backup management method according to claim 3, further comprising, after deleting the to-be-deleted incremental backup:
and updating the dependency relationship among all incremental backups in the backup dependency dictionary.
6. The incremental backup management method of claim 3, further comprising, after querying a parent backup of a current hierarchical incremental backup from the backup dependent dictionary, the step of:
and if the third incremental backup is not inquired after traversing the backup dependent dictionary, deleting the incremental backup to be deleted.
7. The incremental backup management method according to any one of claims 1 to 6, further comprising, after determining that the to-be-deleted incremental backup has a child backup:
judging whether the incremental backup to be deleted is the incremental backup which is firstly created by the system; if so, deleting the incremental backup to be deleted; and if not, executing the operation of updating the dependency relationship of the child backup according to the dependency relationship of the incremental backup to be deleted and the parent backup.
8. An incremental backup management system, comprising:
the to-be-deleted incremental backup determining module is used for receiving a backup deleting instruction and determining to-be-deleted incremental backups according to the backup deleting instruction;
the sub-backup judging module is used for judging whether the incremental backup to be deleted has a sub-backup;
the first deleting module is used for updating the dependency relationship of the child backup according to the dependency relationship between the incremental backup to be deleted and the parent backup and deleting the incremental backup to be deleted if the incremental backup to be deleted has the child backup;
and the second deleting module is used for deleting the incremental backup to be deleted if the incremental backup to be deleted does not have the child backup.
9. An electronic device comprising a memory in which a computer program is stored and a processor which, when invoked by the computer program in the memory, carries out the steps of the incremental backup management method according to any one of claims 1 to 7.
10. A storage medium having stored thereon computer-executable instructions which, when loaded and executed by a processor, carry out the steps of the incremental backup management method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011363433.5A CN112463450B (en) | 2020-11-27 | 2020-11-27 | Incremental backup management method, system, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011363433.5A CN112463450B (en) | 2020-11-27 | 2020-11-27 | Incremental backup management method, system, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112463450A true CN112463450A (en) | 2021-03-09 |
| CN112463450B CN112463450B (en) | 2023-12-22 |
Family
ID=74809036
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011363433.5A Active CN112463450B (en) | 2020-11-27 | 2020-11-27 | Incremental backup management method, system, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112463450B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113238891A (en) * | 2021-03-19 | 2021-08-10 | 浪潮云信息技术股份公司 | Backup deletion method and system based on backup chain |
| CN113535482A (en) * | 2021-07-22 | 2021-10-22 | 华云数据控股集团有限公司 | Cloud backup chain data backup and management method and device, equipment and readable medium |
| CN114817410A (en) * | 2022-06-23 | 2022-07-29 | 心鉴智控(深圳)科技有限公司 | Service data processing method, device, equipment and storage medium |
| WO2023197937A1 (en) * | 2022-04-15 | 2023-10-19 | 中兴通讯股份有限公司 | Data processing method and apparatus, storage medium, and computer program product |
| WO2023236504A1 (en) * | 2022-06-09 | 2023-12-14 | 苏州元脑智能科技有限公司 | Database management method and system, electronic device, and storage medium |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030177149A1 (en) * | 2002-03-18 | 2003-09-18 | Coombs David Lawrence | System and method for data backup |
| US20070185936A1 (en) * | 2006-02-07 | 2007-08-09 | Derk David G | Managing deletions in backup sets |
| CN101477487A (en) * | 2009-01-22 | 2009-07-08 | 上海交通大学 | Multiple incremental files backup and recovery method |
| CN102819536A (en) * | 2011-09-27 | 2012-12-12 | 金蝶软件（中国）有限公司 | Processing method and device of tree type data |
| US20140214767A1 (en) * | 2013-01-30 | 2014-07-31 | Hewlett-Packard Development Company, L.P. | Delta partitions for backup and restore |
| US9235582B1 (en) * | 2013-03-14 | 2016-01-12 | Emc Corporation | Tracking files excluded from backup |
| US20170153951A1 (en) * | 2015-11-30 | 2017-06-01 | Microsoft Technology Licensing, Llc | Incremental synchronous hierarchical system restoration |
| CN106933699A (en) * | 2015-12-30 | 2017-07-07 | 中移(苏州)软件技术有限公司 | A kind of data recovery, snapshot establishment, snapshot delet method and device |
| CN109614051A (en) * | 2018-12-13 | 2019-04-12 | 北京金山云网络技术有限公司 | A kind of method for cleaning of Backup Data, device, electronic equipment and storage medium |
| CN110879762A (en) * | 2019-10-25 | 2020-03-13 | 苏州浪潮智能科技有限公司 | Cloud backup deleting method and locally-stored cloud backup deleting method |
| CN111858159A (en) * | 2020-06-19 | 2020-10-30 | 苏州浪潮智能科技有限公司 | Backup method and system based on chain clone characteristic |
-
2020
- 2020-11-27 CN CN202011363433.5A patent/CN112463450B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030177149A1 (en) * | 2002-03-18 | 2003-09-18 | Coombs David Lawrence | System and method for data backup |
| US20070185936A1 (en) * | 2006-02-07 | 2007-08-09 | Derk David G | Managing deletions in backup sets |
| CN101017453A (en) * | 2006-02-07 | 2007-08-15 | 国际商业机器公司 | Method and system for managing deletions in backup sets |
| CN101477487A (en) * | 2009-01-22 | 2009-07-08 | 上海交通大学 | Multiple incremental files backup and recovery method |
| CN102819536A (en) * | 2011-09-27 | 2012-12-12 | 金蝶软件（中国）有限公司 | Processing method and device of tree type data |
| US20140214767A1 (en) * | 2013-01-30 | 2014-07-31 | Hewlett-Packard Development Company, L.P. | Delta partitions for backup and restore |
| US9235582B1 (en) * | 2013-03-14 | 2016-01-12 | Emc Corporation | Tracking files excluded from backup |
| US20170153951A1 (en) * | 2015-11-30 | 2017-06-01 | Microsoft Technology Licensing, Llc | Incremental synchronous hierarchical system restoration |
| CN106933699A (en) * | 2015-12-30 | 2017-07-07 | 中移(苏州)软件技术有限公司 | A kind of data recovery, snapshot establishment, snapshot delet method and device |
| CN109614051A (en) * | 2018-12-13 | 2019-04-12 | 北京金山云网络技术有限公司 | A kind of method for cleaning of Backup Data, device, electronic equipment and storage medium |
| CN110879762A (en) * | 2019-10-25 | 2020-03-13 | 苏州浪潮智能科技有限公司 | Cloud backup deleting method and locally-stored cloud backup deleting method |
| CN111858159A (en) * | 2020-06-19 | 2020-10-30 | 苏州浪潮智能科技有限公司 | Backup method and system based on chain clone characteristic |
Non-Patent Citations (4)
| Title |
|---|
| 周文瑾;胡晓勤;李自尊;邓亮;: "树形高效数据库备份管理模型", 计算机工程与设计, no. 12, pages 149 - 153 * |
| 曹斌等: "基于过程结构树的流程间差别检测算法", 电子学报, pages 862 - 870 * |
| 程利先;: "浅议中小企业数据备份", 企业技术开发, no. 19, pages 77 - 78 * |
| 肖克辉;倪德明;: "文件系统增量备份策略的形式化描述及实现", 计算机工程与设计, no. 10, pages 217 - 219 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113238891A (en) * | 2021-03-19 | 2021-08-10 | 浪潮云信息技术股份公司 | Backup deletion method and system based on backup chain |
| CN113535482A (en) * | 2021-07-22 | 2021-10-22 | 华云数据控股集团有限公司 | Cloud backup chain data backup and management method and device, equipment and readable medium |
| CN113535482B (en) * | 2021-07-22 | 2024-03-19 | 华云数据控股集团有限公司 | Cloud backup chain data backup method and device, equipment and readable medium |
| WO2023197937A1 (en) * | 2022-04-15 | 2023-10-19 | 中兴通讯股份有限公司 | Data processing method and apparatus, storage medium, and computer program product |
| WO2023236504A1 (en) * | 2022-06-09 | 2023-12-14 | 苏州元脑智能科技有限公司 | Database management method and system, electronic device, and storage medium |
| CN114817410A (en) * | 2022-06-23 | 2022-07-29 | 心鉴智控(深圳)科技有限公司 | Service data processing method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112463450B (en) | 2023-12-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112463450B (en) | Incremental backup management method, system, electronic equipment and storage medium | |
| US10013248B2 (en) | Reducing downtime during upgrades of interrelated components in a database system | |
| RU2429529C2 (en) | Dynamic configuration, allocation and deployment of computer systems | |
| US8548947B2 (en) | Systems and methods for file maintenance | |
| US7676492B2 (en) | Migration of database using serialized objects | |
| US8010962B2 (en) | Infrastructure for the automation of the assembly of schema maintenance scripts | |
| US8121981B2 (en) | Database snapshot management | |
| JP3270216B2 (en) | File name detection method | |
| US7774772B2 (en) | Method and apparatus to perform an application software migration | |
| WO2019109854A1 (en) | Data processing method and device for distributed database, storage medium, and electronic device | |
| CN110427258A (en) | Scheduling of resource control method and device based on cloud platform | |
| Fisun et al. | Query parsing in order to optimize distributed DB structure | |
| US11099837B2 (en) | Providing build avoidance without requiring local source code | |
| CN111078719A (en) | Data recovery method and device, storage medium and processor | |
| CN113792026B (en) | Method and device for deploying database script and computer-readable storage medium | |
| CN116089518A (en) | Data model extraction method and system, terminal and medium | |
| CN114385415A (en) | Method and device for virtual machine to backup across backup storage pools | |
| CN108897569A (en) | The method for cleaning and computer readable storage medium of iOS engineering discarded record | |
| US8630976B2 (en) | Fast search replication synchronization processes | |
| CN108376104B (en) | Node scheduling method and device and computer readable storage medium | |
| JP2010152707A (en) | Backup method of database and database system | |
| CN111694908A (en) | Data storage method, device and storage medium | |
| WO2024078211A1 (en) | Backup method for service cluster instance, recovery method for service cluster instance, and related device | |
| JP3514332B2 (en) | Database backup method | |
| CN116893932A (en) | Resource timing snapshot and backup implementation method based on cloud platform workflow |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |