CN115562911A - Virtual machine data backup method, device, system, electronic equipment and storage medium - Google Patents
Virtual machine data backup method, device, system, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115562911A CN115562911A CN202211560664.4A CN202211560664A CN115562911A CN 115562911 A CN115562911 A CN 115562911A CN 202211560664 A CN202211560664 A CN 202211560664A CN 115562911 A CN115562911 A CN 115562911A
- Authority
- CN
- China
- Prior art keywords
- backup
- virtual machine
- node
- management node
- message
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a virtual machine data backup method, a virtual machine data backup device, a virtual machine data backup system, electronic equipment and a storage medium, and relates to the technical field of cloud platforms. The virtual machine data backup method provided by the application is applied to a cloud platform, the cloud platform comprises a management node and a plurality of computing nodes, and the virtual machine data backup method comprises the following steps: the method comprises the steps that a management node obtains a target computing node corresponding to a virtual machine to be backed up, backup information is created according to a backup task, backup information of a routing value named by the name of the target computing node is created according to the backup information, and the backup information is sent to one or more computing nodes, wherein the one or more computing nodes comprise the target computing node; and the target computing node receives the corresponding backup message according to the routing value of the backup message, and backs up the data to be backed up in the virtual machine to the backup storage server according to the received backup message. The technical scheme of the application can solve the problem of concurrency of backup tasks when a large number of virtual machines are subjected to data backup.
Description
Technical Field
The application relates to the technical field of cloud platforms, in particular to a virtual machine data backup method, a virtual machine data backup device, a virtual machine data backup system, electronic equipment and a storage medium.
Background
The significance of data backup and recovery lies in that after the system is subjected to accidents such as hacker intrusion, hardware failure, software failure or misoperation, the original data can be completely, quickly, simply and reliably recovered, the normal operation of the system can be ensured as much as possible within a certain time range, and data backup is an important means for ensuring data safety.
Currently, the data backup method for the virtual machine includes the following two methods:
the first method is intrusive, that is, agent software is installed in the virtual machine, and data in the virtual machine is copied to a remote backup server through the agent software. The first mode has the advantages that independent backup can be carried out on different types of data, the data volume is small, the defects that independent tools or plug-ins are needed for different types of data, and the maintenance of the agent module is complex;
the second way is non-intrusive, i.e. the data in the entire virtual machine is backed up. The second method has the advantages of simple maintenance and large data backup quantity.
In a cloud environment, the number of virtual machines borne by a cloud platform is usually large, and when a large number of virtual machines on the cloud platform perform data backup at the same time, a bottleneck problem that a large number of backup tasks are processed concurrently exists when any one of the above data backup modes is adopted.
Disclosure of Invention
The application provides a virtual machine data backup method, a virtual machine data backup device, a virtual machine data backup system, an electronic device and a storage medium, which can solve the problem of concurrence of backup tasks when a large number of virtual machines are subjected to data backup.
In a first aspect, the present application provides a virtual machine data backup method, which adopts the following technical scheme:
the virtual machine data backup method is applied to a cloud platform, the cloud platform comprises a management node and a plurality of computing nodes, each virtual machine is provided with a corresponding computing node, and the virtual machine data backup method comprises the following steps:
the management node acquires a target computing node corresponding to a virtual machine to be backed up;
the management node creates backup information according to the backup task;
the management node creates a backup message of naming the routing value by the name of the target computing node according to the backup information;
the management node sending the backup message to one or more computing nodes, the one or more computing nodes including the target computing node;
the target computing node receives the corresponding backup message according to the routing value of the backup message;
and the target computing node backs up the data to be backed up in the virtual machine to a backup storage server according to the received backup message.
Optionally, the creating, by the management node, the backup information according to the backup task includes:
the management node generates a backup instruction according to the backup task;
and the management node creates backup information according to the backup instruction.
Optionally, the virtual machine data backup method further includes: and after the management node creates backup information according to the backup task, storing the backup information in a database of the management node.
Optionally, the virtual machine data backup method further includes: after the target computing node receives the backup message, the target computing node sends confirmation information to the management node, and the management node updates the state of the backup task according to the confirmation information.
Optionally, the virtual machine data backup method further includes: after the target computing node backs up the data to be backed up in the virtual machine according to the backup message, the target computing node sends a backup completion notification to the management node, and the management node updates the state of the backup task according to the backup completion notification.
Optionally, the virtual machine data backup method further includes: and after the abnormal recovery of the management node, searching the incomplete backup tasks and updating the states of all the incomplete backup tasks.
Optionally, the updating the state of all the incomplete backup tasks includes:
the management node sends a backup task exception notification to each computing node in a message mode;
after receiving the backup task exception notification, each computing node reports the state of the current backup task to the management node;
and the management node updates the states of all uncompleted backup tasks according to the states of the current backup tasks reported by each computing node.
Optionally, the virtual machine data backup method further includes: after the abnormal recovery of the computing node, the computing node reports the abnormal recovery to the management node, the management node re-issues the incomplete backup task on the computing node, and the computing node re-executes the backup task.
Optionally, the virtual machine data backup method further includes: before the computing node re-executes the backup task, the computing node cleans the data which are not backed up in the backup storage server.
Optionally, the virtual machine data backup method further includes: after the computing node reports the abnormal recovery to the management node, the management node updates the state of the backup task, and updates the state of the backup task again before the management node re-issues the incomplete backup task on the computing node.
Optionally, the backing up the data to be backed up in the virtual machine to a backup storage server includes: and copying the data to be backed up in the virtual machine to the backup storage server in a remote copying manner to obtain a backup file.
Optionally, the virtual machine data backup method further includes: and naming the backup file according to the disk ID and the backup time of the backup file.
Optionally, the virtual machine data backup method further includes: and persistently storing the naming information of the backup file in a database of the management node.
Optionally, the virtual machine data backup method further includes: and constructing a backup storage pool, wherein the backup storage pool comprises a plurality of backup storage servers.
Optionally, the virtual machine data backup method further includes: and establishing a mapping relation between the backup storage server and the computing node in the backup storage pool.
Optionally, the virtual machine data backup method further includes: and determining a backup storage server corresponding to the target computing node according to the mapping relation before the target computing node backs up the data to be backed up in the virtual machine to the backup storage server according to the backup message.
Optionally, the virtual machine data backup method further includes: registering each backup storage server in the backup storage pool with the management node; when a backup storage server is added, the added backup storage server is registered in the management node, and the management node maintains the mapping relation according to the total number of the computing nodes and the total number of the backup storage servers; and when the backup storage server is deleted, the deleted backup storage server is logged off at the management node, and the management node maintains the mapping relation according to the total number of the computing nodes and the total number of the backup storage servers.
In a second aspect, the present application provides a virtual machine data backup apparatus, which adopts the following technical solution:
the virtual machine data backup device is applied to a cloud platform, the cloud platform comprises a management node and a plurality of computing nodes, each virtual machine is provided with a corresponding computing node, and the virtual machine data backup device comprises:
the node acquisition module is used for acquiring a target computing node corresponding to a virtual machine to be backed up;
the information creating module is used for creating backup information according to the backup task;
the message creating module is used for creating a backup message of naming the routing value by the name of the target computing node according to the backup information;
a message sending module for sending the backup message to one or more computing nodes, the one or more computing nodes including the target computing node;
the message receiving module is used for receiving the corresponding backup message according to the routing value of the backup message;
the backup execution module is used for backing up the data to be backed up in the virtual machine to a backup storage server according to the received backup message;
the node acquisition module, the information creation module, the message creation module and the message sending module are deployed on the management node, and the message receiving module and the backup execution module are deployed on the computing node.
In a third aspect, the present application provides a virtual machine data backup system, which adopts the following technical solutions:
the virtual machine data backup system comprises the virtual machine data backup device and at least one backup storage server.
In a fourth aspect, the present application provides an electronic device, which adopts the following technical solutions:
the electronic device includes:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein, the first and the second end of the pipe are connected with each other,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform any of the virtual machine data backup methods described above.
In a fifth aspect, the present application provides a computer-readable storage medium, which adopts the following technical solutions:
the computer readable storage medium stores computer instructions for causing a computer to perform any of the virtual machine data backup methods described above.
The embodiment of the application provides a virtual machine data backup method, a virtual machine data backup device, a virtual machine data backup system, electronic equipment and a storage medium, wherein the virtual machine data backup method is applied to a cloud platform, the cloud platform comprises a management node and computing nodes, in the process of data backup by applying the virtual machine data backup method, the management node acquires a target computing node corresponding to a virtual machine to be backed up, backup information is created according to a backup task, backup information with a routing value named by the name of the target computing node is created according to the backup information, the backup information is sent to one or more computing nodes, the target computing node receives the corresponding backup information according to the routing value of the backup information, and the data to be backed up in the virtual machine is backed up to a backup storage server according to the received backup information. In the process, a distributed backup task distribution mode is adopted, namely a management node distributes the backup task, and the target computing node corresponding to the virtual machine to be backed up processes the backup task, so that on one hand, the situation that the same node or equipment not only manages the backup task but also executes the backup task is avoided, and on the other hand, a large number of backup tasks of the virtual machine can be distributed to different target computing nodes for processing. Therefore, the virtual machine data backup method can solve the problem of concurrence of backup tasks when a large number of virtual machines are subjected to data backup.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to these drawings without inventive exercise.
Fig. 1 is a schematic diagram of a cloud platform provided in an embodiment of the present application;
fig. 2 is a flowchart of a virtual machine data backup method according to an embodiment of the present application;
fig. 3 is a flowchart illustrating a change of a backup task state according to an embodiment of the present disclosure;
fig. 4 is a schematic diagram of a data backup process provided in an embodiment of the present application;
fig. 5 is a schematic diagram of a data backup and data recovery process according to an embodiment of the present application;
FIG. 6 is a schematic diagram of an incremental backup provided in an embodiment of the present application;
FIG. 7 is a mapping diagram of a backup storage pool and computing nodes provided by an embodiment of the present application;
fig. 8 is a schematic diagram of a virtual machine data backup device according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of an apparatus provided in 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 obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.
It should be noted that, in the embodiments of the present application, the technical features may be combined with each other without conflict.
An embodiment of the present application provides a virtual machine data backup method, where the virtual machine data backup method is applied to a cloud platform, as shown in fig. 1, the cloud platform includes a management node (which may also be referred to as a control node and may be composed of one or more control servers) and a plurality of computing nodes (which may be composed of one or more computing servers), each virtual machine has a corresponding computing node (a one-to-one or one-to-many relationship may be formed between a computing node and a virtual machine), and specifically, as shown in fig. 2, the virtual machine data backup method includes:
s1, a management node acquires a target computing node corresponding to a virtual machine to be backed up.
The management node can acquire a target computing node corresponding to the virtual machine to be backed up according to the corresponding relation between the virtual machine and the computing node.
And S2, the management node creates backup information according to the backup task.
Illustratively, the management node generates a backup instruction according to the backup task, and then creates backup information according to the backup instruction.
Illustratively, the backup instruction may be issued in the following manner: and selecting a virtual machine to be backed up according to the backup task, and enabling the management node to automatically issue a backup instruction in a mode of setting a backup strategy on the management node. The above backup policies may include backup time, backup period, backup type (full or incremental) and the like. For example, if the backup policy is 3 pm daily and full backup is performed on a virtual machine, the backup instruction automatically issued by the management node is to complete full data backup on the virtual machine at 3 pm daily. Of course, the backup instruction may also be manually triggered by an administrator through the management node, where the manual triggering refers to one-time immediate backup. The skilled person can select the desired one according to the actual need.
Illustratively, the backup information may include, but is not limited to, creation time, backup object (virtual machine), task status, backup type (incremental backup or full backup), backup file name, backup storage server name, and the like.
Optionally, in this embodiment of the present application, the virtual machine data backup method further includes: after the management node creates the backup information according to the backup instruction, the backup information is saved in a database of the management node so as to facilitate subsequent maintenance of the backup information (for example, updating a task state in the backup information).
And S3, the management node creates a backup message of naming the routing value by the name of the target computing node according to the backup information.
That is, the header of the generated backup message is assigned to the name of the target computing node in order to distinguish the recipients of the backup message.
Illustratively, the backup message contains information of a backup object (virtual machine), a backup type (incremental backup or full backup), a backup storage server name, a backup time, and the like.
And S4, the management node sends the backup message to one or more computing nodes.
The one or more computing nodes include a target computing node.
Optionally, in this embodiment of the application, the management node sends the backup message to one or more computing nodes through the message middleware, for example, the management node sends the backup message to all computing nodes through the message middleware. The above mode can make the mode of sending the backup message by the management node simple without any judgment process, and is suitable for all the computing nodes.
And S5, the target computing node receives the corresponding backup message according to the routing value of the backup message.
That is, the target computing node receives only the backup message belonging to its own node according to the routing value, so as to execute the backup task corresponding to its own node.
Optionally, the virtual machine data backup method in the embodiment of the present application further includes: after the target computing node receives the backup message, the target computing node sends confirmation information to the management node, and the management node updates the state of the backup task according to the confirmation information so as to conveniently and accurately judge whether the backup task is executed and completed or not in the follow-up process. Illustratively, as shown in FIG. 3, the status of the backup task is updated to "in progress".
And S6, backing up the data to be backed up in the virtual machine to a backup storage server by the target computing node according to the received backup message.
Illustratively, the target computing node performs data backup on the data to be backed up in the virtual machine according to the information such as the backup object (virtual machine), the backup type (incremental backup or full backup), the name of the backup storage server, the backup time and the like indicated by the backup message.
Optionally, as shown in fig. 4 and 5, backing up the data to be backed up in the virtual machine to the backup storage server in the embodiment of the present application includes: and copying the data to be backed up in the virtual machine to a backup storage server in a remote copying manner to obtain a backup file. Further, the virtual machine data backup method further includes: and naming the backup files according to the disk ID and the backup time corresponding to the backup files. Further, the virtual machine data backup method further comprises the following steps: and persistently storing the naming information of the backup file in a database of the management node.
In one example, if the backup type is "full backup," all the data to be backed up is copied to the backup storage server. The specific process is as follows: all disk (including system disk and data disk) data is exported from the storage system of the virtual machine and copied to the backup storage server by means of remote copy. The backup file name is composed of a disk ID (the disk ID is unique and can not be repeated) and backup time, such as: 4e863410-e076-4605-b8f 4-96a456986e8 _20220919130100.
In another example, if the backup type is "incremental backup", snapshot operation is performed on the data in the virtual machine, and the incremental data in the two snapshots is exported and copied to the backup storage server by means of remote copy. The specific process is as follows: as shown in fig. 6, when a virtual machine is backed up, a system disk and a data disk of the virtual machine are backed up respectively, and taking the system disk as an example (a data disk backup process is similar to that of the system disk), a snapshot is taken from the disk during backup, if the backup is a first backup, data to be backed up is exported based on the snapshot, and if the backup is not a first backup, a difference value comparison is performed between a current snapshot and a previous snapshot, incremental data is exported as data to be backed up, and the data is copied to a backup storage server in a remote copy manner. Backup file naming is composed of a disk ID (which is unique and not repeated) and backup time, such as: 4e863410-e076-4605-b8f 4-96a456986e8 _20220919130100.
Optionally, the virtual machine data backup method in the embodiment of the present application further includes: and after the target computing node backs up the data to be backed up in the virtual machine according to the backup message, the target computing node sends a backup completion notification to the management node, and the management node updates the state of the backup task according to the backup completion notification. Illustratively, as shown in FIG. 3, the status of the backup task is updated from "in progress" to "complete".
In addition, the management node and the computing node also take over other basic functions of the cloud platform, for example, the management node is mainly responsible for management of resource scheduling, authentication, computation, storage, network, and the like of the cloud platform, and the computing node is a node for carrying a service and is used for carrying operation of a virtual machine.
The embodiment of the application provides a virtual machine data backup method, which is applied to a cloud platform, wherein the cloud platform comprises a management node and a plurality of computing nodes, each virtual machine is provided with a corresponding computing node, in the process of data backup by applying the virtual machine data backup method, the management node acquires a target computing node corresponding to a virtual machine to be backed up, creates backup information according to a backup task, creates backup information with a name of the target computing node naming a routing value according to the backup information, sends the backup information to one or more computing nodes, the target computing node receives the corresponding backup information according to the routing value of the backup information, and backs up data to be backed up in the virtual machine to a backup storage server according to the received backup information. In the process, a distributed backup task distribution mode is adopted, namely a management node distributes the backup task, and the target computing node corresponding to the virtual machine to be backed up processes the backup task, so that on one hand, the situation that the same node or equipment not only manages the backup task but also executes the backup task is avoided, and on the other hand, a large number of backup tasks of the virtual machine can be distributed to different target computing nodes for processing. Therefore, the virtual machine data backup method can solve the problem of concurrence of backup tasks when a large number of virtual machines are subjected to data backup.
After the data backup is performed by using the virtual machine data backup method, if data in the virtual machine is lost due to an accident or misoperation, as shown in fig. 5, data recovery can be performed in the following manner:
and (3) recovering the full backup data: selecting a virtual machine to be subjected to data recovery, selecting a backup file at a certain time point, remotely pulling the backup file from a backup storage server, and recovering the backup file to a disk corresponding to the virtual machine.
And (3) restoring the incremental backup data: selecting a virtual machine to be subjected to data recovery, selecting a certain time point, remotely pulling all backup files before the time point from a backup storage server, merging all the backup files before the time point into a total backup file, and recovering the total backup file to a disk corresponding to the virtual machine. It should be noted that the data that is incrementally backed up has a dependency relationship, and the backup files need to be merged according to the dependency relationship when the data is restored, for example, 4 backup files file1, file2, file3, and file4 are generated, and when the data needs to be restored, the 4 backup files need to be merged into one total backup file and then restored to the virtual machine.
Optionally, the virtual machine data backup method in the embodiment of the present application further includes: after the abnormal recovery of the management node, the incomplete backup tasks are searched (for example, the incomplete backup tasks are searched by querying a database in the management node), and the states of all the incomplete backup tasks are updated. Through the mode, even if the management node is abnormal (such as power failure, fault and the like) in the actual operation process of the cloud platform, the states of all uncompleted backup tasks can be updated in time after the abnormality is recovered, so that the states of the backup tasks are consistent with the actual execution condition. For example, when the management node is abnormal, if a certain backup task is already executed and completed, the status of the backup task is updated from "in progress" to "completed". Illustratively, in this embodiment of the present application, updating the states of all the incomplete backup tasks includes: the management node sends a backup task exception notification to each computing node in a message mode; after receiving the abnormal notification of the backup task, each computing node reports the state of the current backup task to a management node; and the management node updates the states of all the uncompleted backup tasks according to the states of the current backup tasks reported by each computing node.
Optionally, the virtual machine data backup method further includes: after the abnormal recovery of the computing node, the computing node reports the abnormal recovery to the management node, the management node re-issues the incomplete backup task on the computing node, the computing node re-executes the backup task, and the re-issuing and re-executing mode is the same as the first-time issuing and executing mode, and reference is made to the previous steps, and details are not repeated here. Through the mode, even if the computing node is abnormal (such as power failure and faults) in the actual operation process of the cloud platform, the backup task can be executed again after the abnormality is recovered.
Exemplarily, in an embodiment of the present application, the method for backing up data of a virtual machine further includes: before the computing node executes the backup task again, the computing node cleans the data which are not backed up in the backup storage server. These data that are not backed up to completion may also be referred to as dirty data, which has no practical role and simply occupies storage space in the backup storage server.
Optionally, in this embodiment of the present application, the method for backing up data of a virtual machine further includes: after the computing node reports the abnormal recovery to the management node, the management node updates the state of the backup task, and updates the state of the backup task again before the management node re-issues the incomplete backup task on the computing node. Exemplarily, as shown in fig. 3, after the abnormal recovery of the computing node, the computing node reports the abnormal recovery to the management node, the management node updates the state of the backup task to "failure", and checks (may check by querying the backup information) whether there is an incomplete backup task on the computing node, and when there is an incomplete backup task, resets the state of the backup task to "rebuild", and re-issues the backup task, where the computing node firstly cleans up the incomplete dirty data, and then re-executes the backup task.
It should be added that when the backup information is stored in the database of the management node, the above-mentioned state of the update backup task refers to the task state included in the backup information in the update database.
Optionally, the virtual machine data backup method in the embodiment of the present application further includes: a backup storage pool is constructed, as shown in fig. 7, comprising a plurality of backup storage servers. By the method, the transverse expansion of the backup storage server can be realized, the storage performance of the backup storage server can be further expanded, and the existing bottleneck problem is solved. The number of the backup storage servers can be determined according to the backup storage server network, the performance of the disk IO, the cloud platform scale and the load condition of the backup service. Illustratively, the backup storage pool data structure may comprise: backup storage pool name, ID, creation time, backup storage server name (globally unique), etc.
Optionally, the virtual machine data backup method in the embodiment of the present application further includes: and establishing a mapping relation between the backup storage server and the computing nodes in the backup storage pool, which can also be called as a list of the computing nodes corresponding to the backup storage server. For example, as shown in fig. 7, the mapping relationship is that the 1 st backup storage server corresponds to the 1 st and 2 nd computing nodes, the 2 nd backup storage server corresponds to the 3 rd and 4 th computing nodes, and so on. The mapping relationship may be contained in a backup storage pool data structure. Through the mapping relation, the storage resources of the backup storage pool can be reasonably distributed to each computing node, and the problem of low transmission efficiency caused by the fact that a large number of computing nodes copy backup data to the same backup storage server when executing backup tasks is solved. Optionally, in the method for backing up data of a virtual machine in the embodiment of the present application, a backup storage server corresponding to the target computing node is determined according to the mapping relationship, and then the target computing node backs up data to be backed up in the virtual machine to the backup storage server according to the backup message.
Optionally, the virtual machine data backup method in the embodiment of the present application further includes: when the backup storage servers are increased or decreased, the mapping relation is maintained, so that the storage resource allocation of the backup storage pool is continuously in a better state.
Illustratively, the virtual machine data backup method further comprises: and registering each backup storage server in the backup storage pool to the management node. Specifically, after the cloud platform is deployed, the backup storage pool is configured with one backup storage server by default, and is simultaneously registered to the management node, the management node makes unique numbers for the backup storage pool and the backup storage server, and maintains corresponding information, and when only one backup storage server exists, all the computing nodes correspond to the backup storage server; when the backup storage server is added, the backup storage server is registered, and when the backup storage server is deleted, the deleted backup storage server is logged off.
Based on the above, when the backup storage servers are increased or decreased, the mapping relationship is maintained, and the process of managing the backup storage pool includes:
(2) When a backup storage server is added, the backup storage server is registered in a management node, the management node maintains the backup storage server, meanwhile, the number of the calculation nodes is calculated, the total number of the calculation nodes is divided by the total number of the backup storage server, and the corresponding mapping relation is maintained. The backup data is stored according to the mapping relationship between the computing nodes and the backup storage servers when the backup task is scheduled, for example, the cloud platform includes 10 computing nodes (the total number of the computing nodes in the cloud platform is determined when a cloud platform scheme is designed, and is usually a fixed value), the computing nodes are marked as C1 to C10, 1 backup storage server is arranged in the backup storage pool before, after 1 backup storage server is added, there are 2 backup storage servers in total, the marking is S1 and S2, the result of dividing the total number of the computing nodes 10 by the total number of the backup storage servers 2 is 5, each backup storage server corresponds to 5 computing nodes, so that C1 to C5 corresponds to S1, and C6 to C10 corresponds to S2. In other cases, if the backup storage server cannot be divided, one of the backup storage servers may correspond to fewer computing nodes.
(3) When a backup storage server is deleted, the backup storage server logs off at the management node, simultaneously recalculates the mapping relation according to the number of the calculation nodes, and maintains the corresponding mapping relation by dividing the total number of the calculation nodes by the total number of the backup storage servers. It should be noted that logging off the backup storage server should ensure that there is no backup data in it. For example, the cloud platform includes 10 computing nodes, which are marked as C1 to C10, 3 backup storage servers exist in the backup storage pool, after 1 backup storage server is deleted, 2 backup storage servers remain, which are marked as S1 and S2, and the result of dividing the total number of computing nodes 10 by the total number of backup storage servers 2 is 5, so that each backup storage server corresponds to 5 computing nodes, and C1 to C5 can correspond to S1, and C6 to C10 can correspond to S2. In other cases, if the backup storage server cannot be divided exactly, one of the backup storage servers may correspond to fewer nodes.
In addition, an embodiment of the present application further provides a virtual machine data backup device, where the virtual machine data backup device is applied to a cloud platform, the cloud platform includes a management node and a computing node, each virtual machine has a corresponding computing node, and as shown in fig. 8, the virtual machine data backup device includes:
a node obtaining module 10, configured to obtain a target computing node corresponding to a virtual machine to be backed up;
an information creating module 20 for creating backup information according to the backup task;
a message creating module 30, configured to create a backup message with a name of the target computing node naming the routing value according to the backup information;
a message sending module 40 for sending the backup message to one or more computing nodes, the one or more computing nodes including a target computing node;
a message receiving module 50, configured to receive a corresponding backup message according to a routing value of the backup message;
the backup executing module 60 is configured to backup data to be backed up in the virtual machine to the backup storage server according to the received backup message;
the node acquisition module 10, the information creation module 20, the message generation module 30, and the message transmission module 40 are disposed on a management node, and the message reception module 50 and the backup execution module 60 are disposed on a computing node.
In fig. 8, only one computing node is shown, and the connection manner between the management node and other computing nodes is the same as that shown in fig. 8, which can be derived by those skilled in the art. In addition, each computing node may include one or more backup execution modules to perform backup tasks.
Optionally, in this embodiment of the present application, the message sending module 40 is a message middleware, for example, a message middleware such as ActiveMQ, rabbitMQ, kafka, rocktmq, and the like.
Optionally, the virtual machine data backup device in this embodiment of the application further includes a storage module and a database, where the storage module and the database are disposed on the management node, and the storage module is configured to store the backup information in the database of the management node after the management node creates the backup information according to the backup instruction, and/or persistently store the naming information of the backup file in the database of the management node.
Optionally, the virtual machine data backup device in this embodiment of the application further includes a feedback module and a state update module, where the feedback module is deployed on the computing node, and the state update module is deployed on the management node. Wherein the content of the first and second substances,
the feedback module is used for sending confirmation information to the management node after the message receiving module receives the backup message, and/or sending a backup completion notification to the management node after the data to be backed up in the virtual machine is backed up according to the backup message, and/or reporting the state of the current backup task to the management node after receiving the backup task abnormal notification, and/or reporting the abnormal recovery to the management node.
The state updating module is used for receiving the confirmation information and updating the state of the backup task according to the confirmation information, and/or updating the state of the backup task according to the backup completion notice, and/or updating the states of all uncompleted backup tasks according to the state of the current backup task reported by the computing node after the abnormal recovery of the management node, and/or updating the state of the backup task after the abnormal recovery reported by the computing node to the management node, and updating the state of the backup task again before the uncompleted backup task on the computing node is retransmitted by the management node.
Optionally, the virtual machine data backup device in this embodiment of the application further includes a cleaning module, configured to clean data that is not backed up in the backup storage server before the computing node re-executes the backup task. The cleaning module is deployed on the computing node.
Optionally, the virtual machine data backup apparatus in this embodiment of the application further includes a building module, configured to build a backup storage pool, where the backup storage pool includes a plurality of backup storage servers. The building module is deployed on the management node.
Optionally, the virtual machine data backup apparatus in this embodiment of the application further includes a relationship establishing module, configured to establish a mapping relationship between the backup storage server and the computing node. The relationship establishing module is deployed on the management node.
Optionally, the virtual machine data backup apparatus in this embodiment of the application further includes a relationship determining module, configured to determine, according to the mapping relationship, a backup storage server corresponding to the target computing node before the target computing node backs up the data to be backed up in the virtual machine to the backup storage server according to the backup message. The relationship determination module is deployed on the management node.
Optionally, the virtual machine data backup apparatus in this embodiment of the application further includes a registration module, where the registration module is configured to register each backup storage server in the backup storage pool with the management node, register the added backup storage server with the management node when the backup storage server is added, and log out the deleted backup storage server with the management node when the backup storage server is deleted. The registration module is deployed on the management node.
Optionally, the virtual machine data backup apparatus in this embodiment of the application further includes a relationship maintenance module, configured to maintain the mapping relationship according to the total number of the computing nodes and the total number of the backup storage servers when the backup storage servers are added or deleted. The relationship maintenance module is deployed on the management node.
It should be noted that, in the embodiment of the present application, relevant details of the virtual machine data backup method are all applicable to the corresponding modules, and are not described herein again.
In addition, an embodiment of the present application further provides a virtual machine data backup system, where the virtual machine data backup system includes the virtual machine data backup apparatus described above and at least one backup storage server.
In addition, an embodiment of the present application further provides an electronic device, where the electronic device includes:
at least one processor; and (c) a second step of,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform any of the virtual machine data backup methods described above.
In addition, an embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores computer instructions for causing a computer to execute any one of the above virtual machine data backup methods.
Embodiments of the application may be implemented as an apparatus for performing the desired configuration using any suitable hardware, firmware, software, or any combination thereof, which may include: and electronic equipment such as terminal equipment, servers (clusters) and the like. Fig. 9 schematically illustrates an example apparatus 1100 that may be used to implement various embodiments described herein.
For one embodiment, fig. 9 illustrates an example apparatus 1100 having one or more processors 1102, a control module (chipset) 1104 coupled to at least one of the processor(s) 1102, a memory 1106 coupled to the control module 1104, a non-volatile memory (NVM)/storage 1108 coupled to the control module 1104, one or more input/output devices 1110 coupled to the control module 1104, and a network interface 1112 coupled to the control module 1104.
The processor 1102 may include one or more single-core or multi-core processors, and the processor 1102 may include any combination of general-purpose or special-purpose processors (e.g., graphics processors, application processors, baseband processors, etc.). In some embodiments, the apparatus 1100 can be implemented as a terminal device, a server (cluster), or the like in the embodiments of the present application.
In some embodiments, the apparatus 1100 may include one or more computer-readable media (e.g., the memory 1106 or the NVM/storage 1108) having instructions 1114 and one or more processors 1102 in combination with the one or more computer-readable media configured to execute the instructions 1114 to implement modules to perform the actions described herein.
For one embodiment, control module 1104 may include any suitable interface controllers to provide any suitable interface to at least one of the processor(s) 1102 and/or to any suitable device or component in communication with control module 1104.
The control module 1104 may include a memory controller module to provide an interface to the memory 1106. The memory controller module may be a hardware module, a software module, and/or a firmware module.
The memory 1106 may be used to load and store data and/or instructions 1114 for the device 1100, for example. For one embodiment, memory 1106 may include any suitable volatile memory, such as suitable DRAM. In some embodiments, the memory 1106 may include a double data rate type four synchronous dynamic random access memory (DDR 4 SDRAM).
For one embodiment, control module 1104 may include one or more input/output controllers to provide an interface to NVM/storage 1108 and input/output device(s) 1110.
For example, NVM/storage 1108 may be used to store data and/or instructions 1114. NVM/storage 1108 may include any suitable non-volatile memory (e.g., flash memory) and/or may include any suitable non-volatile storage device(s) (e.g., one or more Hard Disk Drives (HDDs), one or more Compact Disc (CD) drives, and/or one or more Digital Versatile Disc (DVD) drives).
NVM/storage 1108 may include storage resources that are physically part of the device on which apparatus 1100 is installed, or it may be accessible by the device and need not be part of the device. For example, NVM/storage 1108 may be accessed over a network via input/output device(s) 1110.
Input/output device(s) 1110 may provide an interface for apparatus 1100 to communicate with any other suitable device, input/output device(s) 1110 may include communication components, audio components, sensor components, and so forth. Network interface 1112 may provide an interface for device 1100 to communicate over one or more networks, and device 1100 may communicate wirelessly with one or more components of a wireless network according to any of one or more wireless network standards and/or protocols, such as access to a communication standard-based wireless network, e.g., wiFi, 2G, 3G, 4G, 5G, etc., or a combination thereof.
For one embodiment, at least one of the processor(s) 1102 may be packaged together with logic for one or more controller(s) (e.g., memory controller module) of the control module 1104. For one embodiment, at least one of the processor(s) 1102 may be packaged together with logic for one or more controllers of control module 1104 to form a System In Package (SiP). For one embodiment, at least one of the processor(s) 1102 may be integrated on the same die with logic for one or more controller(s) of the control module 1104. For one embodiment, at least one of the processor(s) 1102 may be integrated on the same die with logic for one or more controller(s) of control module 1104 to form a system on chip (SoC).
In various embodiments, the apparatus 1100 may be, but is not limited to being: a server, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a handheld computing device, a tablet, a netbook, etc.) among other terminal devices. In various embodiments, the apparatus 1100 may have more or fewer components and/or different architectures. For example, in some embodiments, device 1100 includes one or more cameras, keyboards, liquid Crystal Display (LCD) screens (including touch screen displays), non-volatile memory ports, multiple antennas, graphics chips, application Specific Integrated Circuits (ASICs), and speakers.
The detection device can adopt a main control chip as a processor or a control module, sensor data, position information and the like are stored in a memory or an NVM/storage device, a sensor group can be used as an input/output device, and a communication interface can comprise a network interface.
For the apparatus embodiment, since it is substantially similar to the method embodiment, the description is relatively simple, and reference may be made to the partial description of the method embodiment for relevant points.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art will understand that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.
Claims (12)
1. A virtual machine data backup method is applied to a cloud platform, the cloud platform comprises a management node and a plurality of computing nodes, each virtual machine is provided with a corresponding computing node, and the virtual machine data backup method is characterized by comprising the following steps:
the management node acquires a target computing node corresponding to a virtual machine to be backed up;
the management node creates backup information according to the backup task;
the management node creates a backup message of naming the routing value by the name of the target computing node according to the backup information;
the management node sending the backup message to one or more computing nodes, the one or more computing nodes including the target computing node;
the target computing node receives the corresponding backup message according to the routing value of the backup message;
and the target computing node backs up the data to be backed up in the virtual machine to a backup storage server according to the received backup message.
2. The virtual machine data backup method according to claim 1, further comprising: and after the management node creates backup information according to the backup task, storing the backup information in a database of the management node.
3. The virtual machine data backup method according to claim 1, further comprising: and after the abnormal recovery of the management node, searching the incomplete backup tasks and updating the states of all the incomplete backup tasks.
4. The virtual machine data backup method according to claim 3, wherein the updating the state of all the incomplete backup tasks comprises:
the management node sends a backup task exception notification to each computing node in a message mode;
after receiving the backup task exception notification, each computing node reports the state of the current backup task to the management node;
and the management node updates the states of all uncompleted backup tasks according to the states of the current backup tasks reported by each computing node.
5. The virtual machine data backup method according to claim 1, further comprising: after the abnormal recovery of the computing node, the computing node reports the abnormal recovery to the management node, the management node re-issues the incomplete backup task on the computing node, and the computing node re-executes the backup task.
6. The virtual machine data backup method according to claim 1, further comprising: and constructing a backup storage pool, wherein the backup storage pool comprises a plurality of backup storage servers.
7. The virtual machine data backup method according to claim 6, further comprising: establishing a mapping relation between a backup storage server and a computing node in the backup storage pool; the virtual machine data backup method further comprises the following steps: and determining a backup storage server corresponding to the target computing node according to the mapping relation before the target computing node backs up the data to be backed up in the virtual machine to the backup storage server according to the backup message.
8. The virtual machine data backup method according to claim 7, further comprising: registering each backup storage server in the backup storage pool with the management node; when a backup storage server is added, the added backup storage server is registered in the management node, and the management node maintains the mapping relation according to the total number of the computing nodes and the total number of the backup storage servers; and when the backup storage server is deleted, the deleted backup storage server is logged out at the management node, and the management node maintains the mapping relation according to the total number of the computing nodes and the total number of the backup storage servers.
9. A virtual machine data backup device is applied to a cloud platform, the cloud platform comprises a management node and a plurality of computing nodes, each virtual machine is provided with a corresponding computing node, and the virtual machine data backup device comprises:
the node acquisition module is used for acquiring a target computing node corresponding to a virtual machine to be backed up;
the information creating module is used for creating backup information according to the backup task;
the message creating module is used for creating a backup message of naming the routing value by the name of the target computing node according to the backup information;
a message sending module for sending the backup message to one or more computing nodes, the one or more computing nodes including the target computing node;
the message receiving module is used for receiving the corresponding backup message according to the routing value of the backup message;
the backup execution module is used for backing up the data to be backed up in the virtual machine to a backup storage server according to the received backup message;
the node acquisition module, the information creation module, the message creation module and the message sending module are deployed on the management node, and the message receiving module and the backup execution module are deployed on the computing node.
10. A virtual machine data backup system comprising the virtual machine data backup apparatus according to claim 9 and at least one backup storage server.
11. An electronic device, characterized in that the electronic device comprises:
at least one processor; and (c) a second step of,
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the virtual machine data backup method according to any one of claims 1 to 8.
12. A computer-readable storage medium storing computer instructions for causing a computer to execute the virtual machine data backup method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211560664.4A CN115562911B (en) | 2022-12-07 | 2022-12-07 | Virtual machine data backup method, device, system, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211560664.4A CN115562911B (en) | 2022-12-07 | 2022-12-07 | Virtual machine data backup method, device, system, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115562911A true CN115562911A (en) | 2023-01-03 |
| CN115562911B CN115562911B (en) | 2023-04-25 |
Family
ID=84770526
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211560664.4A Active CN115562911B (en) | 2022-12-07 | 2022-12-07 | Virtual machine data backup method, device, system, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115562911B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116881052A (en) * | 2023-09-07 | 2023-10-13 | 上海凯翔信息科技有限公司 | Data restoration system for distributed storage |
| CN116991562A (en) * | 2023-09-28 | 2023-11-03 | 宁波银行股份有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN117608494A (en) * | 2023-12-06 | 2024-02-27 | 太极计算机股份有限公司 | Storage method and system of cloud computing cluster |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120072685A1 (en) * | 2010-09-16 | 2012-03-22 | Hitachi, Ltd. | Method and apparatus for backup of virtual machine data |
| WO2015096500A1 (en) * | 2013-12-24 | 2015-07-02 | 华为技术有限公司 | Service migration method and device and disaster tolerance system |
| CN105245565A (en) * | 2015-08-28 | 2016-01-13 | 浪潮集团有限公司 | Cloud system, management node and data obtaining method |
| CN108287747A (en) * | 2017-01-09 | 2018-07-17 | 中国移动通信集团贵州有限公司 | Method and apparatus for virtual machine backup |
| CN109669644A (en) * | 2019-01-02 | 2019-04-23 | 浪潮商用机器有限公司 | A kind of method and apparatus of data storage |
| US20190220364A1 (en) * | 2018-01-18 | 2019-07-18 | EMC IP Holding Company LLC | Method, device and computer program product for data backup |
| CN111651305A (en) * | 2020-08-05 | 2020-09-11 | 腾讯科技（深圳）有限公司 | Virtual machine backup method, virtual machine backup assembly and cloud computing system |
| CN112311568A (en) * | 2019-07-26 | 2021-02-02 | 中移(苏州)软件技术有限公司 | Virtual network creating method and device and computer storage medium |
| CN113127258A (en) * | 2019-12-30 | 2021-07-16 | 华为技术有限公司 | Data backup method, device, equipment and medium |
| CN113986450A (en) * | 2021-09-28 | 2022-01-28 | 新华三大数据技术有限公司 | Virtual machine backup method and device |
| CN114995958A (en) * | 2022-06-24 | 2022-09-02 | 济南浪潮数据技术有限公司 | Virtualization platform information consistency control method, device and medium |
-
2022
- 2022-12-07 CN CN202211560664.4A patent/CN115562911B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120072685A1 (en) * | 2010-09-16 | 2012-03-22 | Hitachi, Ltd. | Method and apparatus for backup of virtual machine data |
| WO2015096500A1 (en) * | 2013-12-24 | 2015-07-02 | 华为技术有限公司 | Service migration method and device and disaster tolerance system |
| CN105245565A (en) * | 2015-08-28 | 2016-01-13 | 浪潮集团有限公司 | Cloud system, management node and data obtaining method |
| CN108287747A (en) * | 2017-01-09 | 2018-07-17 | 中国移动通信集团贵州有限公司 | Method and apparatus for virtual machine backup |
| US20190220364A1 (en) * | 2018-01-18 | 2019-07-18 | EMC IP Holding Company LLC | Method, device and computer program product for data backup |
| CN109669644A (en) * | 2019-01-02 | 2019-04-23 | 浪潮商用机器有限公司 | A kind of method and apparatus of data storage |
| CN112311568A (en) * | 2019-07-26 | 2021-02-02 | 中移(苏州)软件技术有限公司 | Virtual network creating method and device and computer storage medium |
| CN113127258A (en) * | 2019-12-30 | 2021-07-16 | 华为技术有限公司 | Data backup method, device, equipment and medium |
| CN111651305A (en) * | 2020-08-05 | 2020-09-11 | 腾讯科技（深圳）有限公司 | Virtual machine backup method, virtual machine backup assembly and cloud computing system |
| CN113986450A (en) * | 2021-09-28 | 2022-01-28 | 新华三大数据技术有限公司 | Virtual machine backup method and device |
| CN114995958A (en) * | 2022-06-24 | 2022-09-02 | 济南浪潮数据技术有限公司 | Virtualization platform information consistency control method, device and medium |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116881052A (en) * | 2023-09-07 | 2023-10-13 | 上海凯翔信息科技有限公司 | Data restoration system for distributed storage |
| CN116881052B (en) * | 2023-09-07 | 2023-11-24 | 上海凯翔信息科技有限公司 | Data restoration system for distributed storage |
| CN116991562A (en) * | 2023-09-28 | 2023-11-03 | 宁波银行股份有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN116991562B (en) * | 2023-09-28 | 2023-12-26 | 宁波银行股份有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN117608494A (en) * | 2023-12-06 | 2024-02-27 | 太极计算机股份有限公司 | Storage method and system of cloud computing cluster |
| CN117608494B (en) * | 2023-12-06 | 2024-06-07 | 太极计算机股份有限公司 | Storage method and system of cloud computing cluster |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115562911B (en) | 2023-04-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10152382B2 (en) | Method and system for monitoring virtual machine cluster | |
| CN115562911A (en) | Virtual machine data backup method, device, system, electronic equipment and storage medium | |
| US8910172B2 (en) | Application resource switchover systems and methods | |
| CN107526659B (en) | Method and apparatus for failover | |
| US8381015B2 (en) | Fault tolerance for map/reduce computing | |
| US8954579B2 (en) | Transaction-level health monitoring of online services | |
| CN110795503A (en) | Multi-cluster data synchronization method and related device of distributed storage system | |
| US20210133054A1 (en) | Prioritized transfer of failure event log data | |
| CN114942859A (en) | Method, device, equipment, medium and program product for processing node failure | |
| US11042454B1 (en) | Restoration of a data source | |
| US20200389546A1 (en) | State replication, allocation and failover in stream processing | |
| CN117992283A (en) | Cloud host backup method and device, computer equipment and storage medium | |
| CN114189429A (en) | System, method, device and medium for monitoring server cluster faults | |
| CN102546250B (en) | File publishing method and system based on main/standby mechanism | |
| CN103713952A (en) | Virtual disk distributed-memory method based on UFS (Universal Flash Storage) | |
| CN110519393B (en) | Self-service equipment supervision method, device, equipment, server and medium | |
| WO2016086579A1 (en) | Method and device for intelligently backing up and recovering network element data in network management system | |
| CN105677515A (en) | Online backup method and system for database | |
| CN116578446B (en) | Virtual machine backup method, device and system, electronic equipment and storage medium | |
| CN117971564B (en) | Data recovery method, device, computer equipment and storage medium | |
| KR101449202B1 (en) | System and method for data copy and restoration in steel process middleware | |
| CN117608919A (en) | Disaster recovery method, disaster recovery device, computer equipment and storage medium | |
| CN114528156A (en) | Database switching method of heterogeneous disaster tolerance scheme, electronic device and medium | |
| CN116028263A (en) | Database data backup method and device, computing equipment and storage medium | |
| CN117688089A (en) | Redis-based data synchronous switching method, device, equipment and storage medium |
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 |