CN111078357A - Virtual machine backup method and equipment - Google Patents
Virtual machine backup method and equipment Download PDFInfo
- Publication number
- CN111078357A CN111078357A CN201911206789.5A CN201911206789A CN111078357A CN 111078357 A CN111078357 A CN 111078357A CN 201911206789 A CN201911206789 A CN 201911206789A CN 111078357 A CN111078357 A CN 111078357A
- Authority
- CN
- China
- Prior art keywords
- backup
- full
- virtual machine
- storage pool
- incremental
- 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.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 30
- 230000004044 response Effects 0.000 claims abstract description 33
- 230000002159 abnormal effect Effects 0.000 claims abstract description 9
- 238000004590 computer program Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- 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
-
- 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
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 invention provides a method and a device for virtual machine backup, wherein the method comprises the following steps: adding all virtual machines in the cluster into a backup management node; setting a backup storage pool of a virtual machine in a backup management node; respectively judging whether the state of each virtual machine is abnormal and whether a backup storage pool is available or not in response to receiving a backup instruction; respectively judging the backup quantity and the type in the backup storage pool corresponding to each virtual machine in response to the condition that each virtual machine is normal and the backup storage pool is available; and executing a corresponding backup strategy according to the backup quantity and the type. By using the method of the invention, the backup management of a plurality of virtual machines can be completed by a single task, the safety of service data and backup data can be improved, the utilization degree of the storage pool can be reduced, and the performance of the storage pool can be improved.
Description
Technical Field
The field relates to the field of computers, and more particularly to a method and apparatus for virtual machine backup.
Background
Distributed computing arises as the idea of interconnection is ubiquitous. The traditional server concept is challenged by big data from the network, thus creating virtualization technology. A virtual machine obtained using virtualization technology refers to a complete computer system having complete hardware system functionality, operating in a completely isolated environment, simulated by software. By utilizing the virtual machine, the hardware heterogeneity can be effectively shielded, and meanwhile, the virtual machine also has the function of isolating software.
In order to ensure that the operating data is not lost or that the system can be recovered as soon as possible after a fault occurs, the virtual machine needs to be frequently backed up, and the backup data is consistent with the operating data. The consistency of the backup data of the virtual machine with the running data may also be referred to as the consistency of the virtual machine.
The existing virtual machine backup mostly adopts single machine backup, a plurality of virtual machines need to be backed up for many times, backup data is generally mixed with service data for storage, so that storage and use are disordered, the data cannot be recovered in time when the virtual machine fails, and a part of backup mechanisms generally adopt full backup.
Disclosure of Invention
In view of this, an object of the embodiments of the present invention is to provide a method and a device for virtual machine backup, which can complete management of backup of multiple virtual machines through a single task, improve security of service data and backup data, reduce a utilization degree of a storage pool, and improve performance of the storage pool.
In view of the above, an aspect of the embodiments of the present invention provides a method for virtual machine backup, including the following steps:
adding all virtual machines in the cluster into a backup management node;
setting a backup storage pool of a virtual machine in a backup management node;
respectively judging whether the state of each virtual machine is abnormal and whether a backup storage pool is available or not in response to receiving a backup instruction;
respectively judging the backup quantity and the type in the backup storage pool corresponding to each virtual machine in response to the condition that each virtual machine is normal and the backup storage pool is available;
and executing a corresponding backup strategy according to the backup quantity and the type.
According to an embodiment of the present invention, executing the corresponding backup policy according to the number and type of backups includes:
responding to the condition that the number of the backups is smaller than the maximum number, judging whether a full backup exists in the backups, if so, performing incremental backup, and if not, performing the full backup;
in response to the number of backups being equal to the maximum number, the earliest backup being a full backup and an incremental backup being provided thereunder, deleting the earliest incremental backup under the full backup and then performing the incremental backup;
in response to the fact that the number of the backups is equal to the maximum number, the earliest backup is a full backup, and no incremental backup exists below the full backup, deleting the full backup and judging whether other full backups exist or not, if so, performing incremental backup, and if not, performing the full backup;
and in response to the fact that the number of the backups is equal to the maximum number and the earliest backup is not the full backup, deleting the earliest backup and judging whether the full backup exists, if so, performing incremental backup, and if not, performing the full backup.
According to one embodiment of the invention, the maximum number is the maximum number of backed-up files per virtual machine in the backup storage pool.
According to one embodiment of the invention, whether the backup is full backup is determined based on the size of the backup file.
According to one embodiment of the invention, the backup storage pool is a storage device separate from the active storage pool of the virtual machine.
In another aspect of the embodiments of the present invention, there is also provided an apparatus for virtual machine backup, where the apparatus includes:
at least one processor; and
a memory storing program code executable by the processor, the program code when executed by the processor performing the steps of:
adding all virtual machines in the cluster into a backup management node;
setting a backup storage pool of a virtual machine in a backup management node;
respectively judging whether the state of each virtual machine is abnormal and whether a backup storage pool is available or not in response to receiving a backup instruction;
respectively judging the backup quantity and the type in the backup storage pool corresponding to each virtual machine in response to the condition that each virtual machine is normal and the backup storage pool is available;
and executing a corresponding backup strategy according to the backup quantity and the type.
According to an embodiment of the present invention, performing different backup strategies according to different backup numbers and types includes:
responding to the condition that the number of the backups is smaller than the maximum number, judging whether a full backup exists in the backups, if so, performing incremental backup, and if not, performing the full backup;
in response to the number of backups being equal to the maximum number, the earliest backup being a full backup and an incremental backup being provided thereunder, deleting the earliest incremental backup under the full backup and then performing the incremental backup;
in response to the fact that the number of the backups is equal to the maximum number, the earliest backup is a full backup, and no incremental backup exists below the full backup, deleting the full backup and judging whether other full backups exist or not, if so, performing incremental backup, and if not, performing the full backup;
and in response to the fact that the number of the backups is equal to the maximum number and the earliest backup is not the full backup, deleting the earliest backup and judging whether the full backup exists, if so, performing incremental backup, and if not, performing the full backup.
According to one embodiment of the invention, the maximum number is the maximum number of backed-up files per virtual machine in the backup storage pool.
According to one embodiment of the invention, whether the backup is full backup is determined based on the size of the backup file.
According to one embodiment of the invention, the backup storage pool is a storage device separate from the active storage pool of the virtual machine.
The invention has the following beneficial technical effects: in the virtual machine backup method provided by the embodiment of the invention, all virtual machines in a cluster are added into a backup management node; setting a backup storage pool of a virtual machine in a backup management node; respectively judging whether the state of each virtual machine is abnormal and whether a backup storage pool is available or not in response to receiving a backup instruction; respectively judging the backup quantity in the backup storage pool corresponding to each virtual machine in response to the condition that each virtual machine is normal and the backup storage pool is available; according to the technical scheme of executing the corresponding backup strategy according to the backup quantity, the management of the backups of the virtual machines can be completed through a single task, the safety of service data and backup data can be improved, the utilization degree of the storage pool can be reduced, and the performance of the storage pool can be improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other embodiments can be obtained by using the drawings without creative efforts.
FIG. 1 is a schematic flow chart diagram of a method of virtual machine backup according to one embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following embodiments of the present invention are described in further detail with reference to the accompanying drawings.
In view of the foregoing, a first aspect of the embodiments of the present invention provides an embodiment of a method for virtual machine backup. Fig. 1 shows a schematic flow diagram of the method.
As shown in fig. 1, the method may include the steps of:
s1 adds all virtual machines in the cluster to the backup management node, which is equivalent to centralizing the backups of the virtual machines in the cluster together to implement batch backup of the virtual machines, and may also set a backup period, such as several backup per day, or start backup every several days;
s2, setting a backup storage pool of the virtual machine in the backup management node, wherein the backup storage pool and the service storage pool are separately deployed and configured to prevent the data security from being reduced by mixing backup data and service data;
s3, in response to receiving a backup instruction, respectively judging whether each virtual machine state is abnormal and whether a backup storage pool is available, wherein the virtual machines all exist in a database of a virtualization system, the corresponding virtual machine state can be obtained directly according to the id of the virtual machine during backup, the backup storage pool is generally mounted on a physical host, similar to a hard disk mounted on the host, and basically, the backup storage pool can be understood as being available as long as the host of the virtual machine can see the disk;
s4, responding to the fact that each virtual machine is normal in state and available in the backup storage pool, respectively judging the backup number and type in the backup storage pool corresponding to each virtual machine, wherein each virtual machine has an individual storage space in the backup storage pool, the existing backup number of the current virtual machine can be found in the individual storage space corresponding to each virtual machine, the actual files of the backup are stored in the backup storage pool, but the virtual machines store a piece of data in the database at the same time during the backup, and the backup is a chain. Judging the backup type (full or incremental) and directly querying a database according to the virtual machine id;
s5 executing corresponding backup strategy according to the backup quantity and type.
By the technical scheme, the management of the backup of the plurality of virtual machines can be completed through a single task, the safety of service data and backup data can be improved, the utilization degree of the storage pool can be reduced, and the performance of the storage pool is improved.
In a preferred embodiment of the present invention, the performing different backup strategies according to the number and types of backups comprises:
responding to the condition that the number of the backups is smaller than the maximum number, judging whether a full backup exists in the backups, if so, performing incremental backup, and if not, performing the full backup;
in response to the fact that the number of the backups is equal to the maximum number, the earliest backup is a full backup, and an incremental backup is arranged below the earliest backup, the incremental backup is carried out after the earliest incremental backup under the full backup is deleted;
in response to the fact that the number of the backups is equal to the maximum number, the earliest backup is a full backup, and no incremental backup exists below the earliest backup, deleting the full backup and judging whether other full backups exist or not, if so, performing incremental backup, and if not, performing the full backup;
and in response to the fact that the number of the backups is equal to the maximum number and the earliest backup is not the full backup, deleting the earliest backup and judging whether the full backup exists, if so, performing incremental backup, and if not, performing the full backup.
The batch backup operating system starts a plurality of threads to operate a plurality of virtual machines in batch, each thread is independently responsible for the backup of one virtual machine, whether the backup quantity of the current virtual machine reaches the maximum reserved quantity or not is judged, and if the backup quantity reaches the maximum reserved quantity, the backup is directly started. If the maximum reserved number is reached, deleting the earliest backup according to the following rule and then starting the backup.
In the backup process, first, whether the virtual machine has full backup at present is judged, if yes, incremental backup is carried out at the moment, and if not, full backup is carried out. The incremental backups are all performed based on the full backup.
And after the backup number of the virtual machine reaches the maximum reserved number, judging whether the earliest backup of the virtual machine is incremental backup or full backup. If the backup is incremental backup, directly deleting the backup; if the backup is full backup, judging whether incremental backup depends on the full backup or not, and if not, directly deleting the incremental backup; and if the incremental backup depends on the full backup, deleting the incremental backup which is generated earliest and depends on the full backup.
In a preferred embodiment of the present invention, the maximum number is the maximum number of backed-up files per virtual machine in the backup storage pool. The maximum backup number is set to 10 under general conditions, and can be changed into other values according to actual conditions and needs, so that the utilization degree of the storage pool can be reduced by limiting the maximum backup number, and the performance of the storage pool is improved.
In a preferred embodiment of the present invention, it is determined whether to backup a full amount based on the size of the backed-up file. Usually, the data of the full backup is much larger than the size of the file of the incremental backup, and the database can also be directly queried according to the virtual machine id, because the actual file of the backup is stored in the backup storage pool, but the virtual machine stores a piece of data in the database at the same time during the backup, the existing backup situation of the virtual machine is stored, and the backup is a chain.
In a preferred embodiment of the present invention, the backup storage pool is a storage device separate from the active storage pool of the virtual machine. The backup storage pool is separated from the service storage pool, so that the safety of service data and backup data can be improved.
Examples
1. The current batch backup of the management nodes is the virtual machine A, B, C, backup is carried out at 4 points in the morning every day, the backup storage pool uses Store1, the service storage pool used by the virtual machine is Store2, and the maximum backup number is set to be 10;
2. starting a batch backup task at 4 am, firstly judging whether the state of a virtual machine is abnormal, whether a storage pool Store2 of the virtual machine is available, and whether a backup storage pool Store1 is available;
3. when the virtual machines are in a normal state and the storage pool is available, respectively judging A, B, C whether the backup number of the three virtual machines reaches the maximum number according to the maximum backup number 10 in the backup strategy, wherein it is assumed that A does not reach the maximum backup number, B, C reaches the maximum backup number, B is the earliest backup and has incremental backups below B, C is the earliest backup and has no other incremental backups below C;
4. the virtual machine A directly starts backup, if the virtual machine A has full quantity, incremental backup is carried out, otherwise, the virtual machine A carries out full quantity backup;
5. the virtual machine B deletes the earliest incremental backup under the full backup because the earliest full backup is provided with the incremental backup, and then starts the backup, wherein the backup is the incremental backup;
6. and the virtual machine C directly deletes the earliest full backup and then starts backup, judges whether the full backup exists after deletion or not, performs incremental backup if the full backup exists, and performs full backup if the full backup does not exist.
By the technical scheme, the management of the backup of the plurality of virtual machines can be completed through a single task, the safety of service data and backup data can be improved, the utilization degree of the storage pool can be reduced, and the performance of the storage pool is improved.
It should be noted that, as will be understood by those skilled in the art, all or part of the processes in the methods of the above embodiments may be implemented by instructing relevant hardware through a computer program, and the above programs may be stored in a computer-readable storage medium, and when executed, the programs may include the processes of the embodiments of the methods as described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like. The embodiments of the computer program may achieve the same or similar effects as any of the above-described method embodiments.
Furthermore, the method disclosed according to an embodiment of the present invention may also be implemented as a computer program executed by a CPU, and the computer program may be stored in a computer-readable storage medium. The computer program, when executed by the CPU, performs the above-described functions defined in the method disclosed in the embodiments of the present invention.
In view of the above object, a second aspect of the embodiments of the present invention provides an apparatus for virtual machine backup, where the apparatus includes:
at least one processor; and
a memory storing program code executable by the processor, the program code when executed by the processor performing the steps of:
adding all virtual machines in the cluster into a backup management node;
setting a backup storage pool of a virtual machine in a backup management node;
respectively judging whether the state of each virtual machine is abnormal and whether a backup storage pool is available or not in response to receiving a backup instruction;
respectively judging the backup quantity and the type in the backup storage pool corresponding to each virtual machine in response to the condition that each virtual machine is normal and the backup storage pool is available;
and executing a corresponding backup strategy according to the backup quantity and the type.
In a preferred embodiment of the present invention, the performing different backup strategies according to the number and types of backups comprises:
responding to the condition that the number of the backups is smaller than the maximum number, judging whether a full backup exists in the backups, if so, performing incremental backup, and if not, performing the full backup;
in response to the fact that the number of the backups is equal to the maximum number, the earliest backup is a full backup, and an incremental backup is arranged below the earliest backup, the incremental backup is carried out after the earliest incremental backup under the full backup is deleted;
in response to the fact that the number of the backups is equal to the maximum number, the earliest backup is a full backup, and no incremental backup exists below the earliest backup, deleting the full backup and judging whether other full backups exist or not, if so, performing incremental backup, and if not, performing the full backup;
and in response to the fact that the number of the backups is equal to the maximum number and the earliest backup is not the full backup, deleting the earliest backup and judging whether the full backup exists, if so, performing incremental backup, and if not, performing the full backup.
In a preferred embodiment of the present invention, the maximum number is the maximum number of backed-up files per virtual machine in the backup storage pool.
In a preferred embodiment of the present invention, it is determined whether to backup a full amount based on the size of the backed-up file.
In a preferred embodiment of the present invention, the backup storage pool is a storage device separate from the active storage pool of the virtual machine.
It should be particularly noted that the embodiment of the system described above employs the embodiment of the method described above to specifically describe the working process of each module, and those skilled in the art can easily think that the modules are applied to other embodiments of the method described above.
Further, the above-described method steps and system elements or modules may also be implemented using a controller and a computer-readable storage medium for storing a computer program for causing the controller to implement the functions of the above-described steps or elements or modules.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments of the present invention.
The embodiments described above, particularly any "preferred" embodiments, are possible examples of implementations and are presented merely to clearly understand the principles of the invention. Many variations and modifications may be made to the above-described embodiments without departing from the spirit and principles of the technology described herein. All such modifications are intended to be included within the scope of this disclosure and protected by the following claims.
Claims (10)
1. A method for virtual machine backup is characterized by comprising the following steps:
adding all virtual machines in the cluster into a backup management node;
setting a backup storage pool of the virtual machine in the backup management node;
respectively judging whether the state of each virtual machine is abnormal and whether the backup storage pool is available or not in response to receiving a backup instruction;
respectively judging the backup quantity and the type of the backup storage pool corresponding to each virtual machine in response to the condition that each virtual machine is normal and the backup storage pool is available;
and executing a corresponding backup strategy according to the backup quantity and the backup type.
2. The method of claim 1, wherein executing the corresponding backup policy according to the backup quantity and type comprises:
responding to the condition that the number of the backups is smaller than the maximum number, judging whether a full backup exists in the backups, if so, performing incremental backup, and if not, performing the full backup;
in response to the fact that the number of the backups is equal to the maximum number, the earliest backup is a full backup, and an incremental backup exists below the full backup, deleting the earliest incremental backup under the full backup and then performing the incremental backup;
in response to the fact that the number of the backups is equal to the maximum number, the earliest backup is a full backup, and no incremental backup exists below the full backup, deleting the full backup and judging whether other full backups exist or not, if so, performing incremental backup, and if not, performing full backup;
and in response to the fact that the number of the backups is equal to the maximum number and the earliest backup is not the full backup, deleting the earliest backup and judging whether the full backup exists, if so, performing incremental backup, and if not, performing the full backup.
3. The method of claim 2, wherein the maximum number is a maximum number of each of the virtual machine backed-up files in the backup storage pool.
4. The method of claim 2, wherein determining whether to backup a full amount is based on the size of the backed-up file.
5. The method of claim 1, wherein the backup storage pool is a storage device separate from the active storage pool of the virtual machine.
6. An apparatus for virtual machine backup, the apparatus comprising:
at least one processor; and
a memory storing program code executable by the processor, the program code, when executed by the processor, performing the steps of:
adding all virtual machines in the cluster into a backup management node;
setting a backup storage pool of the virtual machine in the backup management node;
respectively judging whether the state of each virtual machine is abnormal and whether the backup storage pool is available or not in response to receiving a backup instruction;
respectively judging the backup quantity and the type of the backup storage pool corresponding to each virtual machine in response to the condition that each virtual machine is normal and the backup storage pool is available;
and executing a corresponding backup strategy according to the backup quantity and the backup type.
7. The device of claim 6, wherein performing the corresponding backup policy according to the backup quantity and type comprises:
responding to the condition that the number of the backups is smaller than the maximum number, judging whether a full backup exists in the backups, if so, performing incremental backup, and if not, performing the full backup;
in response to the fact that the number of the backups is equal to the maximum number, the earliest backup is a full backup, and an incremental backup exists below the full backup, deleting the earliest incremental backup under the full backup and then performing the incremental backup;
in response to the fact that the number of the backups is equal to the maximum number, the earliest backup is a full backup, and no incremental backup exists below the full backup, deleting the full backup and judging whether other full backups exist or not, if so, performing incremental backup, and if not, performing full backup;
and in response to the fact that the number of the backups is equal to the maximum number and the earliest backup is not the full backup, deleting the earliest backup and judging whether the full backup exists, if so, performing incremental backup, and if not, performing the full backup.
8. The device of claim 7, wherein the maximum number is a maximum number of each of the virtual machine backed-up files in the backup storage pool.
9. The apparatus of claim 7, wherein determining whether to backup a full amount is based on a size of the backed-up file.
10. The device of claim 6, wherein the backup storage pool is a storage device separate from the active storage pool of the virtual machine.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911206789.5A CN111078357A (en) | 2019-11-29 | 2019-11-29 | Virtual machine backup method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911206789.5A CN111078357A (en) | 2019-11-29 | 2019-11-29 | Virtual machine backup method and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111078357A true CN111078357A (en) | 2020-04-28 |
Family
ID=70312178
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911206789.5A Withdrawn CN111078357A (en) | 2019-11-29 | 2019-11-29 | Virtual machine backup method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111078357A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112395050A (en) * | 2020-11-30 | 2021-02-23 | 深信服科技股份有限公司 | Virtual machine backup method and device, electronic equipment and readable storage medium |
-
2019
- 2019-11-29 CN CN201911206789.5A patent/CN111078357A/en not_active Withdrawn
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112395050A (en) * | 2020-11-30 | 2021-02-23 | 深信服科技股份有限公司 | Virtual machine backup method and device, electronic equipment and readable storage medium |
| CN112395050B (en) * | 2020-11-30 | 2024-02-23 | 深信服科技股份有限公司 | Virtual machine backup method and device, electronic equipment and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10817386B2 (en) | Virtual machine recovery method and virtual machine management device | |
| US9773015B2 (en) | Dynamically varying the number of database replicas | |
| CN109656742B (en) | Node exception handling method and device and storage medium | |
| KR20140025503A (en) | Replaying jobs at a secondary location of a service | |
| CN111897558A (en) | Kubernets upgrading method and device for container cluster management system | |
| CN108255576B (en) | Virtual machine live migration exception handling method and device and storage medium | |
| CN110162344B (en) | Isolation current limiting method and device, computer equipment and readable storage medium | |
| CN111209110A (en) | Task scheduling management method, system and storage medium for realizing load balance | |
| US20210216353A1 (en) | Host Upgrade Method and Device | |
| CN111181780A (en) | HA cluster-based host pool switching method, system, terminal and storage medium | |
| CN113626256A (en) | Virtual machine disk data backup method, device, terminal and storage medium | |
| CN111538585B (en) | Js-based server process scheduling method, system and device | |
| US10635516B2 (en) | Intelligent logging | |
| CN112860787A (en) | Method for switching master nodes in distributed master-slave system, master node device and storage medium | |
| CN107943615B (en) | Data processing method and system based on distributed cluster | |
| EP3591530A1 (en) | Intelligent backup and recovery of cloud computing environment | |
| CN112948169A (en) | Data backup method, device, equipment and storage medium | |
| CN111078357A (en) | Virtual machine backup method and equipment | |
| CN111158956A (en) | Data backup method and related device for cluster system | |
| CN105743696A (en) | Cloud computing platform management method | |
| CN112269693B (en) | Node self-coordination method, device and computer readable storage medium | |
| CN115098300A (en) | Database backup method, disaster recovery method, device and equipment | |
| CN113553217A (en) | Data recovery method and device, storage medium and computer equipment | |
| CN114553859A (en) | BMC configuration management method and device, electronic equipment and storage medium | |
| CN113312309A (en) | Management method and device of snapshot chain 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 | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20200428 |