CN107526656B - Cloud restoration method and device - Google Patents

Cloud restoration method and device Download PDF

Info

Publication number
CN107526656B
CN107526656B CN201710772413.5A CN201710772413A CN107526656B CN 107526656 B CN107526656 B CN 107526656B CN 201710772413 A CN201710772413 A CN 201710772413A CN 107526656 B CN107526656 B CN 107526656B
Authority
CN
China
Prior art keywords
snapshot
volume
version
restored
cloud
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
Application number
CN201710772413.5A
Other languages
Chinese (zh)
Other versions
CN107526656A (en
Inventor
王佳
伊泽众
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Suzhou Langchao Intelligent Technology Co Ltd
Original Assignee
Suzhou Langchao Intelligent Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Suzhou Langchao Intelligent Technology Co Ltd filed Critical Suzhou Langchao Intelligent Technology Co Ltd
Priority to CN201710772413.5A priority Critical patent/CN107526656B/en
Publication of CN107526656A publication Critical patent/CN107526656A/en
Application granted granted Critical
Publication of CN107526656B publication Critical patent/CN107526656B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1446Point-in-time backing up or restoration of persistent data
    • G06F11/1458Management of the backup or restore process
    • G06F11/1469Backup restoration techniques
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • H04L67/1095Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for supporting replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes or user terminals or syncML

Abstract

The embodiment of the invention discloses a cloud restoration method and a cloud restoration device. The method comprises the steps of judging whether a snapshot version to be restored is a previous snapshot version of a current snapshot version or not according to acquired snapshot version information to be restored; when the snapshot version to be restored is judged to be the last snapshot version of the current snapshot version, acquiring a target snapshot volume and a corresponding mapping relation at the corresponding moment in the local storage system according to the restoration time; according to the mapping relation between the target snapshot volume and the target snapshot volume, recovery data is obtained from the local storage system, so that recovery of the snapshot version is realized; the target snapshot volume is a first snapshot volume or a second snapshot volume, and the first snapshot volume and the second snapshot volume alternately read and write data and are used for recording snapshot information when the local storage system stores in the cloud. According to the technical scheme, data acquisition from a cloud end is avoided, the data acquisition time is greatly shortened, the cloud recovery rate is improved, and the cloud downloading cost can be reduced.

Description

Cloud restoration method and device
Technical Field
The embodiment of the invention relates to the technical field of storage, in particular to a cloud restoration method and device.
Background
With the rapid development of big data and cloud technology, the cloud storage technology with high mass, safety, low cost and high reliability is applied and rapidly developed.
The cloud storage technology can enable a user to store data or access data at any position of the internet without hardware environments such as a power supply, a field, a large amount of local storage space and the like, so that the management cost is saved, and the idea is made possible. The cloud storage comprises cloud backup, cloud cache, cloud mirror image, cloud layering and the like in terms of functional characteristics, wherein the cloud backup is to backup local data on a cloud end through a snapshot technology, so that the data can be rolled back locally when errors occur, the data can be continuously available, and the stability and the reliability of the whole system are ensured.
In the prior art, when performing cloud recovery, no matter the snapshot version is the earliest snapshot version or the next newer version, the recovery target snapshot data needs to be directly obtained from the cloud and then copied on the local primary volume. The data are directly acquired from the cloud, so that the acquisition speed of the data is limited by network bandwidth or cloud downloading speed, the recovery speed is low, and the cloud downloading cost is increased.
Disclosure of Invention
The embodiment of the invention aims to provide a cloud restoration method and a cloud restoration device, so as to improve the speed of cloud restoration.
In order to solve the above technical problems, embodiments of the present invention provide the following technical solutions:
an embodiment of the present invention provides a cloud restoration method, including:
judging whether the snapshot version to be restored is the previous snapshot version of the current snapshot version or not according to the acquired snapshot version information to be restored;
when the snapshot version to be restored is judged to be the last snapshot version of the current snapshot version, acquiring a target snapshot volume and a corresponding mapping relation at the corresponding moment in a local storage system according to the restoration time;
according to the mapping relation between the target snapshot volume and the target snapshot volume, recovery data is obtained from the local storage system, so that recovery of a snapshot version is achieved;
the target snapshot volume is a first snapshot volume or a second snapshot volume, the local storage system includes a first snapshot volume, a second snapshot volume, a first mapping and a second mapping, and is used for recording snapshot information of the local storage system when the local storage system stores in a cloud, the first snapshot volume and the second snapshot volume alternately read and write data, the first mapping is a mapping relationship between the first snapshot volume and an original volume, and the second mapping is a mapping relationship between the second snapshot volume and the original volume.
Optionally, the determining, according to the obtained information of the snapshot version to be restored, whether the snapshot version to be restored is a previous snapshot version of the current snapshot version includes:
and judging whether the snapshot version to be restored is the previous snapshot version of the current snapshot version or not according to the restoration time of the acquired snapshot version to be restored and the time of the current snapshot version.
Optionally, the determining, according to the obtained information of the snapshot version to be restored, whether the snapshot version to be restored is a previous snapshot version of the current snapshot version includes:
and judging whether the snapshot version to be restored is the last snapshot version of the current snapshot version or not according to the acquired restoration version identification number of the snapshot version to be restored and the version identification number of the current snapshot version.
Another aspect of the embodiments of the present invention provides a cloud restoration apparatus, including:
the judging module is used for judging whether the snapshot version to be restored is the previous snapshot version of the current snapshot version or not according to the acquired snapshot version to be restored information;
the acquisition module is used for acquiring a target snapshot volume and a corresponding mapping relation at a corresponding moment in the local storage system according to the restoration time when the snapshot version to be restored is judged to be the previous snapshot version of the current snapshot version; the target snapshot volume is a first snapshot volume or a second snapshot volume, the local storage system comprises a first snapshot volume, a second snapshot volume, a first mapping and a second mapping, and is used for recording snapshot information when the local storage system stores in a cloud, the first snapshot volume and the second snapshot volume alternately read and write data, the first mapping is a mapping relation between the first snapshot volume and an original volume, and the second mapping is a mapping relation between the second snapshot volume and the original volume;
and the restoration module is used for acquiring restoration data from the local storage system according to the mapping relation between the target snapshot volume and the target snapshot volume so as to realize restoration of the snapshot version.
Optionally, the determining module is a module that determines whether the snapshot version to be restored is a previous snapshot version of the current snapshot version according to the restoration time of the acquired snapshot version to be restored and the time of the current snapshot version.
Optionally, the determining module is a module that determines whether the snapshot version to be restored is a previous snapshot version of the current snapshot version according to the acquired restoration version identification number of the snapshot version to be restored and the version identification number of the current snapshot version.
The embodiment of the invention provides a cloud restoration method, which comprises the steps of judging whether a snapshot version to be restored is a previous snapshot version of a current snapshot version or not according to acquired snapshot version information to be restored; when the snapshot version to be restored is judged to be the last snapshot version of the current snapshot version, acquiring a target snapshot volume and a corresponding mapping relation at the corresponding moment in the local storage system according to the restoration time; according to the mapping relation between the target snapshot volume and the target snapshot volume, recovery data is obtained from the local storage system, so that recovery of the snapshot version is realized; the target snapshot volume is a first snapshot volume or a second snapshot volume, and the first snapshot volume and the second snapshot volume alternately read and write data and are used for recording snapshot information when the local storage system stores in the cloud.
The technical scheme provided by the application has the advantages that based on the characteristic that two mapping and two snapshot volumes work alternately during cloud backup, because the local storage system stores two snapshot volumes which are the latest moment and the next-to-last moment respectively, when the snapshot version to be restored is the next-to-last version, namely the last version of the current snapshot version, the data can be directly copied from the local storage system, restoration is carried out, data acquisition from a cloud end is avoided, the time for acquiring the data is greatly shortened, the speed for restoring the cloud is improved, and the cost for downloading the cloud can be reduced.
In addition, the embodiment of the invention also provides a corresponding implementation device for the cloud restoration method, so that the method has higher practicability and the device has corresponding advantages.
Drawings
In order to more clearly illustrate the embodiments or technical solutions of the present invention, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
Fig. 1 is a schematic flow chart of a cloud restoration method according to an embodiment of the present invention;
fig. 2 is a schematic diagram illustrating establishment of a snapshot volume of a local storage system according to an embodiment of the present invention;
fig. 3 is a schematic diagram illustrating a cloud storage snapshot method according to an embodiment of the present invention;
fig. 4 is a structural diagram of a specific embodiment of a cloud restoration device according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the disclosure, the invention will be described in further detail with reference to the accompanying drawings and specific embodiments. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terms "first," "second," "third," "fourth," and the like in the description and claims of this application and in the above-described drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "comprising" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may include other steps or elements not expressly listed.
Having described the technical solutions of the embodiments of the present invention, various non-limiting embodiments of the present application are described in detail below.
Referring to fig. 1, fig. 1 is a schematic flow chart of a cloud restoration method according to an embodiment of the present invention, where the embodiment of the present invention may include the following:
s101: and judging whether the snapshot version to be restored is the previous snapshot version of the current snapshot version or not according to the acquired snapshot version information to be restored.
The version information of the snapshot to be restored may include the time of the snapshot version to be restored and the version number of the snapshot version to be restored, and of course, may also include other information during the snapshot, which does not affect the implementation of the present application.
And judging whether the snapshot version to be restored is the previous snapshot version of the current snapshot version or not according to the restoration time of the acquired snapshot version to be restored and the time of the current snapshot version.
And judging whether the snapshot version to be restored is the previous snapshot version of the current snapshot version or not according to the acquired restoration version identification number of the snapshot version to be restored and the version identification number of the current snapshot version.
The previous snapshot version volume is the previous snapshot version of the current snapshot version, the time of the to-be-restored snapshot version is the time of performing the snapshot of the snapshot version (i.e. the restoration time), for example, the original volume v is respectively at t0、t1、t2、t3、t4Taking 4 snapshots, when taking 5 th snapshot, its last snapshot version is t4Snapshots corresponding in time, i.e. t0Is t1Last snapshot version, t2Is t3Last snapshot version, t3Is t4The last snapshot version.
Each snapshot version has a unique identification number, and the generation of the general identifiable numbers is named according to the sequence of the snapshots, so that whether the snapshot version is the previous version can be determined by comparing the snapshot restoration time with the current version time, and certainly, the judgment can also be performed by comparing the version numbers, for example, the version number of the current snapshot version is v1.2.2, and the version number of the snapshot version to be restored can be v1.2.1, so that the snapshot version to be restored can be determined to be the previous snapshot version of the current snapshot version, i.e., the next new snapshot.
S102: and when the snapshot version to be restored is judged to be the last snapshot version of the current snapshot version, acquiring the corresponding mapping relation between the target snapshot volume at the corresponding moment and the corresponding snapshot volume in the local storage system according to the restoration time.
S103: and according to the mapping relation between the target snapshot volume and the target snapshot volume, acquiring recovery data from the local storage system to realize recovery of the snapshot version.
The target snapshot volume is a first snapshot volume or a second snapshot volume, the local storage system comprises the first snapshot volume, the second snapshot volume, a first mapping and a second mapping and is used for recording snapshot information when the local storage system stores in a cloud, the first snapshot volume and the second snapshot volume alternately read and write data, the first mapping is a mapping relation between the first snapshot volume and an original volume, and the second mapping is a mapping relation between the second snapshot volume and the original volume.
The corresponding mapping relationship is a mapping relationship between the target snapshot volume and the primary volume, for example, when the target snapshot volume is the first snapshot volume, the corresponding mapping relationship is the first mapping.
When the cloud enablement of the primary volume is detected, that is, when the primary volume in the local storage system is converted into the cloud volume, a first snapshot volume, a second snapshot volume, a first mapping and a second mapping are created in the local storage system in advance, wherein the first mapping is a mapping relation between the first snapshot volume and the primary volume, the second mapping is a mapping relation between the second snapshot volume and the primary volume, and the mapping can be represented by using a bitmap. For example, as shown in fig. 2, when a primary volume V of the local storage system has four blocks of data, and V is converted into a cloud volume, the local storage system automatically generates two new self-compaction volumes, that is, a first snapshot volume FCA and a second snapshot volume FCB, and mappings fcmapA and fcmapB that the primary volume corresponds to the two snapshot volumes.
When the primary volume is subjected to cloud storage, snapshot operation is required, when the primary volume is subjected to snapshot for the first time, full-volume copy is performed, incremental copy is performed from the second time to the later time, and when snapshot is performed, the first snapshot volume and the second snapshot volume and the first mapping and the second mapping work alternately, for example, t0In time, the initialization volumes FCA and fcmapA are 0000, fcmapB is 1111, and the cloud end t0The time of day data is a full copy of the original volume, the actual data is read from volume FCA, and which block to read from depends on the location of 1 in fcmapB. t is t0To t1In the meantime, when there is a host IO, COW is executed, fcapa changes the COW block to 1, and volume FCA records COW old data. t is t1When the initialization volumes FCB and fcmapB are 0000, fcmapA is unchanged. The cloud end t1 data at the moment t0To t1The delta data of (1), which location the data is read from the volume FCB, is the location of 1 in fcmapA. t is t2When the initialization is returned alternately, the initialization volume FCA and fcmapA are 0000, and fcmapB is unchanged. Cloud terminal t2Time data is t1To t2The delta data of (1), which location the data is read from volume FCA, is the location of 1 in fcmapB. And so on.
The two snapshot volumes in the local storage system are respectively the snapshot version at the latest moment and the snapshot version at the next latest moment, so that the recovery data can be directly read from the snapshot volume corresponding to the next new version and the corresponding relationship when the snapshot version at the next latest moment is recovered.
For example, if the data of the current snapshot version is read from the volume FCA, the corresponding target snapshot volume of the next new version is the volume FCB, and the recovery data can be obtained according to the volume FCB and fcmapB.
In the technical scheme provided by the embodiment of the invention, based on the characteristic that two mapping and two snapshot volumes work alternately during cloud backup, because the local storage system stores two snapshot volumes which are respectively the latest moment and the next latest moment, when the snapshot version to be restored is the next newer version, namely the last version of the current snapshot version, the data can be directly copied from the local storage system for restoration, so that the data acquisition from a cloud end is avoided, the data acquisition time is greatly shortened, the cloud restoration rate is improved, and the cloud downloading cost can be reduced.
In order to make those skilled in the art better understand the technical solution provided by the present application, the present application describes the technical solution of the present application with a specific example, please refer to fig. 3, which specifically includes:
t0time of day creation snapshot g1Initializing fcmapA and FCA; t is t1Time of day creation snapshot g2Initializing fcmapB and FCB; t is t1To t2Meanwhile, the host io writes to the first block of the primary volume v (black data block is filled in the figure), fcmapB becomes 1000, and the first block in FCB stores the old data of COW. t is t2At that time, the primary volume v data is white and black (the color of the data block), a third cloud snapshot is created, and the initialization fcmapA is alternately triggered to 0000 and the FCA data is empty. Then, data is copied to the cloud end in an incremental mode, and because fcmapB is 1000, the first block of data needs to be copied to the cloud end g3The first block location. Since fcmapA is 0000, data is read from the primary volume v, i.e., just t1To t2The first block of data written by the host, i.e., delta data. After copying to the cloud, g33121 indicates that the first block of data is stored in g3The second and fourth data are stored in g1The third block of data is stored in g2The above.
The latest snapshot data (i.e., g)3) Point to FCA, next new snapshot data (i.e., g)2) Pointing to the FCB. If it is recovered to g2Then, the FCB and fcmapB are read locally. Since fcmapB is 1000, the first block of data is copied from the FCB read to the primary volume v, and the other blocks are on the primary volume v without restoration. The data of the original volume v after recovery is white and black, and meets the requirement of creating g2Time t1Time of day data.
According to the fast cloud restoration method, the two snapshot volumes are stored locally and are updated and updated at the next time, and if the restoration target snapshot is updated, data are directly obtained locally for copy restoration and are not obtained from the cloud. The recovery speed is improved, and the cloud downloading cost is reduced.
The embodiment of the invention also provides a corresponding implementation device for the cloud restoration method, so that the method has higher practicability. In the following, the cloud restoration device provided by the embodiment of the present invention is introduced, and the cloud restoration method device described below and the cloud restoration method described above may be referred to correspondingly.
Referring to fig. 4, fig. 4 is a structural diagram of a cloud restoration device according to an embodiment of the present invention, in a specific implementation manner, where the device may include:
the determining module 401 is configured to determine, according to the obtained version information of the snapshot to be restored, whether the snapshot version to be restored is a previous snapshot version of the current snapshot version.
An obtaining module 402, configured to, when it is determined that the snapshot version to be restored is a previous snapshot version of the current snapshot version, obtain, in the local storage system, a target snapshot volume and a corresponding mapping relationship at a corresponding moment according to restoration time; the target snapshot volume is a first snapshot volume or a second snapshot volume, the local storage system comprises the first snapshot volume, the second snapshot volume, a first mapping and a second mapping and is used for recording snapshot information when the local storage system stores in a cloud, the first snapshot volume and the second snapshot volume alternately read and write data, the first mapping is a mapping relation between the first snapshot volume and an original volume, and the second mapping is a mapping relation between the second snapshot volume and the original volume.
The restoring module 403 is configured to obtain restoring data from the local storage system according to the target snapshot volume and the mapping relationship, so as to restore the snapshot version.
Optionally, in some embodiments of this embodiment, the determining module 401 may be a module that determines whether the snapshot version to be restored is a previous snapshot version of the current snapshot version according to the acquired restoration time of the snapshot version to be restored and the time of the current snapshot version.
In other embodiments, the determining module 401 may also be a module that determines whether the snapshot version to be restored is a previous snapshot version of the current snapshot version according to the acquired restoration version identification number of the snapshot version to be restored and the version identification number of the current snapshot version.
The functions of the functional modules of the cloud restoration device according to the embodiment of the present invention may be specifically implemented according to the method in the foregoing method embodiment, and the specific implementation process may refer to the related description of the foregoing method embodiment, which is not described herein again.
As can be seen from the above, in the embodiment of the present invention, based on the characteristic that two mappings and two snapshot volumes alternately work during cloud backup, since the local storage system stores two snapshot volumes, which are the latest time and the next latest time, when the snapshot version to be restored is the next newer version, that is, the last version of the current snapshot version, data can be directly copied from the local storage system for restoration, thereby avoiding data acquisition from the cloud, greatly reducing the time for data acquisition, improving the speed of cloud restoration, and also reducing the cost of cloud downloading.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The cloud restoration method and the cloud restoration device provided by the invention are described in detail above. The principles and embodiments of the present invention are explained herein using specific examples, which are presented only to assist in understanding the method and its core concepts. It should be noted that, for those skilled in the art, it is possible to make various improvements and modifications to the present invention without departing from the principle of the present invention, and those improvements and modifications also fall within the scope of the claims of the present invention.

Claims (6)

1. A cloud restoration method, comprising:
judging whether the snapshot version to be restored is the previous snapshot version of the current snapshot version or not according to the acquired snapshot version information to be restored;
when the snapshot version to be restored is judged to be the last snapshot version of the current snapshot version, acquiring a target snapshot volume and a corresponding mapping relation at the corresponding moment in a local storage system according to the restoration time;
according to the mapping relation between the target snapshot volume and the target snapshot volume, recovery data is obtained from the local storage system, so that recovery of a snapshot version is achieved;
the target snapshot volume is a first snapshot volume or a second snapshot volume, the local storage system comprises a first snapshot volume, a second snapshot volume, a first mapping and a second mapping, and is used for recording snapshot information of the local storage system during storage in a cloud, the first snapshot volume and the second snapshot volume alternately read and write data, the first mapping is a mapping relation between the first snapshot volume and an original volume, and the second mapping is a mapping relation between the second snapshot volume and the original volume; the first snapshot volume and the second snapshot volume are respectively a snapshot version at the latest moment and a snapshot version at the next latest moment; the alternating reading and writing of data by the first snapshot volume and the second snapshot volume comprises:
the primary volume carries out the first snapshot and is a full copy, and each time from the second snapshot to the later is an incremental copy; the mapping of two snapshot volumes corresponding to the original volume is fcmapA and fcmapB, and the mapping is expressed by a bitmap;
at t0, initializing volumes FCA, fcmapA to 0000, fcmapB to 1111, and reading actual data from the volumes FCA, wherein the data at the cloud time t0 is full copy of the original volumes; executing COW when a host IO exists between t0 and t1, wherein the fcapa changes a COW block into 1, and the volume FCA records old COW data; at t1, initializing a volume FCB, wherein fcmapB is 0000, fcmapA is unchanged, data at the cloud time t1 is incremental data from t0 to t1, and the data is read from the volume FCB; at t2, the process alternates back to initialize the volume FCA, the fcmapA is 0000, and the fcmapB is unchanged.
2. The cloud restoration method according to claim 1, wherein the determining, according to the obtained to-be-restored snapshot version information, whether the to-be-restored snapshot version is a previous snapshot version of the current snapshot version includes:
and judging whether the snapshot version to be restored is the previous snapshot version of the current snapshot version or not according to the restoration time of the acquired snapshot version to be restored and the time of the current snapshot version.
3. The cloud restoration method according to claim 1, wherein the determining, according to the obtained to-be-restored snapshot version information, whether the to-be-restored snapshot version is a previous snapshot version of the current snapshot version includes:
and judging whether the snapshot version to be restored is the last snapshot version of the current snapshot version or not according to the acquired restoration version identification number of the snapshot version to be restored and the version identification number of the current snapshot version.
4. A cloud restoration device, comprising:
the judging module is used for judging whether the snapshot version to be restored is the previous snapshot version of the current snapshot version or not according to the acquired snapshot version to be restored information;
the acquisition module is used for acquiring a target snapshot volume and a corresponding mapping relation at a corresponding moment in the local storage system according to the restoration time when the snapshot version to be restored is judged to be the previous snapshot version of the current snapshot version; the target snapshot volume is a first snapshot volume or a second snapshot volume, the local storage system comprises a first snapshot volume, a second snapshot volume, a first mapping and a second mapping, and is used for recording snapshot information when the local storage system stores in a cloud, the first snapshot volume and the second snapshot volume alternately read and write data, the first mapping is a mapping relation between the first snapshot volume and an original volume, and the second mapping is a mapping relation between the second snapshot volume and the original volume; the first snapshot volume and the second snapshot volume are respectively a snapshot version at the latest moment and a snapshot version at the next latest moment; the alternating reading and writing of data by the first snapshot volume and the second snapshot volume comprises:
the primary volume carries out the first snapshot and is a full copy, and each time from the second snapshot to the later is an incremental copy; the mapping of two snapshot volumes corresponding to the original volume is fcmapA and fcmapB, and the mapping is expressed by a bitmap;
at t0, initializing volumes FCA, fcmapA to 0000, fcmapB to 1111, and reading actual data from the volumes FCA, wherein the data at the cloud time t0 is full copy of the original volumes; executing COW when a host IO exists between t0 and t1, wherein the fcapa changes a COW block into 1, and the volume FCA records old COW data; at t1, initializing a volume FCB, wherein fcmapB is 0000, fcmapA is unchanged, data at the cloud time t1 is incremental data from t0 to t1, and the data is read from the volume FCB; t2, alternately returning, initializing the volume FCA, the fcmapA to 0000, and the fcmapB to be unchanged;
and the restoration module is used for acquiring restoration data from the local storage system according to the mapping relation between the target snapshot volume and the target snapshot volume so as to realize restoration of the snapshot version.
5. The cloud restoration device according to claim 4, wherein the determining module is a module that determines whether the snapshot version to be restored is a previous snapshot version of the current snapshot version according to the acquired restoration time of the snapshot version to be restored and the time of the current snapshot version.
6. The cloud restoration device according to claim 4, wherein the determining module is a module that determines whether the snapshot version to be restored is a previous snapshot version of the current snapshot version according to the acquired restoration version identification number of the snapshot version to be restored and the version identification number of the current snapshot version.
CN201710772413.5A 2017-08-31 2017-08-31 Cloud restoration method and device Active CN107526656B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710772413.5A CN107526656B (en) 2017-08-31 2017-08-31 Cloud restoration method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710772413.5A CN107526656B (en) 2017-08-31 2017-08-31 Cloud restoration method and device

Publications (2)

Publication Number Publication Date
CN107526656A CN107526656A (en) 2017-12-29
CN107526656B true CN107526656B (en) 2020-11-20

Family

ID=60683004

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710772413.5A Active CN107526656B (en) 2017-08-31 2017-08-31 Cloud restoration method and device

Country Status (1)

Country Link
CN (1) CN107526656B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109739688B (en) * 2018-12-18 2021-01-26 杭州宏杉科技股份有限公司 Snapshot resource space management method and device and electronic equipment

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030220948A1 (en) * 2002-01-22 2003-11-27 Columbia Data Products, Inc. Managing snapshot/backup collections in finite data storage
US6993539B2 (en) * 2002-03-19 2006-01-31 Network Appliance, Inc. System and method for determining changes in two snapshots and for transmitting changes to destination snapshot
CN1331063C (en) * 2003-06-10 2007-08-08 联想(北京)有限公司 On-line data backup method based on data volume snapshot
US20060106893A1 (en) * 2004-11-02 2006-05-18 Rodger Daniels Incremental backup operations in storage networks
JP4800031B2 (en) * 2005-12-28 2011-10-26 株式会社日立製作所 Storage system and snapshot management method
GB2495079A (en) * 2011-09-23 2013-04-03 Hybrid Logic Ltd Live migration of applications and file systems in a distributed system
CN103019888B (en) * 2012-12-21 2016-03-30 华为技术有限公司 Backup method and device
CN106371763A (en) * 2016-08-23 2017-02-01 浪潮(北京)电子信息产业有限公司 Snapshot storage method and apparatus, disk and computer
CN106909514B (en) * 2017-03-01 2021-04-30 郑州云海信息技术有限公司 Method and device for positioning snapshot disk address

Also Published As

Publication number Publication date
CN107526656A (en) 2017-12-29

Similar Documents

Publication Publication Date Title
US10474537B2 (en) Utilizing an incremental backup in a decremental backup system
CN107544871B (en) Virtual machine disk backup method and device
CN107577558B (en) Cloud storage snapshot method and device
EP3474143B1 (en) Method and apparatus for incremental recovery of data
US10572335B2 (en) Metadata recovery method and apparatus
CN107562578B (en) Snapshot creating method, device, equipment and storage medium for stored data
US20140222761A1 (en) Terminal Backup and Recovery Method
CN104182294A (en) Method and device for backing up and recovering file
US8433864B1 (en) Method and apparatus for providing point-in-time backup images
CN107239411A (en) A kind of Vehicle Controller EMS memory management process and system
CN105302665B (en) A kind of improved Copy on write Snapshot Method and system
CN107526656B (en) Cloud restoration method and device
CN107479823B (en) Data verification method and device in random read-write file test
CN110019086A (en) More copy read methods, equipment and storage medium based on distributed file system
CN111858173A (en) Data recovery method, device, equipment and medium
CN109614054B (en) data reading method and system
CN108604201A (en) A kind of snapshot rollback method, device, storage control and system
CN112148220A (en) Method and device for realizing data processing, computer storage medium and terminal
CN106909514B (en) Method and device for positioning snapshot disk address
CN110795282A (en) Data rollback method, device, equipment and storage medium
EP2820548B1 (en) Versioned memories using a multi-level cell
US11068194B2 (en) Method and system for storing and managing states of a computer
CN109614273B (en) Method and system for reading incremental data
CN111399774B (en) Data processing method and device based on snapshot under distributed storage system
CN110209351B (en) Distributed storage data processing method and device

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
TA01 Transfer of patent application right

Effective date of registration: 20201102

Address after: 215100 No. 1 Guanpu Road, Guoxiang Street, Wuzhong Economic Development Zone, Suzhou City, Jiangsu Province

Applicant after: SUZHOU LANGCHAO INTELLIGENT TECHNOLOGY Co.,Ltd.

Address before: 450018 Henan province Zheng Dong New District of Zhengzhou City Xinyi Road No. 278 16 floor room 1601

Applicant before: ZHENGZHOU YUNHAI INFORMATION TECHNOLOGY Co.,Ltd.

TA01 Transfer of patent application right
GR01 Patent grant
GR01 Patent grant