CN111045864A - Rapid remote recovery method and system for continuous data protection - Google Patents
Rapid remote recovery method and system for continuous data protection Download PDFInfo
- Publication number
- CN111045864A CN111045864A CN201911175827.5A CN201911175827A CN111045864A CN 111045864 A CN111045864 A CN 111045864A CN 201911175827 A CN201911175827 A CN 201911175827A CN 111045864 A CN111045864 A CN 111045864A
- Authority
- CN
- China
- Prior art keywords
- data
- logical volume
- clone
- recovery
- time point
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1479—Generic software techniques for error detection or fault masking
- G06F11/1489—Generic software techniques for error detection or fault masking through recovery blocks
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method and a system for fast remote recovery of continuous data protection, wherein the method comprises the following steps: step S1, storing the backed-up data on the logical volume of the file system with snapshot function, making snapshot to the data on the backed-up logical volume at regular time, the time point of making snapshot is the time base line when recovering; step S2, when restoring in different places, according to the selected restoring time point, finding the time base line nearest to the restoring time point, cloning the snapshot made at the time point of the time base line into a new clone logic volume, merging events based on the data of the cloned time base line, writing the merged events into the clone logic volume, and mounting the clone logic volume to a backup server in different places; and step S3, setting the clone logical volume after merging the data as a sharing device for the configuration connection of the working machine server to recover in different places, and realizing the purpose of rapidly recovering in different places by a remote mounting mode without remotely transmitting the data and writing a disk in different places.
Description
Technical Field
The invention relates to the technical field of computer data backup disaster recovery, in particular to a method and a system for fast remote recovery of continuous data protection based on a remote hooking mode.
Background
In the field of computers, in order to protect important data information, data backup techniques are generally employed to restore data from a backup medium when the data is unavailable. However, when recovering Data, Data between two backups may be lost, and for some critical information systems, the tolerable amount of Data loss, i.e. the Recovery Point Object (RPO) is as low as possible, requires applying Continuous Data Protection (CDP) technology.
CDP technology is a major breakthrough in the field of data backup technology, and 2011, the CDP technology group of SNIA (global network storage industry association) promulgates three conditions of CDP technology: 1. any data change can be captured; 2. at least one other place can be backed up (disaster recovery); 3. it is possible to recover to any point in time.
Typically, CDP systems continuously monitor data changes and record those changes, and after a disaster occurs, the user can select any point in time to recover to a pre-disaster state. However, in the conventional CDP remote recovery method, the target data to be recovered needs to be written into the local disk before recovery, and then the data is transmitted to the remote server through a remote transmission method. This approach has the following disadvantages:
1. in the prior art, data of a time base (Baseline) closest to a time point to be recovered needs to be written into a local disk, which easily causes the problems of disk IO consumption and overlong disk writing time;
2. the time is occupied in the transmission process of transmitting data to the remote server in a remote transmission mode, and the time is also occupied when a disk is written at the remote server, so that the remote recovery speed is influenced.
Disclosure of Invention
In order to overcome the defects of the prior art, the invention aims to provide a method and a system for fast restoring in different places with continuous data protection, which achieve the aim of fast restoring in different places by a remote mounting mode without remotely transmitting data and writing a disk in different places.
In order to achieve the above object, the present invention provides a fast remote recovery method for continuous data protection, comprising:
step S1, storing the backed-up data on the logical volume of the file system with snapshot function, and making snapshot on the backed-up data on the logical volume at regular time, the time point of making snapshot is the time base line when recovering;
step S2, when restoring in different places, according to the selected restoring time point, finding the time base line nearest to the restoring time point, cloning the snapshot made at the time point of the time base line into a new clone logical volume, merging events based on the data of the cloned time base line, writing the merged events into the clone logical volume, and mounting the clone logical volume to a backup server in different places;
and step S3, setting the clone logical volume after the data combination as a sharing device for the configuration connection of the working machine server.
Preferably, the step S2 further includes:
step S200, finding the snapshot of the nearest time base line before the recovery time point according to the selected recovery time point, and cloning to the clone logical volume;
step S201, mounting the clone logic volume;
step S202, based on the mount directory of the clone logical volume, writing the data change between the time base line and the recovery time point into the clone logical volume, and the merged data on the clone logical volume is the finally needed data which is recovered.
Preferably, in step S3, a shared disk server environment is configured on the remote backup server, and the cloned logical volume after the data merging in step S2 is set as a shared device.
Preferably, the step S3 further includes:
step S301, starting shared disk service;
step S302, adding the clone logical volume where the recovered data is located as a shared disk, and automatically mapping to an access resource area of a client;
step S303, configuring the monitoring IP and the port of the shared device service end.
Preferably, the method further comprises the steps of:
step S4, configuring the client of the sharing device on the working machine server, and connecting the sharing device of step S3.
Preferably, in step S4, the shared device client is established on the work machine server, and the new device corresponding to the server-side shared device is mounted.
Preferably, the step S4 further includes:
step S401, starting shared disk service;
s402, modifying the configuration file and establishing association with the server side sharing equipment;
step S403, according to the IP and the port number configured by the server, logging in the appointed shared storage device;
step S404, connecting to a storage device of the clone logical volume where the recovery data configured by the server is located;
step S405, checking the newly added disk device on the working machine server, and mounting the device to a local appointed directory, wherein the content in the directory is the recovered data.
In order to achieve the above object, the present invention further provides a fast remote recovery system for continuous data protection, comprising:
the remote backup server is used for acquiring disaster recovery backup data of the working machine server, storing the backup data on a logical volume of a file system with a snapshot function, and making snapshots on the backup data on the logical volume at intervals of specified time, wherein the corresponding data of each snapshot is the data of a time base line; when the remote restoration is carried out, according to the selected restoration time point, finding a time base line closest to the time point, cloning a snapshot made at the time point of the time base line into a new clone logical volume, carrying out event merging on the basis of the data of the cloned time base line, writing the event merging into the clone logical volume, mounting the clone logical volume to the remote backup server, and setting the clone logical volume after the data merging into a sharing device;
and the working machine server is used for sending disaster recovery backup data to the remote backup server for backup, configuring a sharing equipment client when the data is restored in a remote place, and connecting the sharing equipment configured by the remote backup server to realize remote restoration.
Preferably, the remote backup server comprises:
the data timing backup module is used for reading and storing full backup of data to be restored at fixed time intervals, storing the backed-up data on a logical volume of the file system with the snapshot function, and snapshotting the data on the backed-up logical volume at specified time intervals;
and the allopatric recovery processing module is used for finding a time base which is closest to the recovery time point, cloning the snapshot made at the time point of the time base into a new clone logical volume, writing the data change between the time base and the recovery time point into the clone logical volume based on an event set between the time base and the recovery time point, and mounting the clone logical volume to an allopatric backup server to be set as a sharing device.
Preferably, the allopatric recovery processing module further comprises:
the clone module is used for finding a time base line closest to the time point according to the selected recovery time point when the remote recovery is carried out, and cloning a snapshot made at the time point of the time base line into a new clone logical volume;
the mounting module is used for mounting the clone logic volume;
the disk IO operation storage module is used for reading and storing all disk IO operations between the selected recovery time point and the time base line;
the event processing module is used for merging all events corresponding to the disk IO operation, recording data change information and storing the data change information in the cloned logical volume equipment cloned based on time base line data, wherein the merged data on the cloned logical volume is the finally needed data for recovery;
and the shared device configuration module is used for setting the clone logical volume after the data are merged into a shared device.
Compared with the prior art, the method and the system for fast remote restoration of continuous data protection of the invention store the backed-up data on the logical volume of the file system with the snapshot function, take snapshots of the backed-up data on the logical volume regularly, find the time base line closest to the restoration time point according to the selected restoration time point when the remote restoration is carried out, clone the snapshots taken at the time point of the time base line into a new clone logical volume, carry out event merging and write into the clone logical volume based on the data of the cloned time base line, mount the clone logical volume to a remote backup server, finally set the clone logical volume after data merging as a sharing device for the configuration connection of a working machine server to carry out the remote restoration without remotely transmitting the data, the purpose of quickly recovering to different places can be achieved without writing different-place magnetic disks.
Drawings
FIG. 1 is a flow chart illustrating the steps of a fast remote recovery method for continuous data protection according to the present invention;
FIG. 2 is a system architecture diagram of a fast remote recovery system with continuous data protection according to the present invention;
FIG. 3 is a block diagram of a remote backup server in accordance with an embodiment of the present invention;
fig. 4 is a schematic diagram of a process of fast allopatric recovery in an embodiment of the present invention.
Detailed Description
Other advantages and capabilities of the present invention will be readily apparent to those skilled in the art from the present disclosure by describing the embodiments of the present invention with specific embodiments thereof in conjunction with the accompanying drawings. The invention is capable of other and different embodiments and its several details are capable of modification in various other respects, all without departing from the spirit and scope of the present invention.
FIG. 1 is a flow chart of steps of a fast remote recovery method for continuous data protection according to the present invention. As shown in fig. 1, the present invention provides a method for fast restoring a continuous data protection from different locations, which includes:
step S1, storing the backed-up data on the logical volume a (zfs volume) of the file system with snapshot function, and making snapshots of the data on the backed-up logical volume a at specified time intervals, where the time point of making the snapshots is the time base (Baseline) during recovery.
Specifically, in step S1, the event of the operation of the user on the working machine server a and the data change (CDP record) caused by the event are saved in a zfs (Zettabyte File System) volume a of the remote backup server B, the backup data backed up from the working machine server a to the remote backup server B is snapshot at regular time, the snapshot time point is a time base (base) at the time of recovery, and the corresponding data of each snapshot is data of the time base (base).
Step S2, when performing remote restoration, finding a time base (Baseline) closest to a selected restoration time point according to the selected restoration time point, cloning a snapshot made at the time point of the time base (Baseline) into a new clone logical volume b, performing event merging based on data of the cloned time base (Baseline), writing the event merging into the clone logical volume b, and mounting the clone logical volume b to a remote backup server.
Specifically, step S2 further includes:
step S200, when the remote restoration is carried out, when a user selects an event at a time point for restoration, according to the selected restoration time point, finding out a snapshot of a nearest time base (Baseline) in front of the time point, and cloning the snapshot to a cloning logical volume device b through zfs.
Step S201 mounts the clone logical volume b, that is, mounts the clone logical volume b to the mount directory.
Step S202, based on the mount directory of the clone logical volume b, writing the data change between the time base (Baseline) and the recovery time point (the data change may be recorded in the forward data backup process and stored in the file of the backup server) into the logical volume b, where the merged data on the clone logical volume b is the finally needed data that is recovered.
In step S3, the clone logical volume b after the data merging is set as a shared device. Specifically, the remote backup server B configures a shared disk server environment, and sets the clone logical volume B with data merged in step S2 as a shared device in an iscsiarget manner.
Specifically, step S3 further includes:
step S300, installing shared disk service software;
step S301, starting shared disk service;
step S302, adding the clone logical volume b where the recovered data is located as a shared disk, and automatically mapping to an access resource area of the client;
step S303, configuring the monitoring IP and the port of the shared device service end.
Step S4, configure the shared device client on the working machine server A and connect the shared device of step S3. Specifically, in the working machine server a, the iscsi initiator establishes the shared device client, connects the shared device in step S3, mounts the new device corresponding to the shared device at the server, that is, after the connection is successful, the working machine server a generates a new disk, mounts the disk into a directory, and can see the recovered CDP data in the mount directory.
Specifically, step S4 further includes:
step S400, installing shared disk client software;
step S401, starting shared disk service;
s402, modifying the configuration file and establishing association with the server side sharing equipment;
step S403, according to the IP and the port number configured by the server, logging in the appointed shared storage device;
step S404, connecting to the storage device of the clone logical volume b where the recovery data configured by the server is located;
step S405, look up the newly added disk device on the server a, mount the device to the local specified directory, where the content in the directory is the recovered data.
Fig. 2 is a system architecture diagram of a fast remote recovery system with continuous data protection according to the present invention. As shown in fig. 2, the present invention provides a fast remote recovery system for continuous data protection, which includes:
the remote backup server 20 is configured to obtain disaster recovery backup data of the working machine server 21, store the backup data on a logical volume a (zfs volume) of the file system having the snapshot function, and snapshot data on the backup logical volume a at specified intervals, where data corresponding to each snapshot is data of a time base (Baseline); when the remote recovery is carried out, according to the selected recovery time point, finding a time base line (Baseline) closest to the time point, cloning a snapshot made at the time point of the time base line (Baseline) into a new clone logical volume b, carrying out event merging on the basis of the data of the cloned time base line (Baseline), writing the event merging into the clone logical volume b, mounting the clone logical volume b to a remote server, and setting the clone logical volume b after the data merging as a sharing device.
Specifically, the remote backup server 20 further comprises:
the data timing backup module 201 is responsible for reading and saving full backup of data to be restored at fixed time intervals, storing the backed-up data on a logical volume a of a file system with a snapshot function, and making snapshots of the data on the backed-up logical volume a at specified time intervals, where the time point of making the snapshots is a time base (Baseline) during restoration. That is to say, the data timing backup module 201 reads and saves the full backup of the data that needs to be restored from the work machine server 21 at regular intervals, stores the backed-up data on the logical volume a (zfs volume) of the file system with the snapshot function, and performs snapshot on the backup data of the work machine server 21 at regular intervals, where the time point of snapshot is the time base (Baseline) during restoration, and the corresponding data of each snapshot is the data of the time base (Baseline).
The remote restoration processing module 202 is configured to, when performing remote restoration, find a time base (Baseline) closest to a selected restoration time point according to the selected restoration time point, clone a snapshot made at the time base (Baseline) into a new clone logical volume b, perform event merging based on data of the cloned time base (Baseline), write the event merged into the clone logical volume b, mount the clone logical volume b to a remote backup server, and set the clone logical volume b after merging data as a shared device. In the embodiment of the present invention, the event to be merged is an event set between the time base (Baseline) and the time point to be recovered, the data change in the period of time is merged and written onto the cloned logical volume b, and the data on the merged cloned logical volume b is the finally required data to be recovered
Specifically, as shown in fig. 3, the offsite recovery processing module 202 further includes:
the cloning module 2020 is configured to, when performing remote restoration, find a closest time base (Baseline) to a selected restoration time point according to the selected restoration time point, and clone a snapshot made at the time base (Baseline) as a new clone logical volume b; specifically, the recovered events at all time points and the changed data related to the events are recorded in the process of transferring the data from the working machine server to the remote backup server and are stored in the file of the remote backup server. During recovery, according to the index value of a specific event, the content of the event can be found from the event file, and the changed data can be found according to the data displacement recorded in the event structure.
A mounting module 2021, configured to mount the clone logical volume b, that is, mount the clone logical volume b to a mounting directory;
a disk IO operation saving module 2022, configured to read and save all disk IO operations between the selected recovery time point and the time base;
the event processing module 2023 is configured to merge all events corresponding to the disk IO operations, record data change information, and store the data change information in the clone logical volume device B cloned based on the time base line data, where the data on the merged clone logical volume B is finally required data for recovery;
and the shared device configuration module 2024 is configured to set the clone logical volume b after the data is merged as a shared device. Specifically, the sharing device configuring module 2024 configures a shared disk server environment in the remote backup server B, and sets the clone logical volume B with the merged data in step S2 as a sharing device in an iscsi target manner.
The working machine server 21 is configured to send disaster recovery backup data to the remote backup server 20 for backup, configure a shared device client (send a trigger signal and related configuration information to the client for configuration when recovering) when performing remote recovery, and connect with a shared device configured by the remote backup server 20. Specifically, the worker server 21 establishes a shared device client through the iscusiitiator, connects to the shared device of the remote backup server 20, mounts the new device corresponding to the server shared device, that is, after the connection is successful, the worker server generates a new disk, mounts the disk to a directory, and can see the recovered CDP data in the mount directory.
Examples
As shown in fig. 4, server a is a user work machine server, and server B is a data backup server.
And taking snapshots of data backed up from the server A to the server at regular time on the server B, wherein the corresponding data of each snapshot is the data of a Baseline time base line.
Events of the user's operations on server a and changes in data due to the events (cdp records) are saved on server B's zfs logical volume a.
When recovering, when a user selects an event at a time point for recovering, the specific steps of the server B side are as follows:
firstly, a snapshot Baseline of a nearest time base before the time point needs to be cloned to a logical volume device B through zfs, and then the cloned logical volume B is mounted.
And step two, writing the data change between the time base line and the recovery time point into the clone logical volume b based on the mount catalog of the clone logical volume.
Step three: and setting the logical volume with the merged data in the step two as a sharing device on the server B in an iscsi target mode.
And finally, establishing a shared device client at the server A end through an iscsi initiator, connecting to the shared device in the third step, generating a new disk at the server A after the connection is successful, mounting the disk to a directory, and viewing the recovered CDP data under the mounting directory.
Therefore, compared with the prior art, the invention has the following advantages:
1. because backup Baseline time Baseline data in the prior art needs to be written into a disk, and the backup Baseline time Baseline data uses snapshot instead of the disk, the disk space and the consumed time for establishing a Baseline copy are saved in the backup process, and because the disk writing needs a large amount of IO (input/output) operation, the time is slow, the snapshot mode of the invention is almost instantly completed for making the Baseline data copy, and the disk space is little occupied;
2. in the recovery process, before merging data operation is carried out based on time base line data, a traditional disk data writing mode needs to copy the data of the time base line as temporary data in order to protect the data of the time base line from being damaged, and then disk merging is carried out based on the temporary data;
3. in the prior art, data is required to be transmitted to a working machine through a network after the recovery process and the merging process, but the data is not required to be transmitted to the working machine through the network in the recovery process, so that the process of remotely transmitting the data is omitted, the operation of writing a disk after the data is transmitted to the working machine is omitted, the data is directly hung on the working machine for use, the hanging process is completed quickly, and only little time is occupied.
The foregoing embodiments are merely illustrative of the principles and utilities of the present invention and are not intended to limit the invention. Modifications and variations can be made to the above-described embodiments by those skilled in the art without departing from the spirit and scope of the present invention. Therefore, the scope of the invention should be determined from the following claims.
Claims (10)
1. A fast allopatric recovery method of continuous data protection comprises the following steps:
step S1, storing the backed-up data on the logical volume of the file system with snapshot function, and making snapshot on the backed-up data on the logical volume at regular time, the time point of making snapshot is the time base line when recovering;
step S2, when restoring in different places, according to the selected restoring time point, finding the time base line nearest to the restoring time point, cloning the snapshot made at the time point of the time base line into a new clone logical volume, merging events based on the data of the cloned time base line, writing the merged events into the clone logical volume, and mounting the clone logical volume to a backup server in different places;
and step S3, setting the clone logical volume after merging data as a sharing device for the configuration connection of the working machine server to perform remote recovery.
2. The method for fast offsite restoration with continuous data protection as claimed in claim 1, wherein the step S2 further comprises:
step S200, finding the snapshot of the nearest time base line before the recovery time point according to the selected recovery time point, and cloning to the clone logical volume;
step S201, mounting the clone logic volume;
step S202, based on the mount directory of the clone logical volume, writing the data change between the time base line and the recovery time point into the clone logical volume, and the merged data on the clone logical volume is the finally needed data which is recovered.
3. The method of claim 1, wherein the method comprises the steps of: in step S3, a shared disk server environment is configured on the remote backup server, and the cloned logical volume after the data merging in step S2 is set as a shared device.
4. The method for fast offsite recovery with continuous data protection as claimed in claim 3, wherein step S3 further comprises:
step S301, starting shared disk service;
step S302, adding the clone logical volume where the recovered data is located as a shared disk, and automatically mapping to an access resource area of a client;
step S303, configuring the monitoring IP and the port of the shared device service end.
5. The method for fast offsite restoration with continuous data protection according to claim 4, wherein said method further comprises the steps of:
step S4, configuring the client of the sharing device on the working machine server, and connecting the sharing device of step S3.
6. The method as claimed in claim 5, wherein the method comprises the following steps: in step S4, the shared device client is established on the server, and the new device corresponding to the server-side shared device is mounted.
7. The method for fast offsite recovery with continuous data protection as claimed in claim 6, wherein step S4 further comprises:
step S401, starting shared disk service;
s402, modifying the configuration file and establishing association with the server side sharing equipment;
step S403, according to the IP and the port number configured by the server, logging in the appointed shared storage device;
step S404, connecting to a storage device of the clone logical volume where the recovery data configured by the server is located;
step S405, checking the newly added disk device on the working machine server, and mounting the disk device to a local appointed directory.
8. A fast remote recovery system for continuous data protection, comprising:
the remote backup server is used for acquiring disaster recovery backup data of the working machine server, storing the backup data on a logical volume of the file system with a snapshot function, and snapshotting the data on the backup logical volume at specified time intervals; when the remote restoration is carried out, according to the selected restoration time point, finding a time base line closest to the restoration time point, cloning a snapshot made at the time point of the time base line into a new clone logical volume, carrying out event merging on the basis of the data of the cloned time base line, writing the merged data into the clone logical volume, then mounting the clone logical volume to the remote backup server, and setting the clone logical volume after the data merging into a sharing device;
and the working machine server is used for sending disaster recovery backup data to the remote backup server for backup, configuring a sharing equipment client when the data is restored in a remote place, and connecting the sharing equipment configured by the remote backup server to realize remote restoration.
9. The fast displaced restore system of continuous data protection according to claim 8, wherein said displaced backup server comprises:
the data timing backup module is used for reading and storing full backup of data to be restored at fixed time intervals, storing the backed-up data on a logical volume of the file system with the snapshot function, and snapshotting the data on the backed-up logical volume at specified time intervals;
and the allopatric recovery processing module is used for finding a time base which is closest to the recovery time point, cloning the snapshot made at the time point of the time base into a new clone logical volume, writing the data change between the time base and the recovery time point into the clone logical volume based on an event set between the time base and the recovery time point, and mounting the clone logical volume to an allopatric backup server to be set as a sharing device.
10. The fast placeshifting recovery system of claim 9 wherein the placeshifting recovery processing module further comprises:
the clone module is used for finding a time base line closest to the time point according to the selected recovery time point when the remote recovery is carried out, and cloning a snapshot made at the time point of the time base line into a new clone logical volume;
the mounting module is used for mounting the clone logic volume;
the disk IO operation storage module is used for reading and storing all disk IO operations between the selected recovery time point and the time base line;
the event processing module is used for merging all events corresponding to the disk IO operation, recording data change information and storing the data change information in the cloned logical volume equipment cloned based on time base line data, wherein the merged data on the cloned logical volume is the finally needed data for recovery;
and the shared device configuration module is used for setting the clone logical volume after the data are merged into a shared device.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911175827.5A CN111045864A (en) | 2019-11-26 | 2019-11-26 | Rapid remote recovery method and system for continuous data protection |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911175827.5A CN111045864A (en) | 2019-11-26 | 2019-11-26 | Rapid remote recovery method and system for continuous data protection |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111045864A true CN111045864A (en) | 2020-04-21 |
Family
ID=70233489
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911175827.5A Pending CN111045864A (en) | 2019-11-26 | 2019-11-26 | Rapid remote recovery method and system for continuous data protection |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111045864A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112214354A (en) * | 2020-10-21 | 2021-01-12 | 上海英方软件股份有限公司 | Rapid recovery method and device for continuous data protection |
| CN112363807A (en) * | 2020-11-27 | 2021-02-12 | 上海爱数信息技术股份有限公司 | Production system arbitrary time pipe taking system and method thereof |
| CN112612650A (en) * | 2020-12-31 | 2021-04-06 | 上海英方软件股份有限公司 | Byte-level real-time copying quick recovery method and system based on file system |
| CN112650723A (en) * | 2020-12-28 | 2021-04-13 | 北京浪潮数据技术有限公司 | File sharing method, device, equipment and computer readable storage medium |
| CN112965857A (en) * | 2021-03-03 | 2021-06-15 | 上海英方软件股份有限公司 | Method and system for rapidly recovering data based on block backup |
| CN114189512A (en) * | 2021-12-14 | 2022-03-15 | 南京欧珀软件科技有限公司 | Baseline code downloading method and device, terminal equipment and storage medium |
| CN114237989A (en) * | 2022-02-25 | 2022-03-25 | 北京奥星贝斯科技有限公司 | Database service deployment and disaster tolerance method and device |
| CN112650723B (en) * | 2020-12-28 | 2024-06-11 | 郑州浪潮数据技术有限公司 | File sharing method, device, equipment and computer readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101650680A (en) * | 2009-07-27 | 2010-02-17 | 浪潮电子信息产业股份有限公司 | Continuous data protection method based on continuous snapshots |
| CN105389230A (en) * | 2015-10-21 | 2016-03-09 | 上海爱数信息技术股份有限公司 | Continuous data protection system and method combining with snapshot technology |
| CN110109780A (en) * | 2019-07-02 | 2019-08-09 | 南京云信达科技有限公司 | A kind of file-level data backup and restoration methods for NAS service |
| CN110188000A (en) * | 2019-05-16 | 2019-08-30 | 上海爱数信息技术股份有限公司 | Application disaster recovery method and system based on virtualization and iSCSI or FC |
| CN110362424A (en) * | 2019-05-23 | 2019-10-22 | 上海英方软件股份有限公司 | A kind of quick recovery method and system based on continuous data protection |
-
2019
- 2019-11-26 CN CN201911175827.5A patent/CN111045864A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101650680A (en) * | 2009-07-27 | 2010-02-17 | 浪潮电子信息产业股份有限公司 | Continuous data protection method based on continuous snapshots |
| CN105389230A (en) * | 2015-10-21 | 2016-03-09 | 上海爱数信息技术股份有限公司 | Continuous data protection system and method combining with snapshot technology |
| CN110188000A (en) * | 2019-05-16 | 2019-08-30 | 上海爱数信息技术股份有限公司 | Application disaster recovery method and system based on virtualization and iSCSI or FC |
| CN110362424A (en) * | 2019-05-23 | 2019-10-22 | 上海英方软件股份有限公司 | A kind of quick recovery method and system based on continuous data protection |
| CN110109780A (en) * | 2019-07-02 | 2019-08-09 | 南京云信达科技有限公司 | A kind of file-level data backup and restoration methods for NAS service |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112214354A (en) * | 2020-10-21 | 2021-01-12 | 上海英方软件股份有限公司 | Rapid recovery method and device for continuous data protection |
| CN112363807A (en) * | 2020-11-27 | 2021-02-12 | 上海爱数信息技术股份有限公司 | Production system arbitrary time pipe taking system and method thereof |
| CN112650723A (en) * | 2020-12-28 | 2021-04-13 | 北京浪潮数据技术有限公司 | File sharing method, device, equipment and computer readable storage medium |
| CN112650723B (en) * | 2020-12-28 | 2024-06-11 | 郑州浪潮数据技术有限公司 | File sharing method, device, equipment and computer readable storage medium |
| CN112612650A (en) * | 2020-12-31 | 2021-04-06 | 上海英方软件股份有限公司 | Byte-level real-time copying quick recovery method and system based on file system |
| CN112612650B (en) * | 2020-12-31 | 2023-06-09 | 上海英方软件股份有限公司 | Quick recovery method and system for byte-level real-time copying based on file system |
| CN112965857A (en) * | 2021-03-03 | 2021-06-15 | 上海英方软件股份有限公司 | Method and system for rapidly recovering data based on block backup |
| CN114189512A (en) * | 2021-12-14 | 2022-03-15 | 南京欧珀软件科技有限公司 | Baseline code downloading method and device, terminal equipment and storage medium |
| CN114237989A (en) * | 2022-02-25 | 2022-03-25 | 北京奥星贝斯科技有限公司 | Database service deployment and disaster tolerance method and device |
| CN114237989B (en) * | 2022-02-25 | 2022-04-26 | 北京奥星贝斯科技有限公司 | Database service deployment and disaster tolerance method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111045864A (en) | Rapid remote recovery method and system for continuous data protection | |
| US7472139B2 (en) | Database recovery method applying update journal and database log | |
| US8554734B1 (en) | Continuous data protection journaling in data storage systems | |
| US9348827B1 (en) | File-based snapshots for block-based backups | |
| EP1455275B1 (en) | Data restoring apparatus using journal data and identification information | |
| US7668876B1 (en) | Snapshot-based replication infrastructure for efficient logging with minimal performance effect | |
| US7577806B2 (en) | Systems and methods for time dependent data storage and recovery | |
| US7865678B2 (en) | Remote copy system maintaining consistency | |
| US5619644A (en) | Software directed microcode state save for distributed storage controller | |
| US7747830B2 (en) | Backup system with continuous data protection | |
| US9098452B2 (en) | Selecting files to backup in a block level backup | |
| EP2161661B1 (en) | Computer system and backup method therefor | |
| US7979649B1 (en) | Method and apparatus for implementing a storage lifecycle policy of a snapshot image | |
| US20140344526A1 (en) | Metadata management | |
| US20050065962A1 (en) | Virtual data store creation and use | |
| US7185048B2 (en) | Backup processing method | |
| AU2016203273A1 (en) | A method for a source storage device sending data to a backup storage device for storage, and storage device | |
| KR20100099153A (en) | Determining whether to use a repository to store data updated during a resynchronization | |
| US8793452B1 (en) | Method of guaranteeing replication of data written by a mainframe to a virtual tape | |
| US7337197B2 (en) | Data migration system, method and program product | |
| KR20030017532A (en) | Data storage system and process | |
| US7506116B2 (en) | Maintaining and using information on updates to a data group after a logical copy is made of the data group | |
| WO2014079028A1 (en) | Data processing method and storage device | |
| CN110825562B (en) | Data backup method, device, system and storage medium | |
| CN112130959B (en) | Virtual machine protection system and method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |