CN115391106A - Method, system and device for pooling backup resources - Google Patents
Method, system and device for pooling backup resources Download PDFInfo
- Publication number
- CN115391106A CN115391106A CN202211075230.5A CN202211075230A CN115391106A CN 115391106 A CN115391106 A CN 115391106A CN 202211075230 A CN202211075230 A CN 202211075230A CN 115391106 A CN115391106 A CN 115391106A
- Authority
- CN
- China
- Prior art keywords
- backup
- snapshot
- machine
- working machine
- file
- 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/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2046—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant where the redundant components share persistent storage
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
- G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
- G06F11/2033—Failover techniques switching over of hardware resources
-
- 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/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/2097—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements maintaining the standby controller/processing unit updated
-
- 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
- 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/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
- G06F9/5077—Logical partitioning of resources; Management or configuration of virtualized resources
-
- 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
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- 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
- G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
-
- 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
- G06F2009/45579—I/O management, e.g. providing access to device drivers or storage
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/84—Using snapshots, i.e. a logical point-in-time copy of the data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/50—Indexing scheme relating to G06F9/50
- G06F2209/5011—Pool
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention belongs to the technical field of computer data disaster recovery, and discloses a method, a system and a device for pooling backup resources.
Description
Technical Field
The invention belongs to the technical field of computer data disaster recovery, and particularly relates to a method, a system and a device for pooling backup resources.
Background
At present, many backup systems of various production systems of numerous enterprises are configured one to one, and a standby machine is carried out in a cold standby, high availability or grouped mode; in the application process of the standby machine equipment, the service time and the service level of the system are not fully considered, and for different production systems distinguished by the system service time, the standby machine hardware resources cannot be reused, so that a state of repeated construction of the standby machine system is formed to a certain extent; for a production service system with high availability or low switching grade supported by the system, the use probability of the cold standby machine is extremely low, most scenes are in an idle standby state, equipment, hardware and network resources are wasted, and the repeated workload of operation and maintenance personnel is increased.
In addition, the resource management of the standby machine only has two dimensions of equipment and a system, and the unified quantitative management and resource allocation of the standby machine state, the used resources, the running condition and the switching condition are lacked, so that the high efficiency and the digitization of the standby machine resource utilization cannot be realized.
Disclosure of Invention
The present invention is directed to a method, system and apparatus for pooling backup resources, so as to solve the problems in the prior art mentioned above.
In order to achieve the purpose, the invention adopts the following technical scheme:
a method for pooling standby resources comprises the following steps:
s1, creating a snapshot according to the state of a production host, backing up data of the production host to a standby terminal and generating a virtualization file of the standby terminal;
s2, providing regular snapshot backup through a configuration strategy;
s3, completing pooling and nodularization of hardware resources through a console; nodes with the same network configuration can be bound into node groups, virtual standby machines can be established on the designated nodes or node group devices, hardware resource allocation and network resource allocation are completed, and virtual machine devices can be migrated among host nodes of different virtual platforms;
s4, the console provides the display of the use conditions of the network resources, the hard disk and storage resources, the CPU, the memory and other hardware resources of the standby machine resource pool;
and S5, the console can complete the work of creating, opening, closing, mounting the hard disk file, recovering the virtual machine snapshot and the like of the virtual machine through the VMDK file and the virtual machine snapshot file of the server under the standby resource pool.
Further, when the working machine is a vmware virtual machine, creating a snapshot and capturing a data effective block for the working machine through VADP; after the virtual machine snapshot is created, the VMDK File becomes a silent state, the VDDK can be used for reading the effective data block of the working machine at the moment, after the source end data is read, the data is written into the VMDK disk File at the designated position of the target vsan storage through the VDDK, and the incremental data is written into the VMDK disk File of the shared storage same-directory snapshot.
Further, when the working machine is a non-vmware virtual machine test, the effective block data or incremental data of the block device can be acquired by developing an agent program and deploying the agent program at the working machine end.
Further, in the backup process, the configuration information of the source end working machine and the target backup file information are recorded in a system database.
Further, the snapshot backup comprises the following steps:
firstly, if the production working machine is a virtual machine, the backup server is connected with a virtualization platform, a snapshot is created, and effective data block information is obtained; if the production working machine is a physical machine, the backup server creates a snapshot through a working machine agent program and acquires effective data block information;
then, the backup server is connected with the target virtualization platform, and if the backup is the first full backup, a basic vmdk disk file is created; if the file is the incremental backup, creating a snapshot vmdk sub-disk file;
after the data is completed, the backup program reads the data of the source end effective data block and writes the data into a vmdk file under the shared storage;
and finally, clearing the snapshot of the source end to complete the backup.
Further, the snapshot recovery steps are as follows:
firstly, a backup server selects a backup point corresponding to a working machine, selects a target virtualization platform host to be restored, and creates a target virtual machine according to the configurations of a working machine memory, a CPU, a network and the like;
secondly, mounting a vmdk disk file corresponding to the designated backup point under the shared storage, creating a temporary snapshot, and starting a virtual machine;
and then, after taking over the working machine and verifying that the application is finished, closing the virtual machine, unloading the disk, deleting the virtual machine, deleting the temporary snapshot and releasing the resource.
Further, a system for pooling resources of a backup terminal comprises a source terminal module, a storage module, a backup module and a recovery module;
the source end module is used for receiving data backup of the working machine to the standby end and generating a virtualization file of the standby machine; the storage module is used for storing the virtualized file; the backup module is used for recording the configuration information of the source end working machine and the target backup file information into a system database; and the recovery module is used for selecting backup points of the specified working machine from the backup information recorded by the database and recovering the backup information on the specified virtual platform host.
Further, a standby-side resource pooling device comprises a working machine, a backup server, a shared storage, a resource pool and a disk, wherein the working machine comprises a plurality of groups of production working machines, and the resource pool comprises a plurality of groups of virtual machines; the resource pool and the disk are connected with a shared storage, and the working machine, the backup server and the shared storage are sequentially connected.
Furthermore, the backup server runs a backup program, and is used for periodically backing up the effective data of the source-end working machine to the target shared storage, storing the full data to the host basic vmdk disk file, and storing the incremental data to the snapshot vmdk sub disk file.
Further, in the virtual platform resource pool, a working machine is created to designate and configure a virtual machine, a backup point is mounted to correspond to a disk file, the virtual machine is started to serve as a takeover machine, and after the application service verification is completed, the disk file can be unloaded, the virtual machine is deleted, and resource pool resources are released.
The invention has the technical effects and advantages that: compared with the prior art, the method, the system and the device for pooling the standby resources have the following advantages that:
in the invention, a source end production working machine can be stored in a target storage in a disk file mode, a plurality of virtual platform hosts can share the storage, when a standby machine is required to take over, only an empty virtual machine needs to be established, and a disk is mounted, so that the recovery is simple and rapid, the hardware resources of the standby machine are pooled, the resources can be distributed and used according to needs, the resources are released in time after the standby machine is used, the normal disaster recovery requirements are met, meanwhile, the hardware equipment is efficiently utilized, and the standby resource pooling method can quickly recover the system according to a strategy when a disaster happens, the disaster recovery efficiency is ensured, meanwhile, the waste of the hardware resources can be reduced, and the utilization rate of the resources of the standby machine is improved.
Drawings
FIG. 1 is a flowchart of a method for pooling standby resources according to an embodiment of the present invention;
FIG. 2 is a flow diagram of a snapshot backup process in an embodiment of the present invention;
FIG. 3 is a flow chart of a snapshot restore process in an embodiment of the present invention;
FIG. 4 is a flowchart illustrating the usage of hardware resources according to an embodiment of the present invention;
FIG. 5 is a block diagram of a system for pooling resources on a standby terminal according to an embodiment of the present invention;
fig. 6 is a block diagram of an apparatus for pooling standby resources according to an embodiment 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. The specific embodiments described herein are merely illustrative of the invention and do not delimit the invention. 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.
As shown in fig. 5, this embodiment further provides a system for pooling resources of a backup end, including a source end module, a storage module, a backup module, and a recovery module;
the source end module is used for receiving data backup of the working machine to the standby end and generating a virtualization file of the standby machine; the storage module is used for storing the virtualized file; the backup module is used for recording the configuration information of the source end working machine and the target backup file information into a system database; and the recovery module is used for selecting backup points of the specified working machine from the backup information recorded by the database and recovering the backup information on the specified virtual platform host.
As shown in fig. 6, a standby resource pooling device includes a working machine, a backup server, a shared storage, a resource pool, and a disk, where the working machine includes multiple groups of production working machines, and the resource pool includes multiple groups of virtual machines; the resource pool and the disk are connected with a shared storage, and the working machine, the backup server and the shared storage are sequentially connected.
And the backup server runs a backup program and is used for periodically backing up the effective data of the working machine of the read or received source end to a target shared storage, storing the full data into a host basic vmdk disk file, and storing the incremental data into a snapshot vmdk sub disk file. In the virtual platform resource pool, a working machine is created to designate and configure a virtual machine, a backup point is mounted to correspond to a disk file, the virtual machine is started to serve as a takeover machine, and after application service verification is completed, the disk can be unloaded, the virtual machine is deleted, and resource pool resources are released.
Based on the above system and device for pooling backup resources, an embodiment of the present invention provides a method for pooling backup resources, as shown in fig. 1 to 4, a target resource pool of the present invention selects VMware vSphere vCenter, and storage uses vssan (distributed shared storage), including the following steps:
s1, creating a snapshot according to the state of a production host, backing up data of the production host to a standby terminal and generating a virtualization file of the standby terminal;
when the working machine is a vmware virtual machine, creating a snapshot and capturing a Data effective block for the working machine through a Data Storage Protection interface (VADP); after the Virtual machine snapshot is created, the VMDK File becomes a silent state, at this time, VDDK (VMware's Virtual Disk Development Kit, VMware Virtual Disk Development toolset) can be used to read the working machine effective data block, after the source end data is read, the VDDK is written into the VMDK Disk File at the designated position of the target vsan storage, and the incremental data is written into the VMDK Disk File of the shared storage same as the directory snapshot.
When the working machine is a non-vmware virtual machine test, the effective block data or incremental data of the block equipment can be acquired by developing an agent program and deploying the agent program at the working machine end. In addition, the capturing and backup modes of the block device are not important in the present invention, and will not be described in detail herein.
S2, providing regular snapshot backup through a configuration strategy; in the backup process, the configuration information of the source end working machine and the target backup file information are recorded in a system database.
The steps of the snapshot backup are as follows:
firstly, if the production working machine is a virtual machine, a backup server is connected with a virtualization platform, a snapshot is created, and effective data block information is obtained; if the production working machine is a physical machine, the backup server creates a snapshot through a working machine agent program and acquires effective data block information;
then, the backup server is connected with the target virtualization platform, and if the first full backup is carried out, a basic vmdk disk file is created; if the file is the incremental backup, creating a snapshot vmdk sub-disk file;
after the data is completed, the backup program reads the data of the source end effective data block and writes the data into a vmdk file under the shared storage;
and finally, clearing the snapshot of the source end to complete the backup.
S3, completing pooling and nodularization of hardware resources through a console; nodes with the same network configuration can be bound into node groups, virtual standby machines can be established on the designated nodes or node group devices, hardware resource allocation and network resource allocation are completed, and virtual machine devices can be migrated among host nodes of different virtual platforms;
and S4, the console provides the display of the service conditions of the network resources, the hard disk and storage resources, the CPU, the internal memory and other hardware resources of the standby machine resource pool.
The display process is as follows: firstly, a backup server is connected with a target virtual platform resource pool, and resource usage information of the resource pool is acquired periodically. And then, displaying and monitoring the resource pool through a large screen, and carrying out risk prompt and abnormal alarm on abnormal resource use.
And S5, the console can complete the work of creating, opening, closing, mounting the hard disk file, recovering the virtual machine snapshot and the like of the virtual machine through the VMDK file and the virtual machine snapshot file of the server under the standby resource pool.
The snapshot recovery steps are as follows:
firstly, a backup server selects a backup point corresponding to a working machine, selects a target virtualization platform host to be restored, and establishes a target virtual machine according to the configuration of a working machine memory, a CPU, a network and the like;
secondly, mounting a vmdk disk file corresponding to the specified backup point under the shared storage, creating a temporary snapshot, and starting a virtual machine;
and then, after taking over the working machine and verifying that the application is finished, closing the virtual machine, unloading the disk, deleting the virtual machine, deleting the temporary snapshot and releasing the resource.
To sum up, in this embodiment, the source-end production operating machine may be stored in the target storage in a manner of a disk file, and the multiple virtual platform hosts may share the use storage, when the standby machine is required to take over, only an empty virtual machine needs to be created and a disk is mounted, so that recovery is simple and fast, resource pooling is implemented for hardware resources of the standby machine, resource allocation and use can be performed as needed, resources are released in time after use is completed, normal disaster recovery requirements are met, and meanwhile, the method for efficiently utilizing hardware devices and pooling resources of the standby end can quickly recover a system according to a policy when a disaster occurs, and while disaster recovery efficiency is ensured, waste of hardware resources can be reduced, and the utilization rate of resources of the standby machine is improved.
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 modifications may be made to the embodiments or portions thereof without departing from the spirit and scope of the invention.
Claims (10)
1. A method for pooling standby resources is characterized by comprising the following steps:
s1, creating a snapshot according to the state of a production host, backing up data of the production host to a standby terminal and generating a virtualization file of the standby terminal;
s2, providing regular snapshot backup through a configuration strategy;
s3, completing pooling and nodularization of hardware resources through a console; the nodes with the same network configuration can be bound into node groups, virtual standby machines can be established on the designated nodes or node group equipment, hardware resource allocation and network resource allocation are completed, and virtual machine equipment can be migrated among different virtual platform host nodes;
s4, the console provides the display of the use conditions of the network resources, the hard disk and storage resources, the CPU, the memory and other hardware resources of the standby machine resource pool;
and S5, the console can complete the work of creating, opening, closing, mounting the hard disk file, recovering the virtual machine snapshot and the like of the virtual machine through the VMDK file and the virtual machine snapshot file of the server under the standby resource pool.
2. The method of claim 1, wherein: when the working machine is a vmware virtual machine, creating a snapshot and capturing a data effective block for the working machine through VADP; after the virtual machine snapshot is created, the VMDK File is changed into a silent state, at the moment, the VDDK can be used for reading the effective data block of the working machine, after the source end data is read, the effective data block is written into the VMDK disk File at the designated position of the target vsan storage through the VDDK, and the incremental data is written into the VMDK disk File of the shared storage same directory snapshot.
3. The method of claim 1, wherein: when the working machine is a non-vmware virtual machine test, the effective block data or incremental data of the block equipment can be acquired by developing an agent program and deploying the agent program at the working machine end.
4. The method of claim 1, wherein: in the backup process, the configuration information of the source end working machine and the target backup file information are recorded in a system database.
5. The method of claim 1, wherein: the steps of the snapshot backup are as follows:
firstly, if the production working machine is a virtual machine, the backup server is connected with a virtualization platform, a snapshot is created, and effective data block information is obtained; if the production working machine is a physical machine, the backup server creates a snapshot through a working machine agent program and acquires effective data block information;
then, the backup server is connected with the target virtualization platform, and if the first full backup is carried out, a basic vmdk disk file is created; if the file is the incremental backup, creating a snapshot vmdk sub-disk file;
after the data is completed, the backup program reads the data of the source end effective data block and writes the data into a vmdk file under the shared storage;
and finally, clearing the snapshot of the source end to complete the backup.
6. The method of claim 1, wherein: the snapshot recovery steps are as follows:
firstly, a backup server selects a backup point corresponding to a working machine, selects a target virtualization platform host to be restored, and establishes a target virtual machine according to the configuration of a working machine memory, a CPU, a network and the like;
secondly, mounting a vmdk disk file corresponding to the designated backup point under the shared storage, creating a temporary snapshot, and starting a virtual machine;
and then, after taking over the working machine and verifying that the application is finished, closing the virtual machine, unloading the disk, deleting the virtual machine, deleting the temporary snapshot and releasing the resource.
7. A system for pooling backup resources, comprising: the device comprises a source end module, a storage module, a backup module and a recovery module;
the source end module is used for receiving data backup of the working machine to the standby end and generating a virtualization file of the standby machine; the storage module is used for storing the virtualized file; the backup module is used for recording the configuration information of the source end working machine and the target backup file information into a system database; and the recovery module is used for selecting backup points of the specified working machine from the backup information recorded by the database and recovering the backup information on the specified virtual platform host.
8. A device for pooling standby resources is characterized in that: the system comprises a working machine, a backup server, a shared storage, a resource pool and a disk, wherein the working machine comprises a plurality of groups of production working machines, and the resource pool comprises a plurality of groups of virtual machines; the resource pool and the disk are connected with a shared storage, and the working machine, the backup server and the shared storage are sequentially connected.
9. The apparatus of claim 8, wherein: and the backup server runs a backup program and is used for periodically backing up the effective data of the working machine at the reading or receiving source end to a target shared storage, storing the full data to a host basic vmdk disk file and storing the incremental data to a snapshot vmdk sub disk file.
10. The apparatus of claim 9, wherein: in the virtual platform resource pool, a working machine is created to designate and configure a virtual machine, a backup point is mounted to correspond to a disk file, the virtual machine is started to serve as a takeover machine, and after application service verification is completed, the disk can be unloaded, the virtual machine is deleted, and resource pool resources are released.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211075230.5A CN115391106A (en) | 2022-09-04 | 2022-09-04 | Method, system and device for pooling backup resources |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211075230.5A CN115391106A (en) | 2022-09-04 | 2022-09-04 | Method, system and device for pooling backup resources |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115391106A true CN115391106A (en) | 2022-11-25 |
Family
ID=84124331
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211075230.5A Pending CN115391106A (en) | 2022-09-04 | 2022-09-04 | Method, system and device for pooling backup resources |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115391106A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116578446A (en) * | 2023-07-10 | 2023-08-11 | 苏州浪潮智能科技有限公司 | Virtual machine backup method, device and system, electronic equipment and storage medium |
-
2022
- 2022-09-04 CN CN202211075230.5A patent/CN115391106A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116578446A (en) * | 2023-07-10 | 2023-08-11 | 苏州浪潮智能科技有限公司 | Virtual machine backup method, device and system, electronic equipment and storage medium |
| CN116578446B (en) * | 2023-07-10 | 2023-09-22 | 苏州浪潮智能科技有限公司 | Virtual machine backup method, device and system, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11397648B2 (en) | Virtual machine recovery method and virtual machine management device | |
| CN102981931B (en) | Backup method and device for virtual machine | |
| US7370164B1 (en) | Backup of virtual machines from the base machine | |
| US9547605B2 (en) | Method for data backup, device and system | |
| CN102394774B (en) | Service state monitoring and failure recovery method for controllers of cloud computing operating system | |
| CN111488241A (en) | Method and system for realizing agent-free backup and recovery operation on container arrangement platform | |
| CN113626256B (en) | Virtual machine disk data backup method, device, terminal and storage medium | |
| US10255124B1 (en) | Determining abnormal conditions of host state from log files through Markov modeling | |
| CN113051104B (en) | Method and related device for recovering data between disks based on erasure codes | |
| CN113886143B (en) | Virtual machine continuous data protection method and device and data recovery method and device | |
| CN103221925A (en) | Data processing method and storage equipment | |
| US9003139B1 (en) | Systems and methods for recovering virtual machines after disaster scenarios | |
| JP2007133544A (en) | Failure information analysis method and its implementation device | |
| WO2021088423A1 (en) | Memory management method and system for raid io, terminal and storage medium | |
| CN115167782B (en) | Temporary storage copy management method, system, equipment and storage medium | |
| CN104216771A (en) | Restarting method and device for software program | |
| CN114035905A (en) | Fault migration method and device based on virtual machine, electronic equipment and storage medium | |
| CN103795742B (en) | Isomery storage and disaster tolerance management system and method | |
| US11263069B1 (en) | Using unsupervised learning to monitor changes in fleet behavior | |
| CN115391106A (en) | Method, system and device for pooling backup resources | |
| CN106612314A (en) | System for realizing software-defined storage based on virtual machine | |
| CN112965783A (en) | System and method for using storage snapshot backup virtual machine | |
| US20070234114A1 (en) | Method, apparatus, and computer program product for implementing enhanced performance of a computer system with partially degraded hardware | |
| CN109582497A (en) | One kind being based on the quick emergency starting method of dynamic data increment | |
| CN115904773A (en) | Memory fault information collection method and device 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 |