Abstract: Provided are a method, system, and article of manufacture for splitting writes between a storage controller and replication engine. A splitter executing in a storage controller manages access to primary volumes. An initialization command is received to communicate with a replication engine. A replication command is received for one primary volume and the primary volume is indicated as subject to replication. A write request is received to write data to a target primary volume of the primary volumes that is indicated as subject to the replication. The data in the write request is written to the target primary volume. The data in the write request is sent to the replication engine. The replication engine executes a copy services function associated with the target primary volume to write the data to a replication engine volume.

Abstract: Provided are a method, system, and article of manufacture for managing writes received to data units that are being transferred to a secondary storage as part of a mirror relationship. Synchronization information indicates data units to transfer from a primary storage to a secondary storage, wherein the synchronization information data is updated to indicate the transfer of one of the data units from the primary storage to the secondary storage. A storage controller receives a write request having an update to a target data unit comprising one of the data units indicated in the synchronization information that has not been transferred from the primary storage to the secondary storage. The write request is allowed to apply the update to the target data unit in response to transferring the data in the target data unit to a network adapter of the storage controller and before the data in the target data unit is transferred to the secondary storage.

Abstract: Provided are a method, system, and article of manufacture for splitting writes between a storage controller and replication engine. A splitter executing in a storage controller manages access to primary volumes. An initialization command is received to communicate with a replication engine. A replication command is received for one primary volume and the primary volume is indicated as subject to replication. A write request is received to write data to a target primary volume of the primary volumes that is indicated as subject to the replication. The data in the write request is written to the target primary volume. The data in the write request is sent to the replication engine. The replication engine executes a copy services function associated with the target primary volume to write the data to a replication engine volume.

Abstract: Provided are a method, system, and article of manufacture for splitting writes between a storage controller and replication engine. A splitter executing in a storage controller manages access to primary volumes. An initialization command is received to communicate with a replication engine. A replication command is received for one primary volume and the primary volume is indicated as subject to replication. A write request is received to write data to a target primary volume of the primary volumes that is indicated as subject to the replication. The data in the write request is written to the target primary volume. The data in the write request is sent to the replication engine. The replication engine executes a copy services function associated with the target primary volume to write the data to a replication engine volume.

Abstract: Provided are a method, system, and article of manufacture for using virtual copies in a failover and failback environment. Updates are copied from a primary first storage at the primary site to a secondary first storage at the secondary site during system operations. A second storage is maintained at at least one of the primary and secondary sites. A failover is performed from the primary site to the secondary site after a failure at the primary site. The at least one second storage is used after recovery of the primary site to synchronize the secondary site to the primary site. Only updates made to the secondary site during the failover are copied to or from the at least one second storage in response to the recovery at the primary site.

Abstract: Provided are a method, system, and article of manufacture for a replication engine communicating with a splitter to split writes between a storage controller and replication engine. Communication is initiated with the splitter implemented in a storage controller managing access to primary volumes. A command is sent to the splitter to copy writes to one primary volume to the replication engine. Write data is received from the splitter to one of the primary volumes following the splitter receiving the command to copy the writes to the replication engine. A determination is made of a copy services function to use for the received data. The determined copy services function is invoked to transfer the received data to a secondary storage volume.

Abstract: Techniques are provided for performing a copy operation. A fast reverse restore command indicating a new source and a new target is received, wherein the new source is an original target and the new target is an original source. A synchronous scan is performed on the new target. A new target structure associated with the new target is updated using a new source structure associated with the new source. Techniques are also provided for performing a copy operation in which a fast reverse restore command is received after an instant virtual copy has been performed from a new target to a new source and wherein the fast reverse restore command is performed before a background copy has been performed by the instant virtual copy.

Abstract: Provided are a method, system, and article of manufacture for copying storage. Data sent from a first storage unit is synchronously copied at a second storage unit. The copied data is sent asynchronously from the second storage unit to a third storage unit.

Abstract: Techniques are provided for performing a copy operation. A fast reverse restore command indicating a new source and a new target is received, wherein the new source is an original target and the new target is an original source. A synchronous scan is performed on the new target. A new target structure associated with the new target is updated using a new source structure associated with the new source. Techniques are also provided for performing a copy operation in which a fast reverse restore command is received after an instant virtual copy has been performed from a new target to a new source and wherein the fast reverse restore command is performed before a background copy has been performed by the instant virtual copy.

Abstract: Techniques are provided for performing a copy operation. A fast reverse restore command indicating a new source and a new target is received, wherein the new source is an original target and the new target is an original source. A synchronous scan is performed on the new target. A new target structure associated with the new target is updated using a new source structure associated with the new source. Techniques are also provided for performing a copy operation in which a fast reverse restore command is received after an instant virtual copy has been performed from a new target to a new source and wherein the fast reverse restore command is performed before a background copy has been performed by the instant virtual copy.

Abstract: Provided are a method, system, and article of manufacture for using virtual copies in a failover and failback environment. Updates are copied from a primary first storage at the primary site to a secondary first storage at the secondary site during system operations. A second storage is maintained at at least one of the primary and secondary sites. A failover is performed from the primary site to the secondary site after a failure at the primary site. The at least one second storage is used after recovery of the primary site to synchronize the secondary site to the primary site. Only updates made to the secondary site during the failover are copied to or from the at least one second storage in response to the recovery at the primary site.

Abstract: Provided are a method, system, and article of manufacture for using virtual copies in a failover and failback environment. Updates are copied from a primary first storage at the primary site to a secondary first storage at the secondary site during system operations. A second storage is maintained at least one of the primary and secondary sites. A failover is performed from the primary site to the secondary site after a failure at the primary site. The at least one second storage is used after recovery of the primary site to synchronize the secondary site to the primary site. Only updates made to the secondary site during the failover are copied to or from the at least one second storage in response to the recovery at the primary site.

Abstract: Provided are a method, system, and program for forming a consistency group of data. Information is provided on a consistency group relationship indicating a plurality of slave controllers and, for each indicated slave controller, a slave storage unit managed by the slave controller. A command is transmitted to each slave controller in the consistency group relationship to cause each slave controller to transmit data in the slave storage unit to a remote storage in a manner that forms the consistency group. A determination is made as to whether all the slave controllers successfully transmitted the data in the slave storage units that is part of the consistency group to the remote storage.

Abstract: Provided are a method, system, deployment and program for managing data transfer in consistency group formation. In one embodiment, nodes are periodically polled to determine traffic conditions. An estimated drain time for a node such as the most congested node, for example, is compared to a drain time limit and if within a vicinity of the drain time limit, operations switch to a consistency group formation mode. Other embodiments are described and claimed.

Abstract: Provided are a method, system, deployment and program for managing data transfer in consistency group formation. In one embodiment, a transfer time for a data structure is selected as a function of at least one determined backlog. Upon expiration of the selected transfer time, the mode of operation may be switched. By dynamically selecting a transfer time, backlogs may be reduced to increase the likelihood of successful creation of a consistency group. Other embodiments are described and claimed.

Abstract: An apparatus, system, and method are disclosed for activating a synchronous mirror as a primary storage volume. The apparatus system and method include directing a third storage volume to store updates sent to the third storage volume from a second storage volume onto a first storage volume in response to the first storage volume becoming operational after a failure, terminating sending updates from the second storage volume to the third storage volume in response to the first storage volume becoming substantially consistent with the third storage volume, and synchronously storing updates received by the second storage volume on the first storage volume and asynchronously storing updates received by the first storage volume on the third storage volume in response to terminating sending updates from the second storage volume to the third storage volume after the first and third storage volumes are substantially consistent.

Abstract: Provided are a method, system, and article of manufacture for managing writes received to data units that are being transferred to a secondary storage as part of a mirror relationship. Synchronization information indicates data units to transfer from a primary storage to a secondary storage, wherein the synchronization information data is updated to indicate the transfer of one of the data units from the primary storage to the secondary storage. A storage controller receives a write request having an update to a target data unit comprising one of the data units indicated in the synchronization information that has not been transferred from the primary storage to the secondary storage. The write request is allowed to apply the update to the target data unit in response to transferring the data in the target data unit to a network adapter of the storage controller and before the data in the target data unit is transferred to the secondary storage.

Abstract: Provided are a method, system, and article of manufacture, wherein a primary control unit sends a selected time to a plurality of secondary control units. Clocks are periodically synchronized at the primary control unit and the secondary control units with a time server. The primary control unit and the plurality of secondary control units consistently update secondary storage subsystems coupled to the plurality of secondary control units at the selected time.

Abstract: Techniques are provided for performing a copy operation. A fast reverse restore command indicating a new source and a new target is received, wherein the new source is an original target and the new target is an original source. A synchronous scan is performed on the new target. A new target structure associated with the new target is updated using a new source structure associated with the new source. Techniques are also provided for performing a copy operation in which a fast reverse restore command is received after an instant virtual copy has been performed from a new target to a new source and wherein the fast reverse restore command is performed before a background copy has been performed by the instant virtual copy.

Abstract: Provided are a method, system, and program for maintaining consistency when mirroring data using different copy technologies. Update groups having updates to primary storage locations are formed using a first copy technology. The updates in the update groups are copied to secondary storage locations. Update groups having updates to primary storage locations are formed using a second copy technology, wherein the updates in the update groups are copied to secondary storage locations. Indication is made in a data structure of a time of an update in response to including the update in one of the update groups formed using the first copy technology. Indication is also made in the data structure of a time of the update group formed using the second copy technology.