Creating consistent user snaps at destination during replication

• US 9,983,942 B1
• Filed: 03/11/2015
• Issued: 05/29/2018
• Est. Priority Date: 03/11/2015
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Inventors: Seela, Nagapraveen V., Brundage, Michael C., Xu, Yan
• Primary Examiner(s): Chan, Tracy
• Application Number:
  US14/644,475
• Time in Patent Office: 1,175 Days
• Field of Search: None
• CPC Class Codes: G06F 11/2058 using more than 2 mirrored copies
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 2201/82 Solving problems relating to consistency ensuring consistency in mirrored systems G06F11/2064
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data

Abstract

A technique for providing access to a data object serving as a target of snapshot-shipping replication includes taking a system snap of the data object after completion of each of multiple snapshot-shipping updates. In response to receiving a request to take a user snap of the data object, a data storage system redirects the request to a previously generated system snap, so that the data storage system takes the user snap of the system snap rather than taking the user snap of the data object itself.

Claims

1. A method for generating snaps in a data storage system, the method comprising:

performing, at a destination data storage system, multiple snapshot-shipping updates to a data object, each snapshot-shipping update applying a set of changes to the data object to bring the data object into a state that is content-consistent with that of a source object operated from a source data storage system, the snapshot-shipping updates performed at respective times to keep the data object substantially current with the source object as the source object changes over time;

after performing each snapshot-shipping update to the data object and before performing another one, generating a system snap of the data object, each system snap providing a point-in-time version of the data object that reflects a state of the data object after completion of the respective snapshot-shipping update;

upon receiving a request to generate a user snap of the data object, generating the user snap of the data object as a snap of a previously generated system snap;

receiving a second request to generate a second user snap of the data object; and

in response to the destination data storage system not being in a process of performing any of the snapshot-shipping updates when the second request is received, generating the second user snap as a snap of the data object,

wherein generating the user snap as the snap of the previously generated system snap is performed in response to the destination data storage system being in the process of performing one of the snapshot-shipping updates when the request to generate the user snap is received, and

wherein the method further comprises;

providing a snap target indicator in the destination data storage system, the snap target indicator identifying a current source to be used for taking user snaps in the destination data storage system;

setting the snap target indicator to a first value while each of a set of snapshot-shipping operations is taking place; and

setting the snap target indicator to a second value during periods between consecutive ones of the set of snapshot-shipping operations, the first value identifying a system snap as the source for taking user snaps, the second value identifying the data object as the source for taking user snaps; and

in response to requests to generate user snaps of the data object, (i) checking the snap target indicator and (ii) generating snaps of the source identified by the snap target indicator.

2. The method of claim 1, wherein the data object is realized in a base file stored in a file system of the destination data storage system, wherein each system snap is a snap of the base file and each system snap is itself a file in the file system, and wherein the user snap and the second user snap are each files in the file system.

3. The method of claim 2, further comprising, after taking each system snap of the data object, destroying any previously-taken system snap of the data object from the file system.

4. The method of claim 2, further comprising:

storing, by the destination data storage system, the snap target indicator to identify a file to be snapped in response to receiving requests to generate snaps of the data object,

wherein generating the user snap includes interrogating the snap target indicator and identifying, from the snap target indicator, the file to be snapped as a system snap file, and

wherein generating the second user snap includes interrogating the snap target indicator and identifying, from the snap target indicator, the file to be snapped as the base file.

5. The method of claim 4, wherein each snapshot-shipping update has a beginning and an end, and wherein the method further comprises:

detecting the beginning of a snapshot-shipping update on the base file; and

in response to detecting the beginning of the snapshot-shipping update on the base file, setting the snap target indicator to identify a system snap file as the file to be snapped.

6. The method of claim 5, wherein the method further comprises:

detecting the end of a snapshot-shipping update on the base file; and

in response to detecting the end of the snapshot-shipping update on the base file, setting the snap target indicator to identify the base file as the file to be snapped.

7. The method of claim 6, wherein the base file provides a file-based realization of one of (i) a LUN, (ii) a file system, or (iii) a VVol (Virtual Volume).

8. The method of claim 1, wherein the destination data storage system includes an updater running within a storage processor of the destination data storage system, and wherein the method further comprises:

the updater detecting a beginning of processing a snapshot-shipping update received from the source data storage system;

in response to the updater detecting the beginning of processing the snapshot-shipping update, setting, by the updater, the snap target indicator to identify a system snap as a target of user snap requests, such that a request for a user snap arriving when the snap target indicator identifies the system snap causes the storage processor to generate the user snap from the system snap; and

in response to the updater detecting an end of processing the snapshot-shipping update, setting, by the updater, the snap target indicator to identify the data object as the target of user snap requests, such that a request for a user snap arriving when the snap target indicator identifies the data object causes the storage processor to generate the user snap from the data object.

9. A data storage system, comprising control circuitry that includes a set of processing units coupled to memory, the control circuitry constructed and arranged to:

perform, at a destination data storage system, multiple snapshot-shipping updates to a data object, each snapshot-shipping update applying a set of changes to the data object to bring the data object into a state that is content-consistent with that of a source object operated from a source data storage system, the snapshot-shipping updates performed at respective times to keep the data object substantially current with the source object as the source object changes over time;

after performing each snapshot-shipping update to the data object and before performing another one, generate a system snap of the data object, each system snap providing a point-in-time version of the data object that reflects a state of the data object after completion of the respective snapshot-shipping update;

upon receiving a request to generate a user snap of the data object, generate the user snap of the data object as a snap of a previously generated system snap;

receive a second request to generate a second user snap of the data object; and

in response to the destination data storage system not being in a process of performing any of the snapshot-shipping updates when the second request is received, generate the second user snap as a snap of the data object,

wherein the control circuitry is constructed and arranged to generate the user snap as the snap of the previously generated system snap in response to the destination data storage system being in the process of performing one of the snapshot-shipping updates when the request to generate the user snap is received, and

wherein the control circuitry is further constructed and arranged to;

provide a snap target indicator in the destination data storage system, the snap target indicator identifying a current source to be used for taking user snaps in the destination data storage system;

set the snap target to a first value while each of a set of snapshot-shipping operations is taking place; and

set the snap target to a second value during periods between consecutive ones of the set of snapshot-shipping operations, the first value identifying a system snap as the source for taking user snaps, the second value identifying the data object as the source for taking user snaps; and

in response to requests to generate user snaps of the data object, (i) check the snap target and (ii) generate snaps of the source identified by the snap target.

10. The data storage system of claim 9,

wherein the memory is constructed and arranged to (i) store the file system including multiple files, (ii) realize the data object and snaps thereof in respective files of the file system, and (iii) store the snap target indicator to identify a file in the file system to be snapped in response to receiving requests to generate snaps of the data object,

wherein each snapshot-shipping update has a beginning and an end and wherein the control circuitry is further constructed and arranged to:

detect the beginning of each snapshot-shipping update on the base file;

in response to detecting the beginning of each snapshot-shipping update on the base file, set the snap target indicator to identify a system snap file as the file to be snapped;

detect the end of each snapshot-shipping update on the base file;

in response to detecting the end of each snapshot-shipping update on the base file, set the snap target indicator to identify the base file as the file to be snapped; and

in response to receiving each of multiple requests to generate a snap of the data object, (a) interrogate the snap target indicator, (b) identify, from the snap target indicator, the file to be snapped and (c) take a snap of the file identified in the snap target indicator.

11. The data storage system of claim 10, wherein the base file provides a file-based realization of one of (i) a LUN, (ii) a file system, or (iii) a VVol (Virtual Volume).

12. A computer-program product including a set of non-transitory, computer-readable media including instructions which, when executed by a set of processing units of a destination data storage system, cause the set of processing units to perform a method for generating snaps, the method comprising:

performing, at a destination data storage system, multiple snapshot-shipping updates to a data object, each snapshot-shipping update applying a set of changes to the data object to bring the data object into a state that is content-consistent with that of a source object operated from a source data storage system, the snapshot-shipping updates performed at respective times to keep the data object substantially current with the source object as the source object changes over time;

after performing each snapshot-shipping update to the data object and before performing another one, generating a system snap of the data object, each system snap providing a point-in-time version of the data object that reflects a state of the data object after completion of the respective snapshot-shipping update; and

upon receiving a request to generate a user snap of the data object, generating the user snap of the data object as a snap of a previously generated system snap;

receiving a second request to generate a second user snap of the data object; and

in response to the destination data storage system not being in a process of performing any of the snapshot-shipping updates when the second request is received, generating the second user snap as a snap of the data object,

wherein generating the user snap as the snap of the previously generated system snap is performed in response to the destination data storage system being in the process of performing one of the snapshot-shipping updates when the request to generate the user snap is received, and

wherein the method further comprises;

providing a snap target indicator in the destination data storage system, the snap target indicator identifying a current source to be used for taking user snaps in the destination data storage system;

setting the snap target to a first value while each of a set of snapshot-shipping operations is taking place; and

setting the snap target to a second value during periods between consecutive ones of the set of snapshot-shipping operations, the first value identifying a system snap as the source for taking user snaps, the second value identifying the data object as the source for taking user snaps; and

in response to requests to generate user snaps of the data object, (i) checking the snap target and (ii) generating snaps of the source identified by the snap target.

13. The computer program product of claim 12, wherein the data object is realized in a base file stored in a file system of the destination data storage system, wherein each system snap is a snap of the base file and each system snap is itself a file in the file system, and wherein the user snap and the second user snap are each files in the file system.

14. The computer program product of claim 13, wherein the method further comprises, after taking each system snap of the data object, destroying any previously-taken system snap of the data object from the file system.

15. The computer program product of claim 13, wherein the method further comprises:

storing, by the destination data storage system, the snap target indicator to identify a file to be snapped in response to receiving requests to generate snaps of the data object,

wherein generating the user snap includes interrogating the snap target indicator and identifying, from the snap target indicator, the file to be snapped as a system snap file;

wherein generating the second user snap includes interrogating the snap target indicator and identifying, from the snap target indicator, the file to be snapped as the base file.

16. The computer program product of claim 15, wherein each snapshot-shipping update has a beginning and an end, and wherein the method further comprises:

detecting the beginning of each snapshot-shipping update on the base file;

in response to detecting the beginning of each snapshot-shipping update on the base file, setting the snap target indicator to identify a system snap file as the file to be snapped;

detecting the end of each snapshot-shipping update on the base file;

in response to detecting the end of each snapshot-shipping update on the base file, setting the snap target indicator to identify the base file as the file to be snapped; and

in response to receiving each of multiple requests to generate a snap of the data object, (a) interrogating the snap target indicator, (b) identifying, from the snap target indicator, the file to be snapped and (c) taking a snap of the file identified in the snap target indicator.

17. The computer program produce of claim 16, wherein the base file provides a file-based realization of one of (i) a LUN, (ii) a file system, or (iii) a VVol (Virtual Volume).