CN114138563A - Method for backing up and restoring Hyper-V virtual machine - Google Patents
Method for backing up and restoring Hyper-V virtual machine Download PDFInfo
- Publication number
- CN114138563A CN114138563A CN202111481798.2A CN202111481798A CN114138563A CN 114138563 A CN114138563 A CN 114138563A CN 202111481798 A CN202111481798 A CN 202111481798A CN 114138563 A CN114138563 A CN 114138563A
- Authority
- CN
- China
- Prior art keywords
- backup
- virtual machine
- file
- snapshot
- configuration
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
-
- 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
- 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/1479—Generic software techniques for error detection or fault masking
- G06F11/1482—Generic software techniques for error detection or fault masking by means of middleware or OS functionality
- G06F11/1484—Generic software techniques for error detection or fault masking by means of middleware or OS functionality involving virtual machines
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a Hyper-V virtual machine backup method, which comprises the steps of making a backup plan and reading the backup plan to restore a virtual machine; the backup plan making method specifically comprises the following steps: acquiring all virtual machine lists and configuration information thereof on a Hypervisor host, and making a backup plan; the backup comprises the following steps: starting the process; a backup judgment step; a storage step; and a snapshot creating step. By the method provided by the invention, remote real-time seamless batch backup, restoration and version control of the Hyper-V virtual machine are realized, the data in the virtual machine can be effectively protected, the situation that the data in the virtual machine is damaged or lost and cannot be found back is prevented, the data safety in the virtual machine is effectively protected, and the cost of data recovery is saved for a user.
Description
Technical Field
The invention belongs to the technical field of computer storage, and particularly relates to a method for backing up and restoring a Hyper-V virtual machine.
Background
With the development of cloud technology, virtual machines are more and more widely applied to individuals and enterprises, and the backup of the virtual machines is needed at present when the system backup is carried out in the past. The implementation principle of the virtual machines of different manufacturers is still greatly different, so that corresponding backup products need to be made for the virtual machines of different manufacturers. The invention aims at a Hyper-V virtual machine under the flag of Microsoft corporation, and realizes a set of backup and recovery method.
Disclosure of Invention
The invention aims to provide a method for backing up and restoring a Hyper-V virtual machine, which aims to solve the problem that the virtual machine cannot be backed up in the prior art proposed in the background technology.
In order to solve the technical problems, the technical scheme adopted by the invention is as follows:
a Hyper-V virtual machine backup method comprises the steps of making a backup plan for backup and reading the backup plan to restore a virtual machine; the backup plan making method specifically comprises the following steps: acquiring all virtual machine lists and configuration information thereof on a Hypervisor host, storing the acquired virtual machine lists and the configuration information thereof in a DB, making a backup plan, storing the backup plan in the DB and backing up through the backup plan;
the backup comprises the following steps:
the starting steps are as follows: after starting up, the backup service is in a running state, a backup plan is read from the DB, and if the current time meets the execution time specified in the plan, the plan is executed; if the execution time specified in the plan is not met, continuing to wait;
a backup judgment step: judging whether the backup is a complete backup or an incremental backup according to a backup plan to be executed, and if the backup is the complete backup, deleting the snapshot and exporting VM information; if the backup is incremental backup, directly exporting VM information, and then deleting the main disk file under the exported temporary folder;
a storage step: storing the finished backup, wherein the main storage is a disk image file of the virtual machine and a configuration file of the virtual machine;
a snapshot creating step: creating a new snapshot for the virtual machine, storing all modifications after the backup, and then finishing the backup;
in the backup judgment step, the fully backed-up and exported VM information is specifically: exporting the complete backup information of the Virtual machine by an export System Definition method in an Msvm _ Virtual System management service class of WMI;
in the backup judging step, the snapshot is created by a user or automatically created by the system after program backup; after the snapshot is deleted, the virtual disk file corresponding to the snapshot can be automatically merged into the main disk file; when the virtual machine is restored, the configuration file of the virtual machine does not need to provide the configuration information of the snapshot.
According to the above scheme, the obtaining of the virtual machine list and the configuration information thereof specifically includes:
a virtual machine list acquisition step: firstly, acquiring all virtual machine lists by using an interface class Msvm _ ComputerSystem of WMI;
the proxy step: using the self-contained Power Shell of the Windows Server as a proxy;
a configuration acquisition step: and obtaining the CPU, Memory and Network configuration of each virtual machine by remotely transmitting Power Shell related commands, wherein the commands comprise Get-VMmemory, Get-VMCPU and Get-VMNetworkAdap.
According to the scheme, the backup judging step comprises the following steps: when the backup is incremental backup, the derivation of the VM information specifically includes:
snapshot deletion step B1: when the virtual machine is completely backed up for the first time, firstly deleting all snapshots under the virtual machine, and after the snapshots are deleted, the Hyper-V automatically merges the contents in the avhdx disk files corresponding to the snapshots into a main disk image file;
full backup step B2: deleting the snapshot, then making a complete backup, and after the complete backup is completed, creating a new snapshot for storing all modifications after the backup;
incremental backup step B3: when incremental backup is carried out, all disk files and configuration information files of the virtual machine are exported to a temporary folder, then the main disk file of the virtual machine under the temporary folder is deleted, the disk files and the configuration files of the virtual machine in the avhdx format corresponding to the snapshot are reserved, the current snapshot is deleted after the export, and then a snapshot is created again; the new snapshot stores all modifications after the current backup, and is also a file to be copied when the next incremental backup is performed.
According to the scheme, the Virtual machine configuration file is specifically an Xml file under a Virtual Machines folder.
A Hyper-V virtual machine reduction method comprises the following steps:
start step A1, start;
virtual machine list acquisition step a 2: reading a virtual machine list from Database;
virtual machine selection step a 3: selecting a virtual machine to be restored;
backup file selection step a 4: selecting a backup file from a backup storage;
connection step a 5: establishing network sharing on a Hypervisor host, and establishing network connection according to the configured account;
download step a 6: downloading the selected backup file to the network share of step A5;
merge disks step A7: merging the disk files and modifying the configuration;
reduction step A8: starting a reduction VM;
end step a 9: and (6) ending.
According to the above scheme, in the step of merging disks a7, the merging of the disk files requires loading of a multi-disk file, and the specific step of loading the multi-disk file includes:
search step C1: according to the time of the restoring point selected by the user, a nearest complete backup is found from the backup storage all the time;
copy step C2: copying all backup files completely backed up to the restoring point to a Virtual Hard Disk subdirectory of a default restoring folder of a remote host;
merging step C3: the method comprises the steps that contents in all disk files of incremental backup are merged into a disk image file of a complete backup, and only one main disk image file of a Vhdx virtual machine exists after merging, so that configuration information of a snapshot is not required to be provided during restoration;
reduction step C4: copying the Virtual machine configuration file at the restoring point selected by the user to the Virtual Machines subdirectory of the default restoring folder, wherein the file records the disk image file name and the disk number of the Virtual machine during each backup, and the restoring process loads the disk according to the configuration.
According to the above scheme, the reduction step C4 specifically includes the following steps: configuration modification step C41: modifying the configuration pointing to the avhdx file to point to vhdx;
node deletion step C42: simultaneously deleting the snapshot nodes;
configuration reduction step C43: modify InstanceId: // properties/parent _ instance _ id, consistent with the original configuration.
Compared with the prior art, the invention has the following beneficial effects:
by the method provided by the invention, remote real-time backup, restoration and version control of the Hyper-V virtual machine are realized, the data in the virtual machine can be effectively protected, the situation that the data in the virtual machine is damaged or lost and cannot be found back is prevented, the data safety in the virtual machine is effectively protected, and the cost of data recovery is saved for a user.
Drawings
FIG. 1 is an overall flow chart of the present invention;
FIG. 2 is a backup flow diagram of the present invention;
FIG. 3 is a reduction scheme of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example one
As shown in fig. 1, fig. 2 and fig. 3, a Hyper-V virtual machine backup method includes making a backup plan for backup and reading the backup plan to restore a virtual machine; the backup plan making method specifically comprises the following steps: acquiring all virtual machine lists and configuration information thereof on a Hypervisor host, storing the acquired virtual machine lists and the configuration information thereof in a DB, making a backup plan, storing the backup plan in the DB and backing up through the backup plan;
the backup comprises the following steps:
the starting steps are as follows: after starting up, the backup service is in a running state, a backup plan is read from the DB, and if the current time meets the execution time specified in the plan, the plan is executed; if the execution time specified in the plan is not met, continuing to wait;
a backup judgment step: judging whether the backup is a complete backup or an incremental backup according to a backup plan to be executed, and if the backup is the complete backup, deleting the snapshot and exporting VM information; if the backup is incremental backup, directly exporting VM information, and then deleting the main disk file under the exported temporary folder;
a storage step: storing the finished backup, wherein the main storage is a disk image file of the virtual machine and a configuration file of the virtual machine;
a snapshot creating step: creating a new snapshot for the virtual machine, storing all modifications after the backup, and then finishing the backup;
in the backup judgment step, the fully backed-up and exported VM information is specifically: exporting the complete backup information of the virtual machine by an export System Definition method in an Msvm _ virtual System management service class of WMI;
in the backup judging step, the snapshot is created by a user or automatically created by the system after program backup; after the snapshot is deleted, the virtual disk file corresponding to the snapshot can be automatically merged into the main disk file; when the virtual machine is restored, the configuration file of the virtual machine does not need to provide the configuration information of the snapshot.
The acquiring of the virtual machine list and the configuration information thereof is specifically as follows:
a virtual machine list acquisition step: firstly, acquiring all virtual machine lists by using an interface class Msvm _ ComputerSystem of WMI;
the proxy step: using the self-contained Power Shell of the Windows Server as a proxy;
a configuration acquisition step: and obtaining the CPU, Memory and Network configuration of each virtual machine by remotely transmitting Power Shell related commands, wherein the commands comprise Get-VMmemory, Get-VMCPU and Get-VMNetworkAdap.
The backup judging step comprises: when the backup is incremental backup, the derivation of the VM information specifically includes:
snapshot deletion step B1: when the virtual machine is completely backed up for the first time, firstly deleting all snapshots under the virtual machine, and after the snapshots are deleted, the Hyper-V automatically merges the contents in the avhdx disk files corresponding to the snapshots into a main disk image file;
full backup step B2: deleting the snapshot, then making a complete backup, and after the complete backup is completed, creating a new snapshot for storing all modifications after the backup;
incremental backup step B3: when incremental backup is carried out, all disk files and configuration information files of the virtual machine are exported to a temporary folder, then the main disk file of the virtual machine under the temporary folder is deleted, disk files and virtual machine configuration files in the avhdx format corresponding to the snapshot are reserved, the current snapshot is deleted after the export, then a snapshot is created again, and the new snapshot stores all modifications after the backup and is also files which need to be copied during the next incremental backup.
The Virtual machine configuration file is specifically an Xml file under a Virtual Machines folder.
A Hyper-V virtual machine reduction method comprises the following steps:
start step A1, start;
virtual machine list acquisition step a 2: reading a virtual machine list from Database;
virtual machine selection step a 3: selecting a virtual machine to be restored;
backup file selection step a 4: selecting a backup file from a backup storage;
connection step a 5: establishing network sharing on a Hypervisor host, and establishing network connection according to the configured account;
download step a 6: downloading the selected backup file to the network share of step A5;
merge disks step A7: merging the disk files and modifying the configuration;
reduction step A8: starting a reduction VM;
end step a 9: and (6) ending.
In the step a7 of merging disks, the merging of the disk files requires loading of a multi-disk file, and the specific steps of loading the multi-disk file include:
search step C1: according to the time of the restoring point selected by the user, a nearest complete backup is found from the backup storage all the time;
copy step C2: copying all backup files completely backed up to the restoring point to a Virtual Hard Disk subdirectory of a default restoring folder of a remote host;
merging step C3: the method comprises the steps that contents in all disk files of incremental backup are merged into a disk image file of a complete backup, and only one main disk image file of a Vhdx virtual machine exists after merging, so that configuration information of a snapshot is not required to be provided during restoration;
reduction step C4: copying the Virtual machine configuration file at the restoring point selected by the user to the Virtual Machines subdirectory of the default restoring folder, wherein the file records the disk image file name and the disk number of the Virtual machine during each backup, and the restoring process loads the disk according to the configuration.
The reduction step C4 specifically includes the following steps:
configuration modification step C41: modifying the configuration pointing to the avhdx file to point to vhdx; because after step C3 is executed, the avhdx disk file does not exist under the default restore folder, and the configuration file in step C4 points to the avhdx file, if not modified, the restore will prompt that the disk file cannot be found;
node deletion step C42: and deleting the snapshot nodes at the same time: global _ settings/snapnotes/list; if the node is not deleted, the snapshot information cannot be found in restoration.
Configuration reduction step C43: modify InstanceId: // properties/parent _ instance _ id, consistent with the original configuration.
Example two
The technical problem to be solved by the invention comprises the following steps:
a) and acquiring all virtual machine lists and configuration information thereof on the Hypervisor host according to the configuration.
Firstly, using an interface class Msvm _ computer system of WMI to obtain all virtual machine lists, and then taking a Power Shell of a Windows Server as a proxy to obtain a CPU, a Memory and a Network configuration of each virtual machine by remotely transmitting a PS related command.
b) Acquiring and exporting all information of the virtual machine during full backup:
microsoft provides a set of WMI components to export a Hype-V virtual machine, and can export the complete backup information of the virtual machine through an export System definition method in the Msvm _ virtual System M administration service class of WMI.
c) Acquiring incremental data of the virtual machine during incremental backup;
1. when the virtual machine is completely backed up for the first time, all snapshots under the virtual machine are deleted firstly, and after the snapshots are deleted, the Hyper-V can automatically merge the contents in the avhdx disk files corresponding to the snapshots into the main disk image files.
2. And deleting the snapshot, then making a full backup, and then creating a new snapshot (the snapshot will store all the modification records after the backup).
3. When incremental backup is carried out, disk files corresponding to the snapshots avhdx and Virtual machine configuration files (Xml files under Virtual Machines folders) are exported, the current snapshot is deleted, and then a snapshot is created again (the snapshot can be stored with all modification records after the current backup)
d) And under the condition that the agent is not installed, how to remotely copy the backup files, how to copy the backup files to the Hypervisor host during restoration, and how to remotely modify the configuration files of the virtual machine.
The method comprises the following steps:
1. according to the WMI component provided by Microsoft, a remote connection to the Hypervisor host dynamically creates a shared folder.
2. And establishing the network sharing connection between the backup host and the Hypervisor host by using the configured connection account.
3. The related operations are completed on the backup host computer by accessing the network shared folder: copying files to a remote host, copying files from a remote host, modifying configuration files on a remote host, and the like.
e) When a user selects any point to restore according to backup, loading a multi-disk file;
1. the latest full backup is found all the way forward in the version control based on the time of the restore point selected by the user.
2. All backup files that are fully backed up between the restore points are copied under the default restore folder of the remote host,
3. and merging the contents (. avhdx) in the disk files of all incremental backups into the disk image file (. vhdx) in the full backup.
4. Modifying the Virtual machine configuration files in the backup folder corresponding to the restoring point, wherein the path is [ root directory ] \ Virtual Machines \ xxx ]. XML, [ xxx ] represents the GUID of the Virtual machine,
i. modify the configuration pointing to the avhdx file to point to vhdx:
deleting snapshot nodes simultaneously: global _ settings/snapnotes/list
Modify InstanceId: // properties/parent _ instance _ id
f) And the virtual machine adds or deletes a disk in the using process, and how to load a correct disk file according to the selected restoring point during restoring.
When the virtual machine is restored, the virtual machine configuration file of the selected restoration point is used.
EXAMPLE III
This embodiment is a further refinement of embodiment two.
Interpretation of professional terms:
WMI: windows Management Instrumentation, Windows Management Specification
PS：Power Shell
To solve the above problems, the present invention includes main functional modules
WMI interface module: the function module is mainly responsible for acquiring the related information of the virtual machine through a WMI interface;
a PS interface module: the functional module is mainly responsible for remotely executing commands related to backup recovery through the Power shell;
a backup module: the function module organizes all functions of the WMI interface and the PS interface according to the backup service logic to complete backup and incremental backup;
a reduction module: the module organizes all functions of the WMI interface and the PS interface according to the restoration service logic to complete the restoration function of the virtual machine.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
Finally, it should be noted that: although the present invention has been described in detail with reference to the foregoing embodiments, it will be apparent to those skilled in the art that changes may be made in the embodiments and/or equivalents thereof without departing from the spirit and scope of the invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (7)
1. A Hyper-V virtual machine backup method is characterized in that: the method comprises the steps of making a backup plan for backup and reading the backup plan to restore the virtual machine; the backup plan making method specifically comprises the following steps: acquiring all virtual machine lists and configuration information thereof on a Hypervisor host, storing the acquired virtual machine lists and the configuration information thereof in a DB, making a backup plan, storing the backup plan in the DB and backing up through the backup plan;
the backup comprises the following steps:
the starting steps are as follows: after starting up, the backup service is in a running state, a backup plan is read from the DB, and if the current time meets the execution time specified in the plan, the plan is executed; if the execution time specified in the plan is not met, continuing to wait;
a backup judgment step: judging whether the backup is a complete backup or an incremental backup according to a backup plan to be executed, and if the backup is the complete backup, deleting the snapshot and exporting VM information; if the backup is incremental backup, directly exporting VM information, and then deleting the main disk file under the exported temporary folder;
a storage step: storing the finished backup, wherein the main storage is a disk image file of the virtual machine and a configuration file of the virtual machine;
a snapshot creating step: creating a new snapshot for the virtual machine, storing all modifications after the backup, and then finishing the backup;
in the backup judgment step, the fully backed-up and exported VM information is specifically: exporting the complete backup information of the virtual machine by an export System Definition method in an Msvm _ virtual System management service class of WMI;
in the backup judging step, the snapshot is created by a user or automatically created by the system after program backup; after the snapshot is deleted, the virtual disk file corresponding to the snapshot can be automatically merged into the main disk file; when the virtual machine is restored, the configuration file of the virtual machine does not need to provide the configuration information of the snapshot.
2. The Hyper-V virtual machine backup method according to claim 1, characterized in that: the acquiring of the virtual machine list and the configuration information thereof is specifically as follows:
a virtual machine list acquisition step: firstly, acquiring all virtual machine lists by using an interface class Msvm _ ComputerSystem of WMI;
the proxy step: using the self-contained Power Shell of the Windows Server as a proxy;
a configuration acquisition step: and obtaining the CPU, Memory and Network configuration of each virtual machine by remotely transmitting Power Shell related commands, wherein the commands comprise Get-VMmemory, Get-VMCPU and Get-VMNetworkAdap.
3. The Hyper-V virtual machine backup method according to claim 1, characterized in that: the backup judging step comprises: when the backup is incremental backup, the derivation of the VM information specifically includes:
snapshot deletion step B1: when the virtual machine is completely backed up for the first time, firstly deleting all snapshots under the virtual machine, and after the snapshots are deleted, the Hyper-V automatically merges the contents in the avhdx disk files corresponding to the snapshots into a main disk image file;
full backup step B2: deleting the snapshot, then making a complete backup, and after the complete backup is completed, creating a new snapshot for storing all modifications after the backup;
incremental backup step B3: when incremental backup is carried out, all disk files and configuration information files of the virtual machine are exported to a temporary folder, then the main disk file of the virtual machine under the temporary folder is deleted, disk files and virtual machine configuration files in the avhdx format corresponding to the snapshot are reserved, the current snapshot is deleted after the export, then a snapshot is created again, and the new snapshot stores all modifications after the backup and is also files which need to be copied during the next incremental backup.
4. The Hyper-V virtual machine backup method according to claim 3, characterized in that: the Virtual machine configuration file is specifically an Xml file under a Virtual Machines folder.
5. A Hyper-V virtual machine restoration method is characterized in that: the virtual machine restoration method comprises the following steps:
start step A1, start;
virtual machine list acquisition step a 2: reading a virtual machine list from Database;
virtual machine selection step a 3: selecting a virtual machine to be restored;
backup file selection step a 4: selecting a backup file from the backup store of claim 1;
connection step a 5: establishing network sharing on a Hypervisor host, and establishing network connection according to the configured account;
download step a 6: downloading the selected backup file to the network share of step A5;
merge disks step A7: merging the disk files and modifying the configuration;
reduction step A8: starting a reduction VM;
end step a 9: and (6) ending.
6. The method for restoring the Hyper-V virtual machine according to claim 5, wherein: in the step a7 of merging disks, the merging of the disk files requires loading of a multi-disk file, and the specific steps of loading the multi-disk file include:
search step C1: according to the time of the restoring point selected by the user, a nearest complete backup is found from the backup storage all the time;
copy step C2: copying all backup files completely backed up to the restoring point to a Virtual Hard Disk subdirectory of a default restoring folder of a remote host;
merging step C3: merging the contents in all the disk files of the incremental backup into the disk image files of the complete backup, wherein only one main disk image file of the Vhdx virtual machine exists after merging, and the configuration information of the snapshot is not required to be provided during restoration;
reduction step C4: copying the Virtual machine configuration file at the restoring point selected by the user to the Virtual Machines subdirectory of the default restoring folder, wherein the file records the disk image file name and the disk number of the Virtual machine during each backup, and the restoring process loads the disk according to the configuration.
7. The method for restoring the Hyper-V virtual machine according to claim 6, wherein: the reduction step C4 specifically includes the following steps:
configuration modification step C41: modifying the configuration pointing to the avhdx file to point to vhdx;
node deletion step C42: deleting the snapshot node;
configuration reduction step C43: modify InstanceId: // properties/parent _ instance _ id, consistent with the original configuration.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111481798.2A CN114138563A (en) | 2021-12-06 | 2021-12-06 | Method for backing up and restoring Hyper-V virtual machine |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111481798.2A CN114138563A (en) | 2021-12-06 | 2021-12-06 | Method for backing up and restoring Hyper-V virtual machine |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114138563A true CN114138563A (en) | 2022-03-04 |
Family
ID=80384152
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111481798.2A Pending CN114138563A (en) | 2021-12-06 | 2021-12-06 | Method for backing up and restoring Hyper-V virtual machine |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114138563A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117112304A (en) * | 2023-08-31 | 2023-11-24 | 成都傲梅科技有限公司 | Disk cloning method and system |
-
2021
- 2021-12-06 CN CN202111481798.2A patent/CN114138563A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117112304A (en) * | 2023-08-31 | 2023-11-24 | 成都傲梅科技有限公司 | Disk cloning method and system |
| CN117112304B (en) * | 2023-08-31 | 2024-02-20 | 成都傲梅科技有限公司 | Disk cloning method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2018202512B2 (en) | Integrating composite formats with finder and explorer | |
| US10310949B1 (en) | Disaster restore of big data application with near zero RTO | |
| JP5021929B2 (en) | Computer system, storage system, management computer, and backup management method | |
| US8024292B2 (en) | Creation of a single snapshot using a server job request | |
| US7873601B1 (en) | Backup of incremental metadata in block based backup systems | |
| US7162498B2 (en) | System recovery method taking backup of data before data conversion batch and producing snapshot of volume having related table stored therein and computer system using the same | |
| JP4762972B2 (en) | System and method for a recovery unit in a database | |
| US7716185B2 (en) | Creation of a single client snapshot using a client utility | |
| US20070239725A1 (en) | Active cache offline access and management of project files | |
| US20070005915A1 (en) | Backup and restore operations using a single snapshot | |
| US20070005914A1 (en) | Backup and restore operations using a single snapshot driven by a server job request | |
| US10102083B1 (en) | Method and system for managing metadata records of backups | |
| CN102841824B (en) | Rollback method and rollback device | |
| CN110837441A (en) | KVM virtual machine backup method based on dirty data bitmap and network block equipment | |
| CN112800019A (en) | Data backup method and system based on Hadoop distributed file system | |
| CN115098299A (en) | Backup method, disaster recovery method, device and equipment for virtual machine | |
| CN114138563A (en) | Method for backing up and restoring Hyper-V virtual machine | |
| CN109508223A (en) | A kind of virtual machine batch creation method, system and equipment | |
| US8266105B2 (en) | System for automatically replicating a customer's personalized computer system image on a new computer system | |
| US20050262033A1 (en) | Data recording apparatus, data recording method, program for implementing the method, and program recording medium | |
| CN112148532A (en) | Batch recovery method and device for hard disk data, storage medium and electronic equipment | |
| US9659025B1 (en) | Automation of RSG management for backup and recovery | |
| JP2001034595A (en) | Method and device for integrating work among a plurality of systems | |
| EP1915682A2 (en) | Creation of a single client snapshot using a client utility | |
| CN117422285A (en) | Operation flow inheritance method |
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 |