Extensive recovery point management using tags
A technique enables coordination of unrelated software components to facilitate extensive recovery point management on a snapshot or recovery point through the use of a flexible tag structure. The tag is organized and arranged as a {key=value,[value] . . . } structure wherein the key denotes an operation that requires coordination between the unrelated software components and the value(s) denote multi-cardinality that provide parameters for coordination of the operation. The multi-cardinality aspect of the flexible tag structure provides a set of values associated with the key of the tag that enables a software component and/or protocol to insert its value(s) into the tag structure for its interpretation. The technique thus provides an extensible model where multiple components/protocols use the tag to coordinate operations on the RP by conveying certain meaning/interpretations of the tag and its values.
1. A method comprising:
generating a snapshot of a workload at a primary site of a multi-site environment in accordance with a recovery point objective (RPO);
associating a tag structure with the generated snapshot, the tag structure configured to coordinate one or more operations between a first software component operating on the snapshot and a second software component operating on the snapshot, wherein the first and second software components are distinct;
replicating the snapshot and tag structure as a recovery point to a secondary site of the environment; and
controlling an operation of the first software component directed to the snapshot using the tag structure while maintaining the RPO.
2. The method of claim 1 wherein the first software component includes garbage collection and wherein the second software component includes snapshot generation.
3. The method of claim 1 wherein the operation of the first software component is garbage collection of unneeded data from the snapshot.
4. The method of claim 1 further comprising:
organizing the tag structure as a key-value structure, wherein the key indicates the operation that requires coordination between the distinct software components and the value indicates multi-cardinality that provides parameters for coordination of the operation among the software components.
5. The method of claim 1 wherein the tag structure includes a tag used as a lock identifying the software component holding the lock.
6. The method of claim 5 wherein the tag structure includes an additional tag indicating an expiry time for the tag used as the lock, and wherein the tag and additional tag are associated with a same key.
7. The method of claim 1 wherein the tag structure is a system defined tag that is used for client/server coordination among the software components and wherein one of the first software component or second software component is a server application configured to take an action based on a value specified in the tag.
8. The method of claim 7 wherein the system defined tag has a key and format of the value defined by the server application.
9. The method of claim 1 wherein the tag structure is a user defined tag for client/client coordination among client applications configured to use a recovery point for the RPO and wherein one of the first software component or second software component is a client application.
10. The method of claim 9 wherein the user defined tag has a key and format of a value defined by the client application and unusable to a server application.
11. A non-transitory computer readable medium including program instructions for execution on a processor, the program instructions configured to:
generate a snapshot of a workload at a primary site of a multi-site environment in accordance with a recovery point objective (RPO);
associate a tag structure with the generated snapshot, the tag structure configured to coordinate one or more operations between a first software component operating on the snapshot and a second software component operating on the snapshot, wherein the first and second software components are distinct;
replicate the snapshot and tag structure as a recovery point to a secondary site of the environment; and
control an operation of the first software component directed to the snapshot using the tag structure while maintaining the RPO.
12. The non-transitory computer readable medium of claim 11 wherein the first software component includes garbage collection and wherein the second software component includes snapshot generation.
13. The non-transitory computer readable medium of claim 11 wherein the operation of the first software component is garbage collection of unneeded data from the snapshot.
14. The non-transitory computer readable medium of claim 11 wherein the program instructions are further configured to:
organize the tag structure as a key-value structure, wherein the key indicates the operation that requires coordination between the distinct software components and the value indicates multi-cardinality that provides parameters for coordination of the operation among the software components.
15. The non-transitory computer readable medium of claim 11 wherein the tag structure includes a tag used as a lock identifying the software component holding the lock.
16. The non-transitory computer readable medium of claim 15 wherein the tag structure includes an additional tag indicating an expiry time for the tag used as the lock, and wherein the tag and additional tag are associated with a same key.
17. The non-transitory computer readable medium of claim 11 wherein the tag structure is a system defined tag that is used for client/server coordination among the software components and wherein one of the first software component or second software component is a server application configured to take an action based on a value specified in the tag.
18. The non-transitory computer readable medium of claim 17 wherein the system defined tag has a key and format of the value defined by the server application.
19. The non-transitory computer readable medium of claim 11 wherein the tag structure is a user defined tag for client/client coordination among client applications configured to use a recovery point for the RPO and wherein one of the first software component or second software component is a client application.
20. The non-transitory computer readable medium of claim 19 wherein the user defined tag has a key and format of a value defined by the client application and unusable to a server application.
21. An apparatus comprising:
a network connecting a node of a primary site to a secondary site of a multi-site environment, the node having a processor configured to execute program instructions configured to:
generate a snapshot of a workload at the primary site in accordance with a recovery point objective (RPO);
associate a tag structure with the generated snapshot, the tag structure configured to coordinate one or more operations between a first software component operating on the snapshot and a second software component operating on the snapshot, wherein the first and second software components are distinct;
replicate the snapshot and tag structure as a recovery point to the secondary site; and
control an operation of the first software component directed to the snapshot using the tag structure while maintaining the RPO.
22. The apparatus of claim 21 wherein the first software component includes garbage collection and wherein the second software component includes snapshot generation.
23. The apparatus of claim 21 wherein the operation of the first software component is garbage collection of unneeded data from the snapshot.
24. The apparatus of claim 21 wherein the program instructions are further configured to:
organize the tag structure as a key-value structure, wherein the key indicates the operation that requires coordination between the distinct software components and the value indicates multi-cardinality that provides parameters for coordination of the operation among the software components.
25. The apparatus of claim 21 wherein the tag structure includes a tag used as a lock identifying the software component holding the lock.
26. The apparatus of claim 25 wherein the tag structure includes an additional tag indicating an expiry time for the tag used as the lock, and wherein the tag and additional tag are associated with a same key.
27. The apparatus of claim 21 wherein the tag structure is a system defined tag that is used for client/server coordination among the software components and wherein one of the first software component or second software component is a server application configured to take an action based on a value specified in the tag.
28. The apparatus of claim 27 wherein the system defined tag has a key and format of the value defined by the server application.
29. The apparatus of claim 21 wherein the tag structure is a user defined tag for client/client coordination among client applications configured to use a recovery point for the RPO and wherein one of the first software component or second software component is a client application.
30. The apparatus of claim 29 wherein the user defined tag has as a key and format of a value defined by the client application and unusable to a server application.