CN112363807A - Production system arbitrary time pipe taking system and method thereof - Google Patents
Production system arbitrary time pipe taking system and method thereof Download PDFInfo
- Publication number
- CN112363807A CN112363807A CN202011359982.5A CN202011359982A CN112363807A CN 112363807 A CN112363807 A CN 112363807A CN 202011359982 A CN202011359982 A CN 202011359982A CN 112363807 A CN112363807 A CN 112363807A
- Authority
- CN
- China
- Prior art keywords
- data
- volume
- production
- incremental data
- backup
- 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
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- 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/45583—Memory management, e.g. access or allocation
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a production system arbitrary time take-over system and its method, the system includes producing end, storage end and disaster-tolerant end, the producing end includes producing machine and memory pool connected with customer end separately, the producing machine is connected to memory pool through CDP driver, the storage end includes the backup unit connected with service end, the service end is connected with customer end, the disaster-tolerant end includes the virtual machine connected with shared storage unit, the shared storage unit is connected with backup unit, CDP driver is used for monitoring the incremental data; the memory pool is used for storing incremental data; the client is used for transmitting the data of the production end to the server; the backup unit is used for backing up the data from the production end and synchronizing the data of the production end to the shared storage unit in a snapshot and clone volume generation mode; the virtual machine acquires data from the shared storage unit to take over production end services. Compared with the prior art, the method can effectively reduce RTO and RPO indexes and reliably take over the production system at any time point.
Description
Technical Field
The invention relates to the technical field of data disaster recovery protection, in particular to an arbitrary time take-over system and a method thereof for a production system.
Background
In order to reduce the cost of enterprise data protection and improve the protection efficiency, various data protection manufacturers propose various disaster Recovery optimization technologies, for a disaster Recovery scheme, an RTO (Recovery Time Objective) and an RPO (Recovery Point Objective) are generally used as the most basic standards, the RTO is the Time length of service interruption tolerable for an enterprise, for example, Recovery is required within half a day after a disaster occurs, the RTO value is twelve hours, the smaller the RTO value is, the stronger the data Recovery capability of a representative disaster Recovery system is; the RPO is loss tolerance of the enterprise and is used for indicating the maximum tolerable data loss amount, if the enterprise performs backup once every morning zero, after the service is recovered, only the data of the morning zero before the latest disaster occurs are stored in the system, and the frequency of data backup is increased when the RPO is required to be improved. Therefore, the good and bad of the two indexes reflect the capacity of disaster recovery technology.
The traditional data backup data logic is: during backup, the full data is firstly written into the storage medium, and then the incremental data is written into the storage medium in sequence. When the user service is down, the previously backed-up data is restored again, when the user data volume is very large, the restoration causes that the RTO and the RPO are very large, when the production system breaks down and needs to take over, the backup data are often read out from the storage medium one by one, and then the virtual machine is constructed to finish the take-over operation of the production system.
Disclosure of Invention
The present invention aims to overcome the defects of the prior art and provide a production system arbitrary time take-over system and a method thereof, so as to reduce the RTO and the RPO and achieve the purpose of taking over the production system at arbitrary time.
The purpose of the invention can be realized by the following technical scheme: an arbitrary time take-over system of a production system comprises a production end, a storage end and a disaster recovery end, wherein the production end comprises a production machine and a memory pool which are respectively connected with a client, the production machine is connected to the memory pool through a CDP (continuous Data protection) driver, the storage end comprises a backup unit connected with a service end, the service end is also connected with the client, the disaster recovery end comprises a virtual machine connected with a shared storage unit, the shared storage unit is connected with the backup unit, and the CDP driver is used for monitoring incremental Data;
the memory pool is used for storing incremental data;
the client is used for transmitting the data of the production end to the server;
the backup unit is used for backing up the data from the production end and synchronizing the data of the production end to the shared storage unit in a snapshot and clone volume generation mode;
and the virtual machine takes over the production end service by acquiring the data synchronized by the shared storage unit.
Further, the backup unit comprises a log volume and a copy data volume which are respectively connected with the server, the log volume is connected to the copy data volume, and the log volume is used for writing incremental data and synchronizing the incremental data to the copy data volume;
the copy data volume is used for writing in full data and incremental data, and cloning the snapshot and combining the incremental data in the log volume to generate a clone volume.
Further, the duplicate data volume is provided with a hole file, and the hole file is used for writing the full data and the incremental data synchronized with the log volume.
Further, the size of the hole file is the same as the size of the storage space of the production machine.
Further, the shared Storage unit is specifically an NAS (Network Attached Storage).
A production system arbitrary time take-over method comprises the following steps:
s1, the client acquires the full data from the production machine, and the CDP driver monitors the random data generated by the production machine and stores the acquired incremental data in the memory pool;
s2, recording a full-volume backup starting time point T1, transmitting full-volume data to a server by a client, backing up the full-volume data by a backup unit, and recording a full-volume data backup finishing time point T2;
s3, the client acquires the incremental data in the time from T1 to T2 from the memory pool, transmits the acquired incremental data to the server, and the backup unit backs up the incremental data in the time from T1 to T2 to complete the primary backup process of the whole quantity;
s4, continuously monitoring random data generated by the production machine by the CDP driver to obtain incremental data, and storing the incremental data in a memory pool;
s5, the client acquires the incremental data from the memory pool, transmits the incremental data to the server, and the backup unit backs up the incremental data and periodically executes snapshot operation on the backup unit;
s6, when the production end has a fault, according to the recovery time point T set by the user, inquiring to obtain a snapshot corresponding to the snapshot time point before the recovery time point T, and cloning the snapshot to obtain a clone roll;
s7, reading the incremental data from the full backup ending time point T2 to the recovery time point T from the backup unit, writing the read incremental data into the clone volume, and finishing data playback;
s8, mounting the local loop of the clone volume to a File System of a storage end, and synchronizing the data of the clone volume to a shared storage unit through an NFS (Network File System);
s9, the disaster recovery end creates a virtual machine, and the virtual machine acquires the data of the clone volume from the shared storage unit, namely, the virtual machine can take over the production end service.
Further, the step S2 specifically includes the following steps:
s21, recording a full backup starting time point T1, and transmitting full data to a server by the client;
s22, creating a copy data volume in the backup unit, formatting the copy data volume, and then creating a hole file in the copy data volume;
s23, the server side writes the received full data into the hole file of the copy data volume and records the full data backup end time point T2.
Further, the step S3 specifically includes the following steps:
s31, the client acquires the incremental data in the time from T1 to T2 from the memory pool and transmits the acquired incremental data to the server;
s32, creating a log volume in the backup unit, and writing the received incremental data in the time from T1 to T2 into the log volume by the server;
and S33, synchronously writing the incremental data written in the journal volume within the time from T1 to T2 into the hole file of the copy data volume, and finishing the process of primary backup of the whole volume.
Further, the step S5 specifically includes the following steps:
s51, the client acquires the incremental data from the memory pool and transmits the incremental data to the server;
s52, the server writes the received incremental data into the log volume, and then synchronizes the incremental data in the log volume to the hole file of the copy data volume;
and S53, periodically snapshot the copy data volume according to the set snapshot interval to obtain a plurality of snapshots.
Further, the step S7 is to read the incremental data from the journal volume from the full backup end time point T2 to the restore time point T.
Compared with the prior art, the invention has the following advantages:
the CDP driver is arranged at the production end, so that the incremental data of the production end can be monitored and obtained in real time, all data of the production end can be backed up by the storage end, and any time of follow-up pipe connection operation is facilitated; by carrying out snapshot and clone operations on the backup unit at the storage end and combining a CDM (Copy Data Management) technology, namely, synchronously mounting the clone volume to the shared storage unit of the disaster recovery end by using NFS (network file system), the virtual machine of the disaster recovery end can immediately use all Data of the production end, so that the Data protection and CDM are combined to carry out Data takeover, and the index Data of RTO and RPO can be effectively reduced.
Secondly, the invention creates a log volume and a duplicate data volume respectively in a backup unit of a storage end, stores incremental data by using the log volume, stores full data by using the duplicate data volume, and synchronously writes the incremental data in the log volume, periodically snapshots the duplicate data volume, when a user needs to take over a production end, the snapshot close to the take over time point can be automatically cloned by only setting any take over time point, and then a clone volume containing all data of the production end before the take over time point can be obtained by combining the incremental data stored in the log volume, and finally, a virtual machine of a disaster recovery end can immediately obtain all the data of the production end before the take over time point in a network mounting mode, thereby reliably realizing the purpose of taking over at any time.
Drawings
FIG. 1 is a schematic diagram of the system of the present invention;
FIG. 2 is a schematic flow diagram of the process of the present invention;
FIG. 3 is a schematic diagram of the arbitrary time take-over system of the production system in the embodiment;
FIG. 4 is a diagram illustrating correspondence between snapshots and backup data in an embodiment;
the notation in the figure is: 1. the system comprises a production end, 2, a storage end, 3, a disaster recovery end, 11, a client end, 12, a production machine, 13, a CDP driver, 14, a memory pool, 21, a service end, 22, a backup unit, 221, a log volume, 222, a copy data volume, 31, a shared storage unit, 32 and a virtual machine.
Detailed Description
The invention is described in detail below with reference to the figures and specific embodiments.
Examples
As shown in fig. 1, an arbitrary time takeover system for a production system includes a production end 1, a storage end 2, and a disaster recovery end 3, where the production end 1 includes a production machine 12 and a memory pool 14 respectively connected to a client 11, the production machine 12 is connected to the memory pool 14 through a CDP driver 13, the storage end 2 includes a backup unit 22 connected to a server 21, the server 21 is further connected to the client 11, the disaster recovery end 3 includes a virtual machine 32 connected to a shared storage unit 31, the shared storage unit 31 is connected to the backup unit 22, the CDP driver 13 is used to monitor incremental data, the memory pool 14 is used to store the incremental data, the client 11 is used to transmit the data of the production end to the server, the backup unit 22 is used to backup the data from the production end 1, and synchronize the data of the production end 1 to the shared storage unit 31 by means of snapshot and clone volume generation, the virtual machine 32 obtains the data synchronized by the shared storage unit 31, to take over the production side service, in this embodiment, the shared storage unit 31 is specifically an NAS.
The backup unit 22 includes a log volume 221 and a copy data volume 222 respectively connected to the server 21, the log volume 221 is connected to the copy data volume 222, and the log volume 221 is used for writing incremental data and synchronizing the incremental data to the copy data volume 222;
the duplicate data volume 222 is used for writing the full data and the incremental data, and by cloning the snapshot, combining the incremental data in the log volume 221 to generate a clone volume, the duplicate data volume 222 is provided with a hole file having the same size as the storage space of the production machine 12, and the hole file is used for writing the full data and the incremental data synchronized with the log volume 221.
The system is applied to practice, and a specific production system arbitrary time take-over process is shown in fig. 2, and comprises the following steps:
s1, the client 11 acquires the full data from the production machine 12, and the CDP driver 13 monitors the random data generated by the production machine 11 and stores the acquired incremental data in the memory pool 14;
s2, recording a full backup start time point T1, the client 11 transmits full data to the server 21, the backup unit 22 backs up the full data, and records a full data backup end time point T2, specifically:
firstly, creating a copy data volume 222 in the backup unit 22, formatting the copy data volume 222, and then creating a hole file in the copy data volume 222;
then, the server 21 writes the received full data into the hole file of the copy data volume 222, and records a full data backup end time point T2;
s3, the client 11 obtains the incremental data from the memory pool 14 in the time period from T1 to T2, transmits the obtained incremental data to the server 21, and the backup unit 22 backs up the incremental data in the time period from T1 to T2, specifically:
firstly, creating a log volume 221 in a backup unit 22, and writing received incremental data in time from T1 to T2 into the log volume 221 by a server 21;
incremental data written in the journal volume 221 within the time from T1 to T2 are synchronously written in a hole file of the copy data volume 222, and the full primary backup process is completed;
s4, the CDP driver 13 continuously monitors the random data generated by the production machine 11 to obtain incremental data, and stores the incremental data in the memory pool 14;
s5, the client 11 obtains the incremental data from the memory pool 14, transmits the incremental data to the server 21, the backup unit 22 backs up the incremental data, and periodically performs a snapshot operation on the backup unit 22, specifically:
the server 21 firstly writes the received incremental data into the log volume 221, and then synchronizes the incremental data in the log volume 221 to the hole file of the copy data volume 222;
periodically taking snapshots of the copy data volume 222 according to a set snapshot interval to obtain a plurality of snapshots;
s6, when the production end 1 has a fault, according to the recovery time point T set by the user, inquiring to obtain a snapshot corresponding to the snapshot time point before the recovery time point T, and cloning the snapshot to obtain a clone roll;
s7, reading the incremental data from the full backup ending time point T2 to the recovery time point T from the log volume 221 of the backup unit 22, writing the read incremental data into the clone volume, and finishing data playback;
s8, mount the local loopback of the clone volume to the file system of the storage end 2, and synchronize the data of the clone volume to the shared storage unit 31 through the NFS;
s9, the disaster recovery end 3 creates the virtual machine 32, and the virtual machine 32 acquires the data of the clone volume from the shared storage unit 31, that is, can take over the production end service.
In this embodiment, the disaster recovery end 3 selects a fusion computer virtualization platform to construct a system structure as shown in fig. 3, and monitors Data of the production end in real time through a CDP driver, and generates a "golden Copy" (i.e., a Copy Data volume) on a non-production storage end, where the "golden Copy" Data format is an original disk format, and can be virtualized again into multiple copies based on a CDM technology to be directly mounted to the disaster recovery end, where CDM (Copy Data Management) focuses on managing and utilizing backup Data, and the Copy Data is mounted through a network during recovery, so as to achieve an effect of reducing RTO; the CDP (Copy Data Management, continuous Data protection) performs real-time monitoring on the Data of the production machine, backs up the Data, and can take over at any time point by using the reference Data and the incremental Data log during recovery. The CDM and CDP technologies are combined, data protection is carried out through CDP, and data take-over is carried out through CDM, so that the purpose of reducing RTO and RPO is achieved.
The specific working process of this embodiment is as follows:
1. firstly, a CDP volume driver (monitoring random data generated by a production machine) and a client (sending data) are deployed at a production end, a server (receiving data), a log volume (storing incremental data) and a copy data volume (storing full data) are deployed at a storage end, a backup process mainly comprises a full backup and an incremental backup process, and a take-over process comprises a data playback and data sharing process.
2. The first backup process of the whole quantity: when a task is initiated, the time point is recorded as T1, the production end firstly sends the disk full data of the production machine to the storage end, simultaneously starts the CDP volume drive monitoring increment data, the storage end firstly creates a duplicate data volume with enough size, formats the duplicate data volume, then creates a hole file with the same size as the production end in the duplicate data volume, and finally directly writes the received full data into the hole file. After the full data backup is completed, recording the time point T2, and then writing the incremental data generated from the time points T1 to T2 into the log volume first and then into the hole file of the copy data volume, so that the whole full data copying process is finished.
3. An incremental backup process: the production end directly sends the incremental data monitored by the CDP driver, the storage end firstly writes the received incremental data into the log volume, simultaneously reads the incremental data in the log volume and synchronizes to the hole file of the replica data volume, and periodically performs snapshot on the replica data volume to obtain snap1, snap2 and snap3 snapshots (as shown in fig. 4, snapshot operations are performed at time points T2, T3 and T4, respectively), so that the data of the replica data volume and the data of the production end are kept consistent in real time.
4. The data playback process: when a user needs to take over the drill, if the user needs to recover to the time point T, the snapshot snap1 corresponding to the snapshot time point T2 before the time point T of the storage copy data volume is cloned (the time is short, the time is in a link form), a clone1 is generated, then the incremental data from the time point T2 to the time point T is read from the log volume and written into the clone, and the data playback is completed.
5. And (3) a data sharing process: the method comprises the steps of mounting a local loopback of a clone volume to a file system, sharing the clone volume through NFS, calling a corresponding interface of a fusioncomputer platform, adding NFS shared storage through NAS, only knowing the sharing IP and path of the NFS, and finally creating a disaster recovery virtual machine (vm1) which is configured with a production end on the storage, wherein the disk file of the fusioncomputer platform virtual machine is in a lun native format, only deleting the original disk file of the disaster recovery virtual machine, establishing a soft connection link to a backup data file in the clone volume, and when starting, the disaster recovery virtual machine can manage the service of the production end through a certain repair process, and in the specific repair process, for the Linux system: because the disk buses of the production machine and the disaster recovery machine are inconsistent, the disaster recovery machine needs to modify items in the production/etc/fstab file through a repair mode; if the production machine adopts grub2 guide, the disaster recovery machine reinstalls the grub2 guide through the rescue mode; for an xfs partition system, a disaster recovery machine system volume can normally enter the system only by repairing; a fusantcomputer platform needs to be provided with a guest driver so as to identify a disk;
for a Windows system:
a fusationcomputer platform also needs to be provided with a guest driver to identify the disk; the production machine is in a GPT partition format, and the disaster recovery machine needs to modify EFI guidance.
In this embodiment, an ESSS storage system is used as a backup medium, a virtual disk of a target virtual machine is a storage virtualization type storage, and the snapshot interval time is set to 10 minutes. Firstly, creating a test1 file from a backup to a production end, wherein the time point is T1;
when the full backup is completed, a snapshot time point snapshot1 is generated, a test2 file is created to a production end at the moment, and the time point is T2;
generating snapshot time points snapshot2 after 10 minutes, creating a test3 file to a production end at the moment, wherein the time point is T3;
then taking over the drill, and when a recovery T1 time point is selected, opening the disaster recovery virtual machine, finding a file test 1; when a recovery T2 time point is selected, the disaster recovery virtual machine is opened, and files test1 and test2 are found; when the recovery time point T3 is selected, the disaster recovery virtual machine is opened, and the files test1, test2 and test3 are found.
In this embodiment, the conventional method, CDM copy data protection, and the method proposed by the present invention are respectively adopted to perform any time takeover exercise test, so as to obtain the test results shown in table 1:
TABLE 1
| RTO | RPO | |
| Traditional disaster recovery method | On the order of days or hours | On the order of days or hours |
| CDM replica data protection | In the order of minutes or seconds | On the order of days or hours |
| The method of the invention | In the order of minutes or seconds | In the order of minutes or seconds |
As can be seen from table 1, the method provided by the present invention can effectively reduce RTO and RPO index data, and in the data disaster recovery process, the present invention does not recover data, but only pulls up user data, and ensures that the user data can be used immediately.
Claims (10)
1. An arbitrary time takeover system of a production system is characterized by comprising a production end (1), a storage end (2) and a disaster recovery end (3), wherein the production end (1) comprises a production machine (12) and a memory pool (14) which are respectively connected with a client (11), the production machine (12) is connected to the memory pool (14) through a CDP driver (13), the storage end (2) comprises a backup unit (22) connected with a service end (21), the service end (21) is also connected with the client (11), the disaster recovery end (3) comprises a virtual machine (32) connected with a shared storage unit (31), the shared storage unit (31) is connected with the backup unit (22), and the CDP driver (13) is used for monitoring incremental data;
the memory pool (14) is used for storing incremental data;
the client (11) is used for transmitting the data of the production end (1) to the server (21);
the backup unit (22) is used for backing up data from the production end (1) and synchronizing the data of the production end (1) to the shared storage unit (31) in a snapshot mode and a clone volume generation mode;
and the virtual machine (32) acquires the data synchronized by the shared storage unit (31) to take over the service of the production end (1).
2. The system for arbitrary time takeover of production system according to claim 1, wherein the backup unit (22) includes a log volume (221) and a copy data volume (222) respectively connected to the server (21), the log volume (221) is connected to the copy data volume (222), the log volume (221) is used for writing incremental data and synchronizing the incremental data into the copy data volume (222);
the replica data volume (222) is used for writing full data and incremental data, and combining the incremental data in the log volume (221) by cloning the snapshot to generate a clone volume.
3. A production system arbitrary time takeover system according to claim 2, wherein the replica data volume (222) is provided with a hole file for writing full data and incremental data synchronized with the log volume (221).
4. A production system arbitrary time takeover system according to claim 3, wherein the size of the hole file is the same as the size of the storage space of the production machine (12).
5. A production system anytime takeover system according to claim 1, wherein said shared storage unit (31) is a NAS.
6. A method for any time take-over of a production system by using the any time take-over system of the production system of claim 1, comprising the steps of:
s1, the client (11) acquires full data from the production machine (12), and meanwhile, the CDP driver (13) monitors random data generated by the production machine (12), and stores the acquired incremental data in the memory pool (14);
s2, recording a full-volume backup starting time point T1, transmitting full-volume data to a server (21) by a client (11), backing up the full-volume data by a backup unit (22), and recording a full-volume data backup finishing time point T2;
s3, the client (11) acquires the incremental data in the time from T1 to T2 from the memory pool (14), transmits the acquired incremental data to the server (21), and the backup unit (22) backs up the incremental data in the time from T1 to T2 to complete the primary backup process of the full amount;
s4, continuously monitoring random data generated by the production machine (12) by the CDP driver (13) to obtain incremental data, and storing the incremental data in a memory pool (14);
s5, the client (11) acquires the incremental data from the memory pool (14), transmits the incremental data to the server (21), and the backup unit (22) backs up the incremental data and periodically executes snapshot operation on the backup unit (22);
s6, when the production end (1) breaks down, according to the recovery time point T set by the user, inquiring to obtain a snapshot corresponding to the snapshot time point before the recovery time point T, and cloning the snapshot to obtain a clone volume;
s7, reading the incremental data from the full backup ending time point T2 to the recovery time point T from the backup unit (22), writing the read incremental data into the clone volume, and finishing data playback;
s8, mounting the local loopback of the clone volume to a file system of a storage end (2), and synchronizing the data of the clone volume to a shared storage unit (31) through NFS;
s9, the disaster recovery end (3) creates a virtual machine (32), and the virtual machine (32) acquires the data of the clone volume from the shared storage unit (31), namely, the service of the production end (1) can be taken over.
7. The method for any time takeover of the production system according to claim 6, wherein the step S2 specifically comprises the following steps:
s21, recording a full backup starting time point T1, and transmitting full data to the server (21) by the client (11);
s22, creating a copy data volume (222) in the backup unit (22), formatting the copy data volume (222), and then creating a hole file in the copy data volume (222);
s23, the server (21) writes the received full data into the hole file of the copy data volume (222), and records the full data backup end time point T2.
8. The method for any time takeover of the production system according to claim 7, wherein the step S3 specifically comprises the following steps:
s31, the client (11) acquires the incremental data in the time from T1 to T2 from the memory pool (14) and transmits the acquired incremental data to the server (21);
s32, creating a log volume (221) in the backup unit (22), and writing the received incremental data in the time from T1 to T2 into the log volume (221) by the server (21);
s33, synchronously writing the incremental data written in the journal volume (221) within the time from T1 to T2 into the hole file of the copy data volume (222), and finishing the process of primary backup of the whole volume.
9. The method for any time takeover of the production system according to claim 6, wherein the step S5 specifically comprises the following steps:
s51, the client (11) acquires the incremental data from the memory pool (14) and transmits the incremental data to the server (21);
s52, the server (21) writes the received incremental data into the log volume (221), and then synchronizes the incremental data in the log volume (221) into the hole file of the copy data volume (222);
s53, periodically snapshot the copy data volume (222) according to the set snapshot interval to obtain a plurality of snapshots.
10. The method of any time takeover of production system as claimed in claim 8, wherein said step S7 is specifically to read the incremental data from the log volume (221) from the full backup end time point T2 to the recovery time point T.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011359982.5A CN112363807A (en) | 2020-11-27 | 2020-11-27 | Production system arbitrary time pipe taking system and method thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011359982.5A CN112363807A (en) | 2020-11-27 | 2020-11-27 | Production system arbitrary time pipe taking system and method thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112363807A true CN112363807A (en) | 2021-02-12 |
Family
ID=74535484
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011359982.5A Pending CN112363807A (en) | 2020-11-27 | 2020-11-27 | Production system arbitrary time pipe taking system and method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112363807A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112988466A (en) * | 2021-04-07 | 2021-06-18 | 中国联合网络通信集团有限公司 | Data backup method, device, equipment, storage medium and program product |
| CN113360322A (en) * | 2021-06-25 | 2021-09-07 | 上海上讯信息技术股份有限公司 | Method and equipment for recovering data based on backup system |
| CN113609107A (en) * | 2021-09-30 | 2021-11-05 | 武汉四通信息服务有限公司 | Database management method and device, electronic equipment and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101495970A (en) * | 2005-06-24 | 2009-07-29 | 信科索尔特公司 | System and method for high performance enterprise data protection |
| CN105389230A (en) * | 2015-10-21 | 2016-03-09 | 上海爱数信息技术股份有限公司 | Continuous data protection system and method combining with snapshot technology |
| CN106776140A (en) * | 2016-12-21 | 2017-05-31 | 博飞信息科技（上海）有限公司 | The standby device and method for recovering all-in-one of super disaster tolerance |
| CN108255641A (en) * | 2017-12-25 | 2018-07-06 | 南京壹进制信息技术股份有限公司 | A kind of CDP disaster recovery methods based on cloud platform |
| CN109408289A (en) * | 2018-10-16 | 2019-03-01 | 国网山东省电力公司信息通信公司 | A kind of cloud disaster tolerance data processing method |
| CN110188000A (en) * | 2019-05-16 | 2019-08-30 | 上海爱数信息技术股份有限公司 | Application disaster recovery method and system based on virtualization and iSCSI or FC |
| CN111045864A (en) * | 2019-11-26 | 2020-04-21 | 上海英方软件股份有限公司 | Rapid remote recovery method and system for continuous data protection |
| CN111338844A (en) * | 2020-02-14 | 2020-06-26 | 无锡华云数据技术服务有限公司 | Database backup management method and electronic equipment |
| US20200349028A1 (en) * | 2019-04-30 | 2020-11-05 | Rubrik, Inc. | Systems and methods for continuous data protection |
-
2020
- 2020-11-27 CN CN202011359982.5A patent/CN112363807A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101495970A (en) * | 2005-06-24 | 2009-07-29 | 信科索尔特公司 | System and method for high performance enterprise data protection |
| CN105389230A (en) * | 2015-10-21 | 2016-03-09 | 上海爱数信息技术股份有限公司 | Continuous data protection system and method combining with snapshot technology |
| CN106776140A (en) * | 2016-12-21 | 2017-05-31 | 博飞信息科技（上海）有限公司 | The standby device and method for recovering all-in-one of super disaster tolerance |
| CN108255641A (en) * | 2017-12-25 | 2018-07-06 | 南京壹进制信息技术股份有限公司 | A kind of CDP disaster recovery methods based on cloud platform |
| CN109408289A (en) * | 2018-10-16 | 2019-03-01 | 国网山东省电力公司信息通信公司 | A kind of cloud disaster tolerance data processing method |
| US20200349028A1 (en) * | 2019-04-30 | 2020-11-05 | Rubrik, Inc. | Systems and methods for continuous data protection |
| CN110188000A (en) * | 2019-05-16 | 2019-08-30 | 上海爱数信息技术股份有限公司 | Application disaster recovery method and system based on virtualization and iSCSI or FC |
| CN111045864A (en) * | 2019-11-26 | 2020-04-21 | 上海英方软件股份有限公司 | Rapid remote recovery method and system for continuous data protection |
| CN111338844A (en) * | 2020-02-14 | 2020-06-26 | 无锡华云数据技术服务有限公司 | Database backup management method and electronic equipment |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112988466A (en) * | 2021-04-07 | 2021-06-18 | 中国联合网络通信集团有限公司 | Data backup method, device, equipment, storage medium and program product |
| CN113360322A (en) * | 2021-06-25 | 2021-09-07 | 上海上讯信息技术股份有限公司 | Method and equipment for recovering data based on backup system |
| CN113609107A (en) * | 2021-09-30 | 2021-11-05 | 武汉四通信息服务有限公司 | Database management method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112363807A (en) | Production system arbitrary time pipe taking system and method thereof | |
| CN105389230B (en) | A kind of continuous data protection system and method for combination snapping technique | |
| US10503616B2 (en) | Periodic data replication | |
| US8145603B2 (en) | Method and apparatus for data recovery using storage based journaling | |
| US7565572B2 (en) | Method for rolling back from snapshot with log | |
| US10067694B1 (en) | Replication ordering | |
| CN101739313B (en) | Method for protecting and restoring continuous data | |
| WO2018098972A1 (en) | Log recovery method, storage device and storage node | |
| US6035412A (en) | RDF-based and MMF-based backups | |
| US9235632B1 (en) | Synchronization of replication | |
| US6691245B1 (en) | Data storage with host-initiated synchronization and fail-over of remote mirror | |
| US8572046B2 (en) | System and method for backing up a computer system | |
| US9535801B1 (en) | Xcopy in journal based replication | |
| US10042579B1 (en) | Crash consistent snapshot | |
| US7484051B2 (en) | Apparatus, system and method for reliably updating a data group in a read-before-write data replication environment using a comparison file | |
| US7139851B2 (en) | Method and apparatus for re-synchronizing mirroring pair with data consistency | |
| CN105550062B (en) | The data reflow method restored based on continuous data protection and time point browsing | |
| US11055183B2 (en) | Data gap management in a remote data mirroring system | |
| US7546428B1 (en) | Computer architecture for managing replication of data in a data storage environment | |
| WO2020063600A1 (en) | Data disaster recovery method and site | |
| CN104461776A (en) | Application disaster tolerance method based on CDP and iSCSI virtual disk technology | |
| US10592128B1 (en) | Abstraction layer | |
| CN107256182A (en) | A kind of method and apparatus of database restoration | |
| CN101594256A (en) | Disaster recovery method, device and system | |
| CN111045864A (en) | Rapid remote recovery method and system for continuous data protection |
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 | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20210212 |