Abstract: A method for performing a write to a volume x in a cascaded architecture is described. In one embodiment, such a method includes determining whether the volume x has a child volume, wherein each of the volume x and the child volume have a target bit map (TBM) associated therewith. The method then determines whether the TBMs of both the volume x and the child volume are set. If the TBMs are set, the method finds a higher source (HS) volume from which to copy the desired data to the child volume. Finding the HS volume includes travelling up the cascaded architecture until the source of the data is found. Once the HS volume is found, the method copies the data from the HS volume to the child volume and performs the write to the volume x. A method for performing a read is also disclosed herein.

Abstract: A method for performing a write to a volume x in a cyclic point-in-time-copy architecture is described. In one embodiment, such a method includes determining whether the volume x has a child volume. The method then determines whether the target bit maps (TBMs) of both the volume x and the child volume are set. If the TBMs are set, the method finds a higher source (HS) volume from which to copy the desired data to the child volume. Once the HS volume is found, the method determines whether the HS volume and the child volume are the same volume. If the HS volume and the child volume are not the same volume, the method copies the data from the HS volume to the child volume. The method then performs the write to the volume x.

Abstract: A method for deleting a relation between a source and a target in a multi-target architecture is described. The multi-target architecture includes a source and multiple targets mapped thereto. In one embodiment, such a method includes initially identifying a relation for deletion from the multi-target architecture. A target associated with the relation is then identified. The method then identifies a sibling target that inherits data from the target. Once the target and the sibling target are identified, the method copies the data from the target to the sibling target. The relation between the source and the target is then deleted. A corresponding computer program product is also disclosed and claimed herein.

Abstract: A method for performing a write to a source volume in a multi-target architecture is described. The multi-target architecture includes a source volume and multiple target volumes mapped thereto. In one embodiment, such a method includes copying data in a track of the source volume to a corresponding track of a target volume (target x). The method enables one or more sibling target volumes (siblings) mapped to the source volume to inherit the data from the target x. When the data is successfully copied to the target x, the method performs a write to the track of the source volume. Other methods for reading and writing data to volumes in the multi-target architecture are also described.

Abstract: A method for performing a write to a volume x in a cyclic point-in-time-copy architecture is described. In one embodiment, such a method includes determining whether the volume x has a child volume. The method then determines whether the target bit maps (TBMs) of both the volume x and the child volume are set. If the TBMs are set, the method finds a higher source (HS) volume from which to copy the desired data to the child volume. Once the HS volume is found, the method determines whether the HS volume and the child volume are the same volume. If the HS volume and the child volume are not the same volume, the method copies the data from the HS volume to the child volume. The method then performs the write to the volume x. A corresponding computer program product is also described.

Abstract: A method for deleting a relation between a source and a target in a multi-target architecture is described. The multi-target architecture includes a source and multiple targets mapped thereto. In one embodiment, such a method includes initially identifying a relation for deletion from the multi-target architecture. A target associated with the relation is then identified. The method then identifies a sibling target that inherits data from the target. Once the target and the sibling target are identified, the method copies the data from the target to the sibling target. The relation between the source and the target is then deleted. A corresponding computer program product is also disclosed and claimed herein.

Abstract: A method for providing rolling continuous data protection of source data is disclosed. In one embodiment, such a method includes enabling a user to select source data and establish a first interval when point-in-time copies of the source data are generated. The method further enables the user to specify a first number of point-in-time copies to retain at the first interval. The method further enables the user to specify a second number of point-in-time copies to retain at a second interval, wherein the second interval is a (n?2) multiple of the first interval. The method further enables the user to specify a third number of point-in-time copies to retain at a third interval, wherein the third interval is a (n?2) multiple of the second interval. A corresponding apparatus and computer program product are also disclosed.

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: A method, system, and computer program product for managing modified metadata in a storage controller cache pursuant to a recovery action by a processor in communication with a memory device is provided. A count of modified metadata tracks for a storage rank is compared against a predetermined criterion. If the predetermined criterion is met, a storage volume having the storage rank is designated with a metadata invalidation flag to defer metadata invalidation of the modified metadata tracks until after the recovery action is performed.

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 program for copying tracks between a primary controller and secondary controller. A track is received from the primary controller that is part of a copy job comprising a sequence of tracks to copy along with a sequence number of the received track and a context number identifying computational resources in the primary controller used to transmit the track, sequence number, and context number. The context number and sequence number transmitted with the track are used to determine if a track preceding the received track was written to storage. The secondary-controller writes the received track to storage if the track preceding the received track was written to storage.

Abstract: Provided are a method, system, and an article of manufacture for preventing data loss. Modified data is stored in a volatile storage. The stored modified data is copied onto a non-volatile storage. A determination is made as to whether the non-volatile storage should be checked for errors. In certain implementations, on determining that the nonvolatile storage should be checked for errors the non-volatile storage is checked for errors. If on checking the non-volatile storage is found to have an error, an indication of the error is provided.

Abstract: Provided are a method, system, and program for maintaining data in a first cache and second cache, wherein a backup cache maintains a backup copy of data in the first cache, and wherein the first cache is used to cache a first set of data in a storage system and the second cache is used to cache a second set of data in the storage system. An unavailable state of the first cache is detected. In response to detecting the unavailable state, requests to the first set of data are blocked and at least one space in the second cache is allocated for data in the backup cache. Requests to the first set of data are allowed to proceed after the at least one space is allocated in the second cache and before the data in the backup cache is copied to the at least one allocated space in the second cache. The data from the backup cache is copied to the allocated at least one space in the second cache after the requests to the first set of data are allowed to proceed.

Abstract: Provided are a method, system, and program for maintaining data in a first cache and second cache, wherein a backup cache maintains a backup copy of data in the first cache, and wherein the first cache is used to cache a first set of data in a storage system and the second cache is used to cache a second set of data in the storage system. An unavailable state of the first cache is detected. In response to detecting the unavailable state, requests to the first set of data are blocked and at least one space in the second cache is allocated for data in the backup cache. Requests to the first set of data are allowed to proceed after the at least one space is allocated in the second cache and before the data in the backup cache is copied to the at least one allocated space in the second cache. The data from the backup cache is copied to the allocated at least one space in the second cache after the requests to the first set of data are allowed to proceed.

Abstract: Provided are a method, system, and an article of manufacture for preventing data loss. Modified data is stored in a volatile storage. The stored modified data is copied onto a non-volatile storage. A determination is made as to whether the non-volatile storage should be checked for errors. In certain implementations, on determining that the nonvolatile storage should be checked for errors the non-volatile storage is checked for errors. If on checking the non-volatile storage is found to have an error, an indication of the error is provided.