A computer-implemented method for adding active volumes to existing replication configurations may include (1) identifying a new volume to be added to an existing replication configuration that replicates a plurality of volumes to a remote storage device, (2) using interchangeable bitmaps to perform an initial synchronization of the new volume with the remote storage device before replicating the new volume to the remote storage device as part of the existing replication configuration, (3) determining that a replication log associated with the replication configuration is capable of flagging future writes by the application to the new volume without overflowing, and, upon making that determination, (4) replicating the new volume to the remote storage device as part of the existing replication configuration. Various other methods, systems, and computer-readable media are also disclosed.

Configuration and replication can be managed across multiple sites for datacenter volumes. A visual representation of a current configuration for a first of a plurality of replication techniques can be conveyed for display on a display device. Changes can be made to the current configuration, producing a future configuration. The future configuration can be analyzed for replication errors, and an updated visual representation can be produced that identified discovered replication errors and highlights differences between the current configuration and the future configuration. The updated visual representation can be conveyed, for display on a display device.

A method and system for optimized read access to shared data via monitoring of mirroring operations are described. A data storage system performs operations that include one controller in a dual-controller host storage appliance in an asymmetric active/active configuration receiving a request from the host for data on a logical unit number owned by the partner controller. The receiving controller, which has a mirror cache of the partner controller's memory for failure recovery, accesses the mirror cache using a data structure that was populated during previous mirror operations. If the data is found in the mirror cache, it is read from the cache and returned to the requesting host without having to contact the partner controller for the data.

A computer-implemented method, according to one approach, includes: receiving a data operation request which includes an activated compound operation flag. The data operation request is added to a queue in a gateway node, and the data operation request is eventually transmitted to a disaster recovery site. An inode entry which corresponds to the portion of data is locked, and metadata associated with the inode entry is updated to indicate that the data operation request has been performed at the disaster recovery site. Supplemental data operation requests which correspond to the portion of data are also identified by evaluating the metadata associated with the inode entry. These supplemental data operation requests are transmitted to the disaster recovery site, and the metadata associated with the inode entry is updated to indicate that the supplemental data operation requests have been performed at the disaster recovery site. Furthermore, the inode entry is unlocked.

Systems and methods which provide for managing multiple mirror resources in a storage distribution network are provided. In some embodiments, a system provides for both high availability and disaster recovery functionality at different mirroring locations. Other embodiments may provide for multiple high availability and/or multiple disaster recovery mirror resources. These mirror resources are operated in a heterogeneous manner in the sense that each have its own transport, protocol, and the like, but are configured function cooperatively or as a single mirror with respect to mirroring a primary node. Embodiments may provide for the mirroring and resynchronization of mirrored resources in the event of a communication loss with a particular resource without ceasing the mirroring operations to other resources.

A system and method for data replication is provided. A host synchronously replicates data between a first local storage device and a second local storage device, the first local storage device and the second local storage device being coupled to the host. Data is then asynchronously replicated from the first local storage device and the second local storage device to at least one remote storage device. In an embodiment, each of the local storage devices may asynchronously replicate data to remote storage devices located at separate sites to provide four site data replication processing. The system described herein provides for advantageous and efficient swapping of control between hosts and storage devices located in different regions in response to disasters and/or other events affecting data storage in a particular region.

A data storage system includes multiple head nodes and data storage sleds. Volume data is replicated between a primary and one or more secondary head nodes for a volume partition and is further flushed to a set of mass storage devices of the data storage sleds. Volume metadata is maintained in a primary and one or more secondary head nodes for a volume partition and is updated in response to volume data being flushed to the data storage sleds. Also, the primary and secondary head nodes store check-points of volume metadata to the data storage sleds, wherein in response to a failure of a primary or secondary head node for a volume partition, a replacement secondary head node for the volume partition recreates a secondary replica for the volume partition based, at least in part, on a stored volume metadata checkpoint.

A failure in a main site is recovered by operating in the same operational environment as a sub site. A remote copy system includes: a first storage system providing a main site; and a second storage system providing a sub site. A storage controller stores data and an operation processed in the main site as a main site journal, sends the main site journal to the sub site for sequential processing, stores data and an operation processed in the sub site as a sub site journal after a failover to the sub site is performed, and cancels an unreflected operation that is not processed in the sub site after being stored in the main site journal prior to the failover in the main site and sequentially processes the sub site journal in the main site, when a failback to the main site is performed.

A method, system and program product for dynamically changing the size of a LUN in a replication based environment, the replication environment having a splitter, a production site and a replication site, the production site having a production LUN, the replication site having a journal and a replication LUN, comprising changing the LUN size on the production site based on a request to change the size of the LUN on the production site, determining on the replication site that the LUN on the production site has changed size, determining whether it is possible to change the size of the replication LUN, based on a negative determination and in response to a request for the replication LUN, pausing replication, and based on a positive determination, changing or faking the size of the replication LUN.

Example embodiments of the present invention relate to a method, a system, and a computer program product for performing data replication and backup. The method comprises performing a first data replication of a production site storage to a replication site storage and performing a first backup of the production site storage to a production site backup storage. A second data replication then may be performed from the production site backup storage to a backup site backup storage.