CN108604201A - A kind of snapshot rollback method, device, storage control and system - Google Patents
A kind of snapshot rollback method, device, storage control and system Download PDFInfo
- Publication number
- CN108604201A CN108604201A CN201680003118.7A CN201680003118A CN108604201A CN 108604201 A CN108604201 A CN 108604201A CN 201680003118 A CN201680003118 A CN 201680003118A CN 108604201 A CN108604201 A CN 108604201A
- Authority
- CN
- China
- Prior art keywords
- snapshot
- version number
- source data
- data
- rollback
- 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.)
- Granted
Links
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
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)
- Retry When Errors Occur (AREA)
Abstract
A kind of snapshot rollback method, device, storage control and system are disclosed, in snapshot rollback method, it includes that the rollback of target snapshot ID is asked that storage control, which is received,；The version number of the source data of the target snapshot is obtained, and obtains the version number for the target snapshot that the target snapshot ID is identified, wherein the target snapshot is the snapshot of the source data；Establish the points relationship of the version number of the source data and the version number of the target snapshot.The quick rollback of snapshot may be implemented using the technology.
Description
The present invention is about field of storage, in particular to snapping technique field.
In recent years, with the continuous development of information science and technology and the extensive use of internet, the data volume of generation is rapidly increased with incredible speed, the progress of business also to data processing technique availability, reliability, in terms of more stringent requirements are proposed.On the one hand, data protection, data backup, data parallel utilize the demand of (such as test, report generation, data are analyzed) to become more and more important；On the other hand, online commerce mode requires system ceaselessly to operate, and shuts down the loss of the pause and commercial opportunity that then mean business.As a result, in order to improve the reliabilities of data, data snapshot technology is come into being.
Using data snapshot technology, the consistency image (i.e. snapshot) at the instant moment of completely available volume data can be obtained in almost moment, and occupies less memory space.Quick data recovery can be carried out when storing equipment and application failure or file corruption occurring, data are restored to the state (i.e. snapshot rollback) at some available time point, to realize online data backup and restore.
It can restore data rapidly in following scene using snapshot:
(1) virus infection.
(2) artificial maloperation.
(3) it maliciously distorts.
(4) corrupted data caused by system failure.
(5) corrupted data caused by application program BUG.
(6) corrupted data caused by storage system BUG.
(7) storage medium damage (snapshot only based on split mirror technology can restore data).
Fig. 1 describes the whole process that data backup and recovery are carried out using snapshot by taking virus infection as an example: (1) each hour periodically generates snapshot to business datum, and when snapshot only additionally saves variance data, therefore data volume is few；(2) after discovery the problem of 5 points of data are infected afternoon, rollback (roll back) is carried out to data using the last snapshot (snapshot of version number 3), data are restored to before being infected, to evade the damage of virus infection bring.
In the example of Fig. 1, it is assumed that current time is 6 pm, then the current version of file system is exactly
The data of 6 pm.If file system is rolled back to 4 points of state in afternoon by host request at this time, that is, rolls back to snapshot 1, concrete operations are that the data of snapshot 1 are copied to current file system, then delete the content of snapshot 1.The process of this rollback is related to a large amount of data duplication, therefore causes largely to consume to system operations resource.
Summary of the invention
In a first aspect, the present invention provides a kind of embodiment of snapshot rollback method, it can be executed by controller, method includes: that storage control receives rollback request, wherein include target snapshot ID in the rollback request；The storage control obtains the version number of the source data of the target snapshot, and obtains the version number for the target snapshot that the target snapshot ID is identified, wherein the target snapshot is the snapshot of the source data；Establish the points relationship of the version number of the source data and the version number of the target snapshot.This points relationship is referred to as " redirecting " relationship.Quick rollback may be implemented using the program, and there is no data to replicate in rollback process, has saved system resource.
In a kind of possible design, data ID is further carried in the rollback request, the version number of the source data for obtaining the target snapshot specifically includes: the version number of the source data of the target snapshot is obtained according to the data ID.Target snapshot can be found using data ID.In some cases, such as source data is file system, and in storage system when only one file system, can not carry data ID.Therefore, it is optional for carrying data ID.
In a kind of possible design, the method also includes: the storage control receives the first read request, and first read request includes first object address；According to the first object address, the requested data of the first read request are obtained from the source data；When in the source data not including the data of the request, obtained from the target snapshot according to points relationship.The program is describeed how according to address reading data.
In a kind of possible design, the method also includes: the storage control receives write request, and the write request includes the data that writing address and needs update；Object block is found according to said write address；According to said write address, the object block is written in the data for needing to update.The program describes how that data are written according to address.
In a kind of possible design, the method also includes: the storage control obtains the version of source data
This number, specifically include: the storage control searches the source data according to the target snapshot ID；The storage control obtains the version number of the source data according to the source data found.
In a kind of possible design, before starting rolling back action, further comprise: the storage control is updated the version number of source data.The update of version number can show that source data is by rolling back action.The operation that the version number updates can also execute after the rollback.
In a kind of possible design, before receiving rollback request, establish: the version number of the source data is directed toward the points relationship of the version number for the snapshot being newly generated；Between multiple snapshots, the version number of each snapshot is directed toward version number's points relationship of the last snapshot generated.What the embodiment of the present invention was established is the points relationship between file system and snapshot and between snapshot.This points relationship is described using version number, is a kind of optional mode.
In a kind of possible design, the source data is file system or logical unit number LUN.
Second aspect, the present invention provide a kind of embodiment of snapshot rollback device.The method that first aspect or each possible design of first aspect can be executed, and possess corresponding technical effect.No further explanation will be given herein.
The third aspect, the present invention provides storage control, including processor and interface, the interface is for receiving rollback request and rollback request being transmitted to processor, the method that the processor executes first aspect or each possible design of first aspect for (such as by running program), and possess corresponding technical effect.No further explanation will be given herein.
Fourth aspect, the present invention provide a kind of snapshot rollback system, including second aspect or each possible design of second aspect snapshot rollback device, further include storage medium, the storage medium is for storing the target snapshot and the file system.Possess second aspect or each possible technical effect designed of second aspect.No further explanation will be given herein.
5th aspect, the present invention provides a kind of snapshot rollback system, including second aspect or each possible design of second aspect snapshot rollback device, further include storage medium, the storage medium is for storing the target snapshot and the file system.Possess second aspect or each possible technical effect designed of second aspect.No further explanation will be given herein.
Fig. 1 is described in the prior art, and the process of data backup and recovery is carried out using snapshot；
Fig. 2 is that the present invention redirects relationship embodiment schematic diagram；
Fig. 3 is another redirection relationship embodiment schematic diagram of the present invention；
Fig. 4 is another redirection relationship embodiment schematic diagram of the present invention；
Fig. 5 is another redirection relationship embodiment schematic diagram of the present invention；
Fig. 6 is the flow chart of the embodiment of invention snapshot rollback method；
Fig. 7 is the example structure topological diagram of invention fast photographing device；
Fig. 8 is the example structure schematic diagram of invention storage control.
Snapping technique is field of storage common technique, and snapshot is data in image sometime, and carrying out protection to data using snapshot can be improved the reliability of data.
The data for being created snapshot are known as source data.There are many types for source data, such as: some or all of storage data etc. in file system, logical unit number (English: Logical Unit Number, LUN), for sake of simplicity, being introduced by taking file system as an example hereinafter.For the write request that storage system receives, if what is carried in write request is new data, can be written into source data；If the data carried in write request compare the content not changed with the data that snapshot records, can be not written into.After creating snapshot, newly-generated snapshot can save the variance data between current source data and a preceding snapshot.By snapshot, the content of the file system of snapshot time can be recovered, is known as rollback using the process that snapshot restores data.
Each snapshot of file system possesses a version number, file system itself Ye Youyige version number.Version number can reflect out the sequencing of snapshot generation.The snapshot and file system of different editions can be distinguished using version number.A kind of common version number's rule is: version number includes numerical value, generates that time more late snapshot, the numerical value in its version number are bigger, and the numerical value of the version number of file system is maximum.In addition, version number is also possible to letter or other symbols, as long as different snapshots can be distinguished all within the protection scope of the present embodiment.The snapshot of file system described in various embodiments of the present invention is all based on for same file system, and in order to describe simplicity, the snapshot of file system is referred to as snapshot hereinafter.Since snapshot is to execute " snapshot operation " to file system to generate, in other words, file system is the data source of snapshot, therefore file system is also referred to as source file system.
In the embodiment of the present invention, the points relationship between file system and the snapshot of different editions is established.The points relationship includes the points relationship between the points relationship between the version number of file system and the version number of snapshot, and the version number of snapshot sometime and the version number of snapshot before.If points relationship be file system be directed toward snapshot, from file system read less than content, can be read from its redirection snapshot.If points relationship is that snapshot is directed toward snapshot, according to points relationship, read from a snapshot less than content, can be read from the snapshot that it is directed toward.In other words, using the points relationship, it can jump in the target snapshot being directed to and obtain to the access request that can not obtain data in the file system.
By being set to point to relationship, file system can be directed toward target snapshot, the access for file system, if not finding requested data in file system, it can transfer to obtain data from target snapshot, to realize the effect for file system being rolled back to target snapshot.After rollback, the content of accessible file system at the time of be rolled-back to.Such as in 11:00, file system rolls back to the 10:00 moment, then it is accessible to 10:00 when file system content.Due to only establishing points relationship, there is no data copy.Therefore, the embodiment of the present invention may be implemented not need data copy to realize snapshot rollback.The data of other snapshots are not influenced by rollback, and are deleted or are modified without snapshot, other snapshots still can be accessed normally.
Before rollback, the present embodiment can establish the points relationship between snapshot and the points relationship between file system and snapshot in advance.Points relationship between snapshot can be determined by the generation time of snapshot.In one embodiment, the generation time of snapshot is determined by the numerical values recited of version number, so, the points relationship includes the snapshot for the smaller version number's representative of numerical value that the snapshot that the lesser version number of numerical value being directed towards by the file system that the biggish version number of numerical value represents represents and the snapshot that the lesser version number of the numerical value represents are directed towards.
A series of continuous points relationships, we term it version number paths.Referring to fig. 2, scheme Zhong Youyige version number path, referred to as version number path 0.In version number path, from big to small according to version number, points relationship is: the file system of version number 3 -- snapshot of > version number 2 -- snapshot of > version number 1.This series of points relationship is described by version number path 0.Wherein version number 3 is the version number of file system, and version number 2 and version number 1 are all the version numbers of snapshot.
If carrying out rolling back action, the points relationship for establishing file system between the snapshot that is rolled back.Also, it can also be updated to the version number of file system, update scheme is, for example, to add 1 to the version number of original file system.Referring to Fig. 3, on the basis of Fig. 2, snapshot 1 is rolled back to current file system, then establishes the points relationship between current version file system and snapshot 1.Also, new version number is assigned to file system.Such as the version number of original file system is 3, to original current version number plus 1, the version number of current file system is updated to 4.
After rolling back action, snapshot 2 is still retained within the storage system.In weight points relationship, snapshot 2 and file system have been directed to snapshot 1.Then 1 Liang Ge version number path of version number path 0 and version number path is formd.
If continuing to create new snapshot, as soon as every creation new snapshot, is updated the version number of file system.Such as 1 is added to the version number of file system；Version number of the version number of file system before update as newly created snapshot.Referring to fig. 4, if on the basis of Fig. 3, snapshot 3 and snapshot 4 are created again.Then one 5 version numbers are co-existed in, wherein 4 version numbers are for marking snapshot；1 version number updates acquisition on the basis of original file system version number, is used for tab file system.
Each rolling back action can generate a file system to the points relationship between snapshot；Therefore, each rolling back action can generate a new version number path.And the version number path formed between existing snapshot remains unchanged.Referring to Fig. 5, according to above-mentioned rule and so on, when file system is rolled back to snapshot 3.A version number path is then generated again, and in newly-generated version number path, file system is directed toward snapshot 3.The points relationship between the snapshot in version number path 0 and version number path 1 originally remains unchanged.Therefore, one 3 version number paths: version number path 0 (snapshot 2-- > snapshot 1), version number path 1 (snapshot 5-- > snapshot 4), version number path 2 (file system -- > snapshot 4) are shared.
It is the topological diagram of storage system embodiment of the present invention referring to Fig. 6.Storage control 11 and hard disk 12 connect, and collectively constitute storage system, provide data storage service for host 13.Storage control 11 is managed hard disk 12, and provides memory interface for host 13.Hard disk 12 provides memory space, can be used for storing snapshot and file system, in other embodiments, hard disk 12 can be other storage mediums, such as solid state hard disk etc..
Controller 11 and hard disk 12 are two mutually independent equipment in Fig. 6.In other embodiments,
It also can integrate hard disk inside storage control 11, to form a complete storage system by storage control 11.In other words, storage medium be arranged in storage control either internally or externally can, as long as being capable of providing memory space.
Each step of the flow chart of snapshot rollback method embodiment of the present invention, this method can be executed by controller.Specifically, including the following steps.
21, controller establishes the points relationship between snapshot and the points relationship between file system and snapshot.
Points relationship between snapshot can be determined that each snapshot is directed toward the snapshot of previous generation by the chronological order of generation snapshot.It is understood that the snapshot generated earliest is not directed to other snapshots.File system is directed toward the snapshot generated the latest.Form the structure of a chain type.The snapshot being pointed to is directed to his file system/snapshot next stage snapshot.
Points relationship describes the acquisition direction of content in file system.According to points relationship, read from file system/snapshot less than content, can attempt to obtain in the snapshot being directed toward from it；If still read less than, it tries obtained from next stage snapshot again；Reading of content is needed until getting.The content for needing to read, which can be, to be read with block (block) for unit.
Above-mentioned points relationship can be described by version number.Its specific practice is: establishing the points relationship between the points relationship between the version number of snapshot and file system version number and snapshot version number.
This step 21 is a default step, is executed before rolling back action.Therefore, for rollback process, the step is not required.
22, the rollback that storage control receiving host issues is requested, and the data ID and target snapshot ID of file system are carried in the rollback request.Rollback request generates the data at moment for requesting file system to roll back to snapshot version representated by target snapshot ID.
Data ID is used for unique identification source data, such as when the source data is LUN, data ID is then LUN ID；Alternatively, the data ID is the ID of the file system when source data is file system, for file system described in unique identification.Possess different snapshot ID by multiple snapshots that same file system generates, however these snapshots and the file system share the same data ID.Therefore, both data ID and snapshot ID, which are combined, can navigate to a unique snapshot.
Data ID is optionally that in some cases, such as in system when only one file system, file system and the snapshot of this file system can be found by not needing data ID.The corresponding snapshot ID of each snapshot.Target snapshot ID is the ID for needing the snapshot being rolled-back to.
In other embodiments, rollback request may not be host sending, such as by generating inside storage control.
23, the storage control obtains the version number of file system, and obtains the version number of target snapshot corresponding to the target snapshot ID.
By the data ID, the version number of file system and file system can be obtained.By the data ID, the version number of the snapshot of each version and the snapshot of each version can also be obtained.
By target snapshot ID, the version number of target snapshot corresponding to target snapshot ID can be obtained.
The acquisition of the two version numbers in time sequencing in no particular order.It can obtain, can also first be obtained with any one simultaneously, acquisition after another.
24, the storage control is updated the version number of file system.
The version number of file system and the version number of snapshot may each be number.A kind of update method is to add 1 to the version number of current version object, the version number as new current version object.
To one of the effect that version number updates, it can show that file system is by rolling back action.
In other embodiments, can not also more new version number, keep file system original version number it is constant.In other words, this step is optional.
25, the storage control starts rolling back action, and the rolling back action includes: to establish the points relationship that the target snapshot is directed toward from the file system.
This points relationship can be described with the points relationship between the version number of the file system and the version number of target snapshot.
In addition, the points relationship that file system is directed toward other snapshots can be cancelled.
Above-mentioned steps 22-25 is rollback process, and step 26 below is introduced after above-mentioned rolling back action.How data in file system are read.
26, the first read request that the storage control receiving host is sent carries data ID and the first object address of file system in first read request.First read request reads the file system for requesting
First object data in system.The storage control obtains first object data, returns to the host according to points relationship.
First object address can be logical block address (logic block address, LBA) and data length is described jointly.Wherein logical block address describes initial position of the first object data in storage equipment, and data length describes the size of first object data.
In addition, first object address can also be described jointly by first address and end address.Storage control obtains the ID (the e.g. address of block) of the block where first object data according to first object address.The read-write of content is carried out using block as granularity.The first object data in one block, or in continuous multiple pieces.File system is found using file system ID, searches the block for needing to read from the file system using described piece of ID.
After having started rolling back action, if there is new data are written, the file system by rolling back action can be written into.Therefore, block is searched from the file system first.
For any one block, first searched from from the file system；If not finding this block in file system, successively searched from next stage snapshot according to points relationship；If still do not found, searched from next stage snapshot again, until obtaining the block position for needing to read.First object data are obtained from the block found and return to host.
It should be noted that for the block in storage valid data, will record the LBA of block, LBA can be stored to be read for controller in memory in storage file system or when shining in storage medium fastly.Such as LBA is recorded in a manner of the LBA of record block in the controller and physical address (PBA) mapping relations.Therefore, when reading the data in block, whether according to the LBA for carrying block in read request, can find in file system or some snapshot has corresponding piece.
Optionally, if in the access request to file system content, file system ID is not carried, defaults to the access to file system.
As previously mentioned, points relationship describes the acquisition direction of content in file system.Therefore it can attempt to obtain requested piece step by step according to points relationship described in points relationship, since file system.We are described by taking one of block as an example, this block is named as first object block.Then: if obtaining the first object block from file system, being directly returned to host；If there is no in file system described
First object block, the snapshot being directed toward from file system, which is looked for, searches the first object block, and the host is returned to if finding；Otherwise, the object block is searched from snapshot pointed by the snapshot that file system is directed toward, be returned to if found to the host；Otherwise, it continues to attempt to obtain the object block in next stage snapshot again；It recycles according to this, until finding the object block.The first object block is read, the content that first object data are belonged in first object block is returned to host.Described piece be snapshot and file system component units.
Step 26 can be executed in any time after step 21, as long as there are the points relationships between file system and any snapshot in storage system.
In one embodiment, step 26 can execute after step 25.In this case, storage control obtains the requested data of the first read request according to the first object address from the source data, fails the part obtained from the source data, obtains from the target snapshot according to points relationship.For the part for failing to obtain in target snapshot, obtained from the snapshot that the target snapshot is directed toward according to points relationship.It according to snapshot points relationship, searches step by step according to this, until obtaining the requested all data in first object address.
In step 26, describe how storage control handles the read request that host issues.For the write request that host issues, the processing mode of storage control is similar with step 26, such as file system ID and the writing address for data to be written are carried in write request.Difference is only that: additionally being carried in write request and is needed to update the system data for arriving file system.Storage control carries the position that writing address finds object block in file system using write request, and object block then is written in object content.
27, the second read request that the storage control receiving host is sent carries snapshot ID and the second destination address in second read request.The storage control obtains the second target data, returns to the host according to points relationship.
It, can any time execution after step 21 based on points relationship of the step 27 between the snapshot that step 21 is established.The difference is that, it is the data of file system that the first read request in step 26, which requests the first object data read, with step 26, and in step 27, what the second read request requested the second target data read is the data in snapshot.
Controller obtains ID (the e.g. block of block where the second target data according to first object address
Address).Second target data can also may be distributed in multiple pieces in one block.The snapshot of snapshot ID representative is found using snapshot ID.The block that second target data is related to is named as second piece, and reading process is similar with step 26: the second object block is searched from the snapshot using described piece of ID；If do not found, second object block is successively searched from next stage snapshot according to points relationship；Until obtaining second object block.The part for belonging to the second target data in second object block is returned to host.
Since detailed process is similar with step 26, the target only read becomes snapshot from file system, therefore can refer to step 26, and and will not be described here in detail.
Step 27 describes how to read snapshot data, can be individually performed, and can also execute, can also be executed during executing step 22-26 after step 26.
Referring to Fig. 8, the present invention also provides a kind of embodiments of snapshot rollback device, can apply above-mentioned snapshot rollback method.Snapshot rollback device 3 include: receiving module 31, version number processing touch 32, roll-back module 33 and read module 34.Snapshot rollback device can be hardware, e.g. storage control.It is also possible to software, such as operates in the program in storage control, can also be the combination of software and hardware.Since snapshot rollback method embodiment corresponding with snapshot rollback Installation practice has done more detailed introduction, the function of its each module is only briefly described below.
Receiving module 31 includes target snapshot ID in the rollback request for receiving rollback request.Version number's processing module 32 and receiving module 31 communicate, the version number of the source data for obtaining the target snapshot, and obtain the version number of target snapshot corresponding to the target snapshot ID, wherein the target snapshot is the snapshot of the source data.Roll-back module 33 and version number's processing module 32 communication, the version number for establishing the source data are directed toward the points relationship of the version number of the target snapshot.The source data is file system or logical unit number LUN.
Optionally, data ID is further carried in the rollback request, the version number for the source data that version number's processing module obtains the target snapshot specifically includes: version number's processing module obtains the version number of the source data of the target snapshot according to the data ID.
Optionally, the present invention also provides the embodiments of degree evidence: the receiving module, is also used to receive the first read request, and first read request includes first object address；The rollback device further includes read module 34, for obtaining the requested data of the first read request from the source data according to the first object address,
Fail the part obtained from the source data, is obtained from the target snapshot according to points relationship.
Optionally, version number's processing module obtains the version number of source data specifically: version number's processing module searches the source data according to the target snapshot ID；Version number's processing module obtains the version number of the source data according to the source data found.In other embodiments, there can also be other schemes to obtain the version number of source data, such as directly carry the version number of source data in rollback request.
The version number of the source data and the points relationship of the version number of the target snapshot are: to the access request that can not obtain data in the file system, jumping to from the target snapshot being directed to and obtain.
Optional version number's processing module is also used to: before starting rolling back action, being updated to the version number of source data.Such as 1 is added to the version number of source data, as new source data version number.
Version number's processing module, is also used to: points relationship is established in the rollback device initialization, the points relationship includes: the points relationship that the version number of the source data is directed toward the version number for the snapshot being newly generated；And between multiple snapshots, the version number of each snapshot is directed toward the points relationship of the version number of the last snapshot generated.
Claims (18)
- A kind of snapshot rollback method characterized by comprisingStorage control receives rollback request, includes target snapshot ID in the rollback request；The storage control obtains the version number of the source data of the target snapshot, and obtains the version number for the target snapshot that the target snapshot ID is identified, wherein the target snapshot is the snapshot of the source data；The storage control establishes the points relationship of the version number of the source data and the version number of the target snapshot.
- The method according to claim 1, wherein further carrying data ID in the rollback request, the version number of the source data for obtaining the target snapshot is specifically included:The version number of the source data of the target snapshot is obtained according to the data ID.
- The method according to claim 1, wherein wherein, the method also includes:The storage control receives the first read request, and first read request includes first object address；According to the first object address, the requested data of the first read request are obtained from the source data；When in the source data not including the data of the request, obtained from the target snapshot according to points relationship.
- The method according to claim 1, wherein wherein, the method also includes:The storage control receives write request, and the write request includes the data that writing address and needs update；Object block is found according to said write address；According to said write address, the object block is written in the data for needing to update.
- The method according to claim 1, wherein the storage control obtains the version number of source data, specifically include:The storage control searches the source data according to the target snapshot ID；The storage control obtains the version number of the source data according to the source data found.
- The method according to claim 1, wherein further comprising before starting rolling back action:The storage control is updated the version number of source data.
- The method according to claim 1, wherein before the method, further includes:Points relationship is established, the points relationship includes:The version number of the source data is directed toward the points relationship of the version number for the snapshot being newly generated；AndBetween multiple snapshots, the version number of each snapshot is directed toward version number's points relationship of the last snapshot generated.
- Method according to any one of claims 1-7, it is characterised in that:The source data is file system or logical unit number LUN.
- A kind of snapshot rollback device characterized by comprisingReceiving module includes target snapshot ID in the rollback request for receiving rollback request；Version number's processing module, the version number of the source data for obtaining the target snapshot, and obtain the version number of target snapshot corresponding to the target snapshot ID, wherein the target snapshot is the snapshot of the source data；Roll-back module is directed toward the points relationship of the version number of the target snapshot for the version number for establishing the source data.
- Snapshot rollback device according to claim 9, which is characterized in that further carry data ID in the rollback request, the version number for the source data that version number's processing module obtains the target snapshot specifically includes:Version number's processing module obtains the version number of the source data of the target snapshot according to the data ID.
- Snapshot rollback device according to claim 9, which is characterized in that wherein:The receiving module, is also used to receive the first read request, and first read request includes first object address；The rollback device further includes read module, for according to the first object address, from described The requested data of the first read request are obtained in source data, are failed the part obtained from the source data, are obtained from the target snapshot according to points relationship.
- Snapshot rollback device according to claim 9, which is characterized in that version number's processing module obtains the version number of source data, specifically includes:Version number's processing module searches the source data according to the target snapshot ID；Version number's processing module obtains the version number of the source data according to the source data found.
- Snapshot rollback device according to claim 9, wherein version number's processing module is also used to:Before starting rolling back action, the version number of source data is updated.
- Snapshot rollback device according to claim 9, which is characterized in that version number's processing module is also used to:Points relationship is established in the rollback device initialization, the points relationship includes:The version number of the source data is directed toward the points relationship of the version number for the snapshot being newly generated；AndBetween multiple snapshots, the version number of each snapshot is directed toward the points relationship of the version number of the last snapshot generated.
- The snapshot rollback device according to any one of claim 9-14, it is characterised in that:The source data is file system or logical unit number LUN.
- A kind of storage system further includes storage medium, for storing the target snapshot and the file system including any snapshot rollback device of claim 9-14.
- A kind of storage control, including processor and interface, the interface is for receiving rollback request and rollback request being transmitted to processor, and the processor is for executing operation below:Rollback request is received, includes target snapshot ID in the rollback request；Obtain the version number of the source data of the target snapshot, and the version number according to the target snapshot ID carried in rollback request the target snapshot identified, wherein the target snapshot is the snapshot of the source data；Establish the source data version number be directed toward the target snapshot version number points relationship.
- A kind of storage system further includes storage medium, for storing the target snapshot and the file system including the snapshot rollback device described in claim 17.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2016/113421 WO2018119998A1 (en) | 2016-12-30 | 2016-12-30 | Snapshot rollback method, apparatus, storage controller, and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108604201A true CN108604201A (en) | 2018-09-28 |
| CN108604201B CN108604201B (en) | 2022-02-25 |
Family
ID=62706584
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201680003118.7A Active CN108604201B (en) | 2016-12-30 | 2016-12-30 | Snapshot rollback method, device, storage controller and system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN108604201B (en) |
| WO (1) | WO2018119998A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110515543A (en) * | 2019-08-02 | 2019-11-29 | 星辰天合（北京）数据科技有限公司 | Object bucket-based snapshot method, device and system |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109408294A (en) * | 2018-11-13 | 2019-03-01 | 郑州云海信息技术有限公司 | A kind of snapshot rollback method, device, equipment and storage medium |
| CN111552437B (en) * | 2020-04-22 | 2024-03-15 | 上海天玑科技股份有限公司 | Snapshot method and snapshot device applied to distributed storage system |
| CN111625262B (en) * | 2020-05-28 | 2023-08-22 | 广东浪潮大数据研究有限公司 | Rollback method, system, equipment and storage medium of workload resource |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102023863A (en) * | 2010-12-13 | 2011-04-20 | 中兴通讯股份有限公司 | Method and device for switching editions |
| CN104407935A (en) * | 2014-11-07 | 2015-03-11 | 华为数字技术（成都）有限公司 | Snapshot rollback method and storage equipment |
| CN105095016A (en) * | 2014-05-16 | 2015-11-25 | 北京云巢动脉科技有限公司 | Disk snapshot roll-back method and device |
| CN105528464A (en) * | 2016-01-28 | 2016-04-27 | 北京宇航系统工程研究所 | Version management system capable of automatically judging technical condition consistency of associated data |
| WO2016101283A1 (en) * | 2014-12-27 | 2016-06-30 | 华为技术有限公司 | Data processing method, apparatus and system |
| CN105808449A (en) * | 2014-12-31 | 2016-07-27 | 中国电信股份有限公司 | Virtual storage image version management method and system for virtual machine |
| US20160239392A1 (en) * | 2015-02-16 | 2016-08-18 | International Business Machines Corporation | Preserving management services with distributed metadata through the disaster recovery life cycle |
| CN105938457A (en) * | 2016-03-31 | 2016-09-14 | 华为技术有限公司 | Data filtering method, and device and data reading system |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060143412A1 (en) * | 2004-12-28 | 2006-06-29 | Philippe Armangau | Snapshot copy facility maintaining read performance and write performance |
| CN102012853B (en) * | 2011-01-14 | 2012-05-23 | 南开大学 | Zero-copy snapshot method |
| CN104268036A (en) * | 2014-10-13 | 2015-01-07 | 浪潮电子信息产业股份有限公司 | Snapshot volume reading method based on zero copy |
-
2016
- 2016-12-30 WO PCT/CN2016/113421 patent/WO2018119998A1/en active Application Filing
- 2016-12-30 CN CN201680003118.7A patent/CN108604201B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102023863A (en) * | 2010-12-13 | 2011-04-20 | 中兴通讯股份有限公司 | Method and device for switching editions |
| CN105095016A (en) * | 2014-05-16 | 2015-11-25 | 北京云巢动脉科技有限公司 | Disk snapshot roll-back method and device |
| CN104407935A (en) * | 2014-11-07 | 2015-03-11 | 华为数字技术（成都）有限公司 | Snapshot rollback method and storage equipment |
| WO2016101283A1 (en) * | 2014-12-27 | 2016-06-30 | 华为技术有限公司 | Data processing method, apparatus and system |
| CN105808449A (en) * | 2014-12-31 | 2016-07-27 | 中国电信股份有限公司 | Virtual storage image version management method and system for virtual machine |
| US20160239392A1 (en) * | 2015-02-16 | 2016-08-18 | International Business Machines Corporation | Preserving management services with distributed metadata through the disaster recovery life cycle |
| CN105528464A (en) * | 2016-01-28 | 2016-04-27 | 北京宇航系统工程研究所 | Version management system capable of automatically judging technical condition consistency of associated data |
| CN105938457A (en) * | 2016-03-31 | 2016-09-14 | 华为技术有限公司 | Data filtering method, and device and data reading system |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110515543A (en) * | 2019-08-02 | 2019-11-29 | 星辰天合（北京）数据科技有限公司 | Object bucket-based snapshot method, device and system |
| CN110515543B (en) * | 2019-08-02 | 2021-02-19 | 星辰天合（北京）数据科技有限公司 | Object bucket-based snapshot method, device and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108604201B (en) | 2022-02-25 |
| WO2018119998A1 (en) | 2018-07-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9804934B1 (en) | Production recovery using a point in time snapshot | |
| US9053075B2 (en) | Storage control device and method for controlling storages | |
| US9600553B1 (en) | Distributed replication in cluster environments | |
| US8627012B1 (en) | System and method for improving cache performance | |
| US8930947B1 (en) | System and method for live migration of a virtual machine with dedicated cache | |
| US8738883B2 (en) | Snapshot creation from block lists | |
| US8473462B1 (en) | Change tracking for shared disks | |
| US8700570B1 (en) | Online storage migration of replicated storage arrays | |
| US9354907B1 (en) | Optimized restore of virtual machine and virtual disk data | |
| US20150213100A1 (en) | Data synchronization method and system | |
| JP4419884B2 (en) | Data replication apparatus, method, program, and storage system | |
| US9483367B1 (en) | Data recovery in distributed storage environments | |
| US10120595B2 (en) | Optimizing backup of whitelisted files | |
| CN107329704B (en) | Cache mirroring method and controller | |
| US8745342B2 (en) | Computer system for controlling backups using wide area network | |
| CN108604201A (en) | A kind of snapshot rollback method, device, storage control and system | |
| JP2012507788A (en) | Method and system for recovering a computer system using a storage area network | |
| JP6133396B2 (en) | Computer system, server, and data management method | |
| WO2018076633A1 (en) | Remote data replication method, storage device and storage system | |
| US20160283148A1 (en) | Backup control device, backup control method, and recording medium | |
| US10078558B2 (en) | Database system control method and database system | |
| US9075809B1 (en) | Methods and systems for application cluster virtual nodes | |
| US9053033B1 (en) | System and method for cache content sharing | |
| US10366076B1 (en) | Systems and methods for repairing corrupted data segments in deduplicated data systems | |
| US8046630B2 (en) | Storage control apparatus, storage control method, and computer product |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |