CN110688259B - Private cloud backup recovery system and backup recovery method thereof - Google Patents
Private cloud backup recovery system and backup recovery method thereof Download PDFInfo
- Publication number
- CN110688259B CN110688259B CN201910918089.2A CN201910918089A CN110688259B CN 110688259 B CN110688259 B CN 110688259B CN 201910918089 A CN201910918089 A CN 201910918089A CN 110688259 B CN110688259 B CN 110688259B
- Authority
- CN
- China
- Prior art keywords
- platform
- backup
- virtual machine
- production platform
- processing unit
- 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.)
- Active
Links
- 238000011084 recovery Methods 0.000 title claims abstract description 48
- 238000000034 method Methods 0.000 title claims abstract description 24
- 238000004519 manufacturing process Methods 0.000 claims abstract description 89
- 238000012544 monitoring process Methods 0.000 claims abstract description 37
- 238000012545 processing Methods 0.000 claims abstract description 32
- 230000002457 bidirectional effect Effects 0.000 claims abstract description 4
- 230000001360 synchronised effect Effects 0.000 claims description 16
- 238000012423 maintenance Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 3
- 230000003203 everyday effect Effects 0.000 description 3
- 238000009825 accumulation Methods 0.000 description 2
- 230000002354 daily effect Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000010485 coping Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
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
- G06F11/1469—Backup restoration techniques
-
- 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
- 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/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/45595—Network integration; Enabling network access in virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a private cloud backup recovery system and a backup recovery method thereof, comprising a production platform, a backup platform and a monitoring processing unit, wherein the production platform is connected with the backup platform in a bidirectional manner so as to realize mutual synchronization of virtual machine basic mirror image, virtual machine data increment and network topology; the production platform is also connected with the input end of the monitoring processing unit so as to send a service state message of the production platform to the monitoring processing unit, and the monitoring processing unit judges whether the service of the production platform is normal; the output end of the monitoring processing unit is connected to the backup platform, and the working state of the backup platform is controlled according to the judgment result of the monitoring processing unit. Compared with the prior art, the method and the device have the advantages that based on the characteristic of block storage, the operation cost of a backup platform is effectively reduced and the universality is improved by directly operating the storage blocks; by means of continuously storing the data increment, the backup storage space is reduced, and the user service can be recovered quickly.
Description
Technical Field
The invention relates to the technical field of cloud storage, in particular to a private cloud backup recovery system and a backup recovery method thereof.
Background
Compared with public cloud, the private cloud has more selectable space in terms of data security and data backup, and can enhance the control capability of users on data, so that the private cloud can access data at any place through a single machine or mobile equipment by centralizing the data, thereby realizing resource sharing and collaborative work in the network, reducing the traditional resource exchange, improving the utilization rate of resources and reducing the use of mobile storage equipment.
After the cloud platform formally provides services, considering the requirements of the operational maintenance service ITSM (IT service management ) on the continuity of user services, the cloud platform must have reliable backup capability and user service recovery capability for coping with disasters, so that the user services can be quickly recovered after the disasters occur, and the cloud backup schemes currently on the market can be roughly divided into the following types:
1) Hot standby: simultaneously, two sets of identical platforms are maintained, and the data on the two sets of platforms are synchronized in real time, so that the recovery speed is high, and the operation cost is very high;
2) Snapshot-based cold backup: synchronizing full or incremental snapshots of a guest virtual machine on a backup platform every day, which method can occupy a large amount of storage space;
3) Only the application data of the client on the virtual machine is backed up: this approach requires different solutions for each type of application, reducing versatility.
The backup scheme has higher requirements on the operation cost of enterprises, is almost unbearable for small and medium-sized enterprises, and has large storage occupation space and low universality, which can reduce the user service recovery speed and increase the user service recovery time, namely, the backup scheme can not really have the cost, the recovery speed and the universality.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provide a private cloud backup recovery system and a backup recovery method thereof.
The aim of the invention can be achieved by the following technical scheme: the private cloud backup recovery system comprises a production platform, a backup platform and a monitoring processing unit, wherein the production platform is in bidirectional connection with the backup platform so as to realize mutual synchronization of a virtual machine base mirror image, a virtual machine data increment and a network topology;
the production platform is also connected with the input end of the monitoring processing unit so as to send a service state message of the production platform to the monitoring processing unit, and the monitoring processing unit judges whether the service of the production platform is normal;
the output end of the monitoring processing unit is connected to the backup platform, and the working state of the backup platform is controlled according to the judgment result of the monitoring processing unit.
Further, the production platform is provided with a first block of storage for exporting snapshot images of the virtual machine and data increments of the virtual machine;
the backup platform is provided with a second block storage and user service recovery unit, and the second block storage is used for storing the snapshot image of the virtual machine, creating a basic image corresponding to the virtual machine and storing the data increment of the virtual machine;
the user service recovery unit is used for starting user service, generating user data increment and pushing the user data increment back to the production platform.
A private cloud backup recovery method comprises the following steps:
s1, synchronizing basic mirror images: creating a virtual machine on a production platform according to the requirements of a user, deriving a snapshot image of the virtual machine from a block storage, transmitting the snapshot image of the virtual machine into a backup platform, and creating a basic image corresponding to the virtual machine by the backup platform;
s2, monitoring service states: the production platform sends the current service state information to the monitoring processing unit, the monitoring processing unit judges whether the current service state is normal, if so, the step S3 is executed, otherwise, the step S5 is executed;
s3, synchronizing network topology: the backup platform requests and stores the network topology information of the production platform in real time;
s4, synchronizing data increment: exporting a quick data increment of the virtual machine from the block storage, and then storing the data increment of the virtual machine into a corresponding basic mirror image in the backup platform;
s5, restoring the user service: according to the current synchronous network topology information and data, the backup platform starts user service and generates user data increment;
s6, pushing the recycled data increment: after the production platform is restored, the user data increment generated in the backup platform is pushed back to the production platform, so that the synchronization of the production platform and the backup platform is ensured.
Further, the step S1 specifically includes the following steps:
s11, creating a virtual machine on a production platform according to user requirements, and performing first snapshot on the virtual machine to obtain a first snapshot mirror image of the virtual machine;
s12, a first snapshot image of the virtual machine is derived from the block storage of the production platform, and at the moment, no application and data of a user exist in the first snapshot image of the virtual machine;
s13, the first snapshot image of the virtual machine is transmitted into a backup platform, a blank block is created in the block storage of the backup platform, and the first snapshot image of the virtual machine is added to the blank block to serve as a basic image corresponding to the virtual machine on the backup platform.
Further, the step S3 specifically includes the following steps:
s31, the backup platform requests the network topology information of the production platform from the production platform at preset time intervals, and the network topology information of the production platform is stored in a stack template mode;
s32, starting a working stack by using a stack template, and deleting the last stored network topology information every time the network topology information is updated and stored, so that the network topology structure of the production platform can be synchronized in real time on the backup platform.
Further, the step S4 specifically includes the following steps:
s41, performing an Nth snapshot on the virtual machine according to a preset snapshot strategy, and deriving the data increment of the Nth snapshot of the virtual machine to the Nth snapshot of the virtual machine from the block storage of the production platform;
s42, the virtual machine data increment is transmitted into the backup platform, and the virtual machine data increment is directly inserted into the corresponding basic mirror image through the block storage of the backup platform.
Further, the step S5 specifically includes the following steps:
s51, in the backup platform, generating stack templates of all computing resources according to the current synchronous network topology information and data;
s52, starting a work stack by using the stack template in the step S51, and simultaneously clearing the last work stack and generating user data increment, wherein the user service is completely restored.
Further, step S6 is specifically to re-push the user data increment generated in the backup platform during the period of waiting for the recovery of the production platform back to the production platform after the recovery of the production platform, so that the recovered production platform and the backup platform are synchronized.
Compared with the prior art, the invention has the following advantages:
1. the method is based on the characteristic of block storage, directly operates the storage blocks, does not aim at any specific type of application, and therefore has universality, and the backup is aimed at the block storage corresponding to the user virtual machine, only exports and stores the data increment of the virtual machine during the backup, and has high backup efficiency compared with the direct exporting of the snapshot of the virtual machine; and each virtual machine only has one corresponding backup, so that the storage space is reduced to the maximum extent.
2. The invention stores the incremental data of the virtual machine into the corresponding basic mirror image in the backup platform continuously, can avoid write-once when the user service is recovered, thereby reducing the data accumulation time, rapidly starting the user service when the disaster occurs, rapidly recovering the user service by adopting a working stack mode, and improving the recovery speed.
3. The backup platform is only used for storing backup when the production platform is in normal service, and operation and maintenance cost is not required to be generated; after the backup platform starts the user service and finishes the restoration of the user service, the temporary resources on the backup platform are removed by deleting the work stack, so that the operation and maintenance cost during the process of starting the user service by the backup platform is further reduced.
Drawings
FIG. 1 is a schematic diagram of a system architecture of the present invention;
FIG. 2 is a schematic flow chart of the method of the present invention;
FIG. 3 is an overall architecture diagram of private cloud backup and restore in an embodiment;
FIG. 4 is a schematic diagram of a process for synchronizing base images and virtual machine data increments in an embodiment;
the figure indicates: 1. the system comprises a production platform 11, a first block storage, a backup platform 2, a second block storage 21, a user service recovery unit 22, a monitoring processing unit 3.
Detailed Description
The invention will now be described in detail with reference to the drawings and specific examples.
As shown in fig. 1, a private cloud backup recovery system comprises a production platform 1, a backup platform 2 and a monitoring processing unit 3, wherein the production platform 1 is in bidirectional connection with the backup platform 2 so as to realize mutual synchronization of virtual machine basic mirror image, virtual machine data increment and network topology;
the production platform 1 is also connected with the input end of the monitoring processing unit 3 to send a service state message of the production platform 1 to the monitoring processing unit 3, and the monitoring processing unit 3 judges whether the service of the production platform is normal;
the output end of the monitoring processing unit 3 is connected to the backup platform 2, and the working state of the backup platform 2 is controlled according to the judgment result of the monitoring processing unit 3.
The production platform 1 is provided with a first block storage 11 for exporting snapshot images of the virtual machine and data increments of the virtual machine;
the backup platform 2 is provided with a second block storage 21 and a user service recovery unit 22, wherein the second block storage 22 is used for storing a snapshot image of the virtual machine, creating a basic image corresponding to the virtual machine and storing data increment of the virtual machine;
the user service restoration unit 21 is configured to initiate a user service, generate user data increments, and push back the user data increments to the production platform 1.
The backup and recovery method applying the private cloud backup and recovery system comprises the following steps:
s1, synchronizing basic mirror images: creating a virtual machine on a production platform according to the requirements of a user, deriving a snapshot image of the virtual machine from a block storage, transmitting the snapshot image of the virtual machine into a backup platform, and creating a basic image corresponding to the virtual machine by the backup platform;
s2, monitoring service states: the production platform sends the current service state information to the monitoring processing unit, the monitoring processing unit judges whether the current service state is normal, if so, the step S3 is executed, otherwise, the step S5 is executed;
s3, synchronizing network topology: the backup platform requests and stores the network topology information of the production platform in real time;
s4, synchronizing data increment: the data increment of the virtual machine is exported from the block storage, and then the data increment of the virtual machine is stored in a corresponding basic mirror image in the backup platform;
s5, restoring the user service: according to the current synchronous network topology information and data, the backup platform starts user service and generates user data increment;
s6, pushing the recycled data increment: after the production platform is restored, the user data increment generated in the backup platform is pushed back to the production platform, so that the synchronization of the production platform and the backup platform is ensured.
The overall framework of this embodiment is shown in fig. 3, where VM is a virtual machine (virtual machine), and the specific application process of this embodiment includes:
1. synchronous base mirror
The first step: and creating a virtual machine on the production platform according to the user requirements according to the user virtual machine requirements. Performing a first snapshot on the virtual machine, and exporting a first snapshot image of the virtual machine in a block storage of a production platform, wherein the snapshot image of the virtual machine has no application and data of a user;
and a second step of: and transmitting the first snapshot image of the virtual machine into a backup platform, creating a blank block in a block storage of the backup platform, and adding the transmitted image into the blank block to serve as a basic image corresponding to the virtual machine on the backup platform.
The execution times of the synchronous basic mirror image are executed once when a user requests a new virtual machine, in this step, it is necessary to confirm in advance with the user which user services are the settings of the disaster recovery level for the core service, that is, it is necessary to confirm the content (the first snapshot mirror image of the virtual machine) of the basic data block synchronization established by the backup platform, so that the service cloud host is directly pulled up when the disaster occurs, that is, the user service is quickly started and recovered. This is critical to reducing recovery time. For example, some cloud platforms use a manner of directly starting a cloud host by using a mirror image or a cloud hard disk, so that basic data must be synchronized to a management range of the mirror image or the cloud hard disk, instead of storing a separate external file under a directory of the system, which wastes uploading time of the mirror image or the cloud hard disk.
2. Synchronous network topology
The first step: the backup platform requests the network topology information of the production platform once every 10 minutes (the frequency is adjusted according to the actual requirement) from the production platform and stores the network topology information in the form of a stack template;
and a second step of: and starting a work stack by using a stack template (deleting the last work stack in the project when updating each time), and keeping the same network topology structure on the backup platform as that of the production platform at any time.
The execution times of the synchronous network topology can synchronize the network topology for a plurality of times a day according to the set frequency.
The reason for designing the network topology to synchronize in real time is that there are two points: first, it is guaranteed that when restoring traffic, the restoration time for the network part is reduced, since the network changes less frequently; second, it helps to confirm that disaster recovery between the production platform and the backup platform is ready, verifying compliance between the two networks. Therefore, the invention adopts the monitoring processing unit to confirm that the working state of the backup platform is reliable in real time by monitoring the service state information of the production platform.
3. Timing synchronization generated data increments
The first step: creating a timing snapshot strategy for the virtual machine of the user, and prescribing that each virtual machine is snapshot once every day, and deriving the data increment of the snapshot of each virtual machine in the current day for the snapshot of the previous day in the block storage;
and a second step of: and the data increment in each virtual machine is transmitted into a backup platform, and then the data increment is directly inserted into the corresponding basic mirror image of each virtual machine through the block storage of the backup platform, and at the moment, the application and the data of the user exist in the basic mirror image of the backup platform.
The number of times of executing the data increment of the synchronous virtual machine is at least once a day, and if the data increment is backed up for a plurality of times, the synchronization of the backup is considered to be actively carried out in real time.
Data is generated by a normal production platform every day, even every moment, and a backup platform must pay attention to the newly added data. The delta must be synchronized in time before the disaster occurs and loaded into the image so that complete synchronization of the data is maintained.
Specifically, the process of synchronizing the base image and the virtual machine data increment is shown in fig. 4: platform A is a production platform, and platform B is a backup platform.
4. Restoring user services
The first step: generating stack templates of all computing resources according to the latest network topology information and data on the backup platform;
and a second step of: the stack template is used to launch the work stack (on the order of seconds depending on the backup platform capabilities), which action will also clear the work stack previously present in the project, at which point the user service is fully restored.
The number of times of executing the recovery user service is once when the disaster occurs, and the most main consideration is the continuity of the user service when the disaster recovery is performed according to the definition in the ITSM, so that the performance of a business host and the capacity of a platform are not required to be completely consistent with the original platform. Therefore, when recovering each service host, the use of minimized computing resources, such as the minimized number of vcpus (which may be generally 2) and the minimized virtual memory size (which may be generally 4G and windows may be 8G), may not be directly reduced in terms of disk, so that the storage size of the original host may be used. This also requires that the invention, when embodied, should ensure the actual storage capacity of the backup platform, which cannot be smaller than the production environment.
While the production environment generally adopts three copies or more for high availability of storage, on the backup platform, a two-copy or non-copy mode can be considered, so that the storage utilization rate is improved as much as possible.
5. Push back user data delta
And pushing the user data increment generated in the time waiting for the production platform to recover back to the production platform on the backup platform.
The number of executions of the push-back user data increment is one time after the production platform resumes.
All the steps are automatically triggered and completed by the timing tasks, the monitoring script and the automation script. A unified application layer data backup service may be used, along with application layer data backup. For example, an application using a database may use the relevant tools at the database level when pushing back data. This stage does not recommend using incremental push back of block stores because it is not necessary for the production environment to record the state of data synchronization too much. I.e. it is not necessary for the production environment to be aware of the existence of the backup platform.
In summary, in order to ensure the continuity of user services, the present invention considers the following three aspects in the backup platform cost, the service recovery speed and the application adaptability:
1. and the operation cost of the disaster recovery platform is saved, and only the cloud with the minimum configuration is reserved. If the project names of the cloud production platforms are different, the cloud platforms can be simultaneously disaster-prepared into one backup platform to form a method of many-to-one, so that the backup cost is saved to the greatest extent, and the key points of saving the cost are as follows:
1.1 the backup platform is only used for storing backup at ordinary times, and the operation and maintenance cost is not required to be generated;
1.2, only generating one backup for the virtual machine of each user, and maximally reducing the storage cost;
1.3 the specification of the backup platform is not required to be consistent with that of the production platform, and the backup platform is used as a temporary foothold of the client application, so that the minimum resource capable of bearing the user application is ensured;
1.4 one backup platform can provide service for a plurality of cloud platforms, so that resource blank is reduced to the greatest extent;
1.5 save the user's resource topology in the form of a working stack, which can be restored quickly by one key. The backup platform can be conveniently deleted by one key after the completion of the service life, and the operation and maintenance cost during the starting of the backup platform is minimized.
2. And the recovery performance is considered, so that the service of the client can be recovered most quickly. And a plurality of incremental data are continuously added into the storage mirror images to be combined, so that daily data increment is completed, writing together during recovery is avoided, the time of data accumulation is reduced, and services can be quickly pulled up and user services can be recovered when a disaster occurs.
3. The deployment mode is simple, and the algorithm of arranging and storing the increment snapshot in the cloud service is utilized. Each cloud has a different implementation, but resource orchestration must be supported in terms of operational requirements. The invention needs to greatly utilize the arrangement mode to achieve unified release and unified recovery of resources.
4. And the method has wide applicability, and is not aimed at any specific type of application due to the fact that the storage block is directly operated, so that different types of users are satisfied.
The invention is used as a solution for balancing the operation cost and the recovery time of the client virtual machine, and is characterized in that the backup is aimed at the block storage corresponding to the client virtual machine, only the data increment is exported by utilizing the characteristic of the block storage, and the method is more efficient than directly exporting the snapshot of the virtual machine. And updating the daily increment part to the backup block storage corresponding to the block storage on the backup platform, wherein the backup is only performed on the block storage layer no matter what application the client deploys in the virtual machine. When the backup needs to be restored, all resources of the client on the production platform are restored by one key in a working stack mode, and when the production platform is restored, after the increment generated by the client on the backup platform is pushed back to the production platform, the temporary resources can be deleted by one key in a stack deleting mode, so that the purpose of multiplexing the backup platform is achieved. In the scheme, the backup platform does not ensure the high performance of the original virtual machine of the client, and only ensures the minimum resource for normal operation of the client service, so the configuration requirement on the backup platform is lower.
Claims (5)
1. The private cloud backup recovery method is applied to a private cloud backup recovery system and is characterized by comprising a production platform, a backup platform and a monitoring processing unit, wherein the production platform is in bidirectional connection with the backup platform so as to realize mutual synchronization of a virtual machine basic mirror image, a virtual machine data increment and a network topology;
the production platform is also connected with the input end of the monitoring processing unit so as to send a service state message of the production platform to the monitoring processing unit, and the monitoring processing unit judges whether the service of the production platform is normal;
the output end of the monitoring processing unit is connected to the backup platform, and the working state of the backup platform is controlled according to the judgment result of the monitoring processing unit;
the backup recovery method comprises the following steps:
s1, synchronizing basic mirror images: creating a virtual machine on a production platform according to the requirements of a user, deriving a snapshot image of the virtual machine from a block storage, transmitting the snapshot image of the virtual machine into a backup platform, and creating a basic image corresponding to the virtual machine by the backup platform;
s2, monitoring service states: the production platform sends the current service state information to the monitoring processing unit, the monitoring processing unit judges whether the current service state is normal, if so, the step S3 is executed, otherwise, the step S5 is executed;
s3, synchronizing network topology: the backup platform requests and stores the network topology information of the production platform in real time;
s4, synchronizing data increment: the data increment of the virtual machine is exported from the block storage, and then the data increment of the virtual machine is stored in a corresponding basic mirror image in the backup platform;
s5, restoring the user service: according to the current synchronous network topology information and data, the backup platform starts user service and generates user data increment;
s6, pushing the recycled data increment: after the production platform is restored, the user data increment generated in the backup platform is pushed back to the production platform so as to ensure the synchronization of the production platform and the backup platform;
the step S3 specifically includes the following steps:
s31, the backup platform requests the network topology information of the production platform from the production platform at preset time intervals, and the network topology information of the production platform is stored in a stack template mode;
s32, starting a working stack by using a stack template, and deleting the last stored network topology information every time the network topology information is updated and stored, so that the network topology structure of the production platform can be synchronized in real time on the backup platform;
the step S4 specifically comprises the following steps:
s41, performing an Nth snapshot on the virtual machine according to a preset snapshot strategy, and deriving the data increment of the Nth snapshot of the virtual machine to the Nth snapshot of the virtual machine from the block storage of the production platform;
s42, the virtual machine data increment is transmitted into the backup platform, and the virtual machine data increment is directly inserted into the corresponding basic mirror image through the block storage of the backup platform.
2. The private cloud backup recovery method according to claim 1, wherein the production platform is provided with a first block storage for exporting snapshot images of the virtual machine and data increments of the virtual machine;
the backup platform is provided with a second block storage and user service recovery unit, and the second block storage is used for storing the snapshot image of the virtual machine, creating a basic image corresponding to the virtual machine and storing the data increment of the virtual machine;
the user service recovery unit is used for starting user service, generating user data increment and pushing the user data increment back to the production platform.
3. The private cloud backup recovery method according to claim 1, wherein the step S1 specifically includes the steps of:
s11, creating a virtual machine on a production platform according to user requirements, and performing first snapshot on the virtual machine to obtain a first snapshot mirror image of the virtual machine;
s12, a first snapshot image of the virtual machine is derived from the block storage of the production platform, and at the moment, no application and data of a user exist in the first snapshot image of the virtual machine;
s13, the first snapshot image of the virtual machine is transmitted into a backup platform, a blank block is created in the block storage of the backup platform, and the first snapshot image of the virtual machine is added to the blank block to serve as a basic image corresponding to the virtual machine on the backup platform.
4. The private cloud backup recovery method according to claim 1, wherein the step S5 specifically includes the steps of:
s51, in the backup platform, generating stack templates of all computing resources according to the current synchronous network topology information and data;
s52, starting a work stack by using the stack template in the step S51, and simultaneously clearing the last work stack and generating user data increment, wherein the user service is completely restored.
5. The private cloud backup recovery method according to claim 1, wherein step S6 is specifically to re-push the user data increment generated in the backup platform in the waiting period of the production platform recovery time back to the production platform after the production platform is recovered, so as to synchronize the recovered production platform with the backup platform.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910918089.2A CN110688259B (en) | 2019-09-26 | 2019-09-26 | Private cloud backup recovery system and backup recovery method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910918089.2A CN110688259B (en) | 2019-09-26 | 2019-09-26 | Private cloud backup recovery system and backup recovery method thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110688259A CN110688259A (en) | 2020-01-14 |
| CN110688259B true CN110688259B (en) | 2024-02-06 |
Family
ID=69110405
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910918089.2A Active CN110688259B (en) | 2019-09-26 | 2019-09-26 | Private cloud backup recovery system and backup recovery method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110688259B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113535476A (en) * | 2021-07-14 | 2021-10-22 | 中盈优创资讯科技有限公司 | Method and device for rapidly recovering cloud assets |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1486020A (en) * | 2002-09-23 | 2004-03-31 | 华为技术有限公司 | Mehod for implementing network interconnection management based on asynchronous transmission mode |
| CN102394774A (en) * | 2011-10-31 | 2012-03-28 | 广东电子工业研究院有限公司 | Service state monitoring and failure recovery method for controllers of cloud computing operating system |
| CN107943557A (en) * | 2017-11-18 | 2018-04-20 | 浙江网新恒天软件有限公司 | A kind of magnetic disk of virtual machine incremental snapshot method based on cloud platform |
| CN108055327A (en) * | 2017-12-15 | 2018-05-18 | 佛山三维二次方科技有限公司 | Cloud computing experiment porch based on OpenStack |
| CN109582443A (en) * | 2018-12-06 | 2019-04-05 | 国网江西省电力有限公司信息通信分公司 | Virtual machine standby system based on distributed storage technology |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170262345A1 (en) * | 2016-03-12 | 2017-09-14 | Jenlong Wang | Backup, Archive and Disaster Recovery Solution with Distributed Storage over Multiple Clouds |
-
2019
- 2019-09-26 CN CN201910918089.2A patent/CN110688259B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1486020A (en) * | 2002-09-23 | 2004-03-31 | 华为技术有限公司 | Mehod for implementing network interconnection management based on asynchronous transmission mode |
| CN102394774A (en) * | 2011-10-31 | 2012-03-28 | 广东电子工业研究院有限公司 | Service state monitoring and failure recovery method for controllers of cloud computing operating system |
| CN107943557A (en) * | 2017-11-18 | 2018-04-20 | 浙江网新恒天软件有限公司 | A kind of magnetic disk of virtual machine incremental snapshot method based on cloud platform |
| CN108055327A (en) * | 2017-12-15 | 2018-05-18 | 佛山三维二次方科技有限公司 | Cloud computing experiment porch based on OpenStack |
| CN109582443A (en) * | 2018-12-06 | 2019-04-05 | 国网江西省电力有限公司信息通信分公司 | Virtual machine standby system based on distributed storage technology |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110688259A (en) | 2020-01-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11829263B2 (en) | In-place cloud instance restore | |
| US20200050518A1 (en) | Application migration between environments | |
| US11663085B2 (en) | Application backup and management | |
| US11016935B2 (en) | Centralized multi-cloud workload protection with platform agnostic centralized file browse and file retrieval time machine | |
| WO2020072338A1 (en) | Data backup and disaster recovery between environments | |
| CN109151045B (en) | Distributed cloud system and monitoring method | |
| US7594138B2 (en) | System and method of error recovery for backup applications | |
| CN102594849B (en) | Data backup and recovery method and device, virtual machine snapshot deleting and rollback method and device | |
| KR101970839B1 (en) | Replaying jobs at a secondary location of a service | |
| CN103176831B (en) | A kind of dummy machine system and management method thereof | |
| US11947429B2 (en) | Data disaster recovery method and site | |
| CN101908980A (en) | Network management upgrading method and system | |
| CN106790713B (en) | Across data center virtual machine migration method under cloud computing environment | |
| WO2020088533A1 (en) | Disaster recovery method and apparatus for virtualization platform | |
| CN105354113A (en) | Server, and system and method for managing server | |
| CN112380062A (en) | Method and system for rapidly recovering system for multiple times based on system backup point | |
| CN104252397A (en) | Realizing method for supporting automatic backup of cloud platform user file | |
| CN104750573A (en) | Whole-consistency back-up and restoration methods for data nodes of distributed data system | |
| WO2024120227A1 (en) | Container data protection system, method and apparatus, and device and readable storage medium | |
| WO2024103594A1 (en) | Container disaster recovery method, system, apparatus and device, and computer-readable storage medium | |
| CN110399202B (en) | Efficient virtual machine disaster recovery method and device | |
| CN110688259B (en) | Private cloud backup recovery system and backup recovery method thereof | |
| CN110972497A (en) | Disaster recovery method and device for virtualization platform | |
| CN114328009A (en) | Unified disaster recovery backup method and device for heterogeneous database based on virtualization and snapshot | |
| CN114584459B (en) | Method for realizing high availability of main and standby of container cloud platform |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |