Abstract: A technique provides network efficient data failover by explicitly protecting one or more common snapshot references at sites of a multi-site data replication environment to improve granularity of control of recovery point objectives (RPO) for data across the sites. A common snapshot reference or recovery point (RP) ensures that, in the event of failure to a site, data designated for failover may be quickly protected by replicating only small incremental changes to the RP so as to maintain RPO requirements across the sites. Illustratively, the technique enhances and extends a disaster recovery (DR) application programming interface (API) protocol through an extension that defines and applies a tag to the RP, wherein the tag enables protection and/or preservation of the RP by ensuring that the sites honor the tag applied to the RP. The tag essentially functions as an advisory lock for the RP that is shared among the sites to prevent deletion of the RP at the sites throughout the duration of the lock.

Abstract: 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.

Abstract: A replication progress tracking technique is configured to present progress tracking state relating to data replicated as a recovery point (RP) from a source site to one or more target and/or remote sites over a network in a multi-site data replication environment. The progress tracking state of the replicated RP, i.e., RP replication progress, is persistently stored as a progress tracking recording at the target site independent of the source site of the replication and presented (i.e., viewed) using a well-defined, published application programming interface that is publicly callable by one or more clients of the environment.

Abstract: A technique provides network efficient data failover by explicitly protecting one or more common snapshot references at sites of a multi-site data replication environment to improve granularity of control of recovery point objectives (RPO) for data across the sites. A common snapshot reference or recovery point (RP) ensures that, in the event of failure to a site, data designated for failover may be quickly protected by replicating only small incremental changes to the RP so as to maintain RPO requirements across the sites. Illustratively, the technique enhances and extends a disaster recovery (DR) application programming interface (API) protocol through an extension that defines and applies a tag to the RP, wherein the tag enables protection and/or preservation of the RP by ensuring that the sites honor the tag applied to the RP. The tag essentially functions as an advisory lock for the RP that is shared among the sites to prevent deletion of the RP at the sites throughout the duration of the lock.

Abstract: A technique provides network efficient data failover by explicitly protecting one or more common snapshot references at sites of a multi-site data replication environment to improve granularity of control of recovery point objectives (RPO) for data across the sites. A common snapshot reference or recovery point (RP) ensures that, in the event of failure to a site, data designated for failover may be quickly protected by replicating only small incremental changes to the RP so as to maintain RPO requirements across the sites. Illustratively, the technique enhances and extends a disaster recovery (DR) application programming interface (API) protocol through an extension that defines and applies a tag to the RP, wherein the tag enables protection and/or preservation of the RP by ensuring that the sites honor the tag applied to the RP. The tag essentially functions as an advisory lock for the RP that is shared among the sites to prevent deletion of the RP at the sites throughout the duration of the lock.