Abstract: A storage controller receives a command from a host application to perform a point-in-time backup of a source dataset to a storage cloud. The storage controller generates a target dataset via a point-in-time copy of the source dataset, and a mapping that indicates a correspondence between locations of the source dataset and locations of the target dataset. The storage controller copies the target dataset to the storage cloud to generate a backup dataset that is the point-in-time backup of the source dataset, wherein the backup dataset is accessible via reference to the locations of the source dataset.

Abstract: A storage controller receives a command from a host application to perform a point-in-time backup of a source dataset to a storage cloud. The storage controller generates a target dataset via a point-in-time copy of the source dataset, and a mapping that indicates a correspondence between locations of the source dataset and locations of the target dataset. The storage controller copies the target dataset to the storage cloud to generate a backup dataset that is the point-in-time backup of the source dataset, wherein the backup dataset is accessible via reference to the locations of the source dataset.

Abstract: A storage controller receives a command from a host application to perform a point-in-time backup of a source dataset to a storage cloud. The storage controller generates a target dataset via a point-in-time copy of the source dataset, and a mapping that indicates a correspondence between locations of the source dataset and locations of the target dataset. The storage controller copies the target dataset to the storage cloud to generate a backup dataset that is the point-in-time backup of the source dataset, wherein the backup dataset is accessible via reference to the locations of the source dataset.

Abstract: A method for copying data from a primary fully provisioned volume to a secondary thin-provisioned volume is disclosed. In one embodiment, such a method includes hosting, on a primary storage system, a fully provisioned volume comprising a plurality of storage elements. A volume table of contents (VTOC) associated with the fully provisioned volume is analyzed to determine which storage elements in the fully provisioned volume have been allocated to data sets. In certain embodiments, the VTOC is copied into memory of a secondary host system and the secondary host system analyzes the copy to determine which storage elements in the fully provisioned volume have been allocated to data sets. The method then copies, from the fully provisioned volume to a secondary thin-provisioned volume, data in only those storage elements that have been allocated to data sets. A corresponding system and computer program product are also disclosed.

Abstract: A storage controller receives a command from a host application to perform a point-in-time backup of a source dataset to a storage cloud. The storage controller generates a target dataset via a point-in-time copy of the source dataset, and a mapping that indicates a correspondence between locations of the source dataset and locations of the target dataset. The storage controller copies the target dataset to the storage cloud to generate a backup dataset that is the point-in-time backup of the source dataset, wherein the backup dataset is accessible via reference to the locations of the source dataset.

Abstract: A method for copying data from a primary thin-provisioned volume to a secondary thin-provisioned volume includes issuing a query to a primary storage system. The primary storage system hosts a thin-provisioned volume made up of multiple storage elements. The method returns, in response to the query, a reply indicating which storage elements in the thin-provisioned volume are backed by physical storage. In certain embodiments, the reply contains a bitmap having a bit for each storage element in the thin-provisioned volume. In other embodiments, the reply contains a starting address and ending address for each storage area that is backed, or not backed, by physical storage. The method then copies, from the primary storage system to a secondary storage system, data in only those storage elements that are backed by physical storage. A corresponding system and computer program product are also disclosed.

Abstract: A storage controller receives a command from a host application to perform a point-in-time backup of a source dataset to a storage cloud. The storage controller generates a target dataset via a point-in-time copy of the source dataset, and a mapping that indicates a correspondence between locations of the source dataset and locations of the target dataset. The storage controller copies the target dataset to the storage cloud to generate a backup dataset that is the point-in-time backup of the source dataset, wherein the backup dataset is accessible via reference to the locations of the source dataset.

Abstract: A storage controller receives a command from a host application to perform a point-in-time backup of a source dataset to a storage cloud. The storage controller generates a target dataset via a point-in-time copy of the source dataset, and a mapping that indicates a correspondence between locations of the source dataset and locations of the target dataset. The storage controller copies the target dataset to the storage cloud to generate a backup dataset that is the point-in-time backup of the source dataset, wherein the backup dataset is accessible via reference to the locations of the source dataset.

Abstract: A method for copying data from a primary fully provisioned volume to a secondary thin-provisioned volume is disclosed. In one embodiment, such a method includes hosting, on a primary storage system, a fully provisioned volume comprising a plurality of storage elements. A volume table of contents (VTOC) associated with the fully provisioned volume is analyzed to determine which storage elements in the fully provisioned volume have been allocated to data sets. In certain embodiments, the VTOC is copied into memory of a secondary host system and the secondary host system analyzes the copy to determine which storage elements in the fully provisioned volume have been allocated to data sets. The method then copies, from the fully provisioned volume to a secondary thin-provisioned volume, data in only those storage elements that have been allocated to data sets. A corresponding system and computer program product are also disclosed.

Abstract: Embodiments of the present invention provide systems, methods, and computer program products for managing computing devices to handle an input/output (I/O) request. In one embodiment, the I/O request may eligible for performance throttling based, at least in part, on the associated importance level for performing the received I/O request and one or more characteristics of the received I/O request. Embodiments of the present invention provide systems, methods, and computer program products for throttling the I/O request and transmitting the I/O request to a storage controller.

Abstract: A method for copying data from a primary thin-provisioned volume to a secondary thin-provisioned volume includes issuing a query to a primary storage system. The primary storage system hosts a thin-provisioned volume made up of multiple storage elements. The method returns, in response to the query, a reply indicating which storage elements in the thin-provisioned volume are backed by physical storage. In certain embodiments, the reply contains a bitmap having a bit for each storage element in the thin-provisioned volume. In other embodiments, the reply contains a starting address and ending address for each storage area that is backed, or not backed, by physical storage. The method then copies, from the primary storage system to a secondary storage system, data in only those storage elements that are backed by physical storage. A corresponding system and computer program product are also disclosed.

Abstract: A computer implemented method includes the steps of establishing a plurality of storage control sessions, wherein each storage control session associates at least one primary storage controller and at least one secondary storage controller with a predetermined path through a data transport network that interconnects the primary and secondary storage controllers; identifying storage control sessions that have data available to be transferred from primary storage controllers to secondary storage controllers; accumulating available data for each session and determining transfer time through the network for each data element to estimate prospective bandwidth utilization; and determining, for a predetermined time interval, whether transferring the available data would fully occupy available bandwidth of the data transport network for the predetermined time interval.

Abstract: When the mirrored point in time copy fails, at that point in time all the data for making the source and target of the point in time copy consistent is available on secondary volumes at disaster recovery site. The data for the source and target of the failed point in time copy are logically and physically equal at that point in time. This logical relationship can be maintained, and protected against ongoing physical updates to the affected tracks on the source secondary volume, by first reading the affected tracks from the source secondary volume, copying the data to the target secondary volume, and then writing the updated track to the source secondary volume.

Abstract: A method for backing up data is disclosed. In one embodiment, such a method includes sending, from a host system to a storage system, a first request to make a logical point-in-time copy of production data on the storage system. The storage system executes the first request by creating the logical point-in-time copy thereon. An identifier is assigned to the logical point-in-time copy. The method further sends, from the host system to the storage system, a second request to directly copy a specified portion of data in the logical point-in-time copy to cloud storage. The second request identifies the logical point-in-time copy using the identifier. The storage system executes the second request by directly copying the specified portion from the logical point-in-time copy to the cloud storage. A corresponding system and computer program product are also disclosed.

Abstract: Embodiments of the present invention provide systems, methods, and computer program products for managing computing devices to handle an input/output (I/O) request. In one embodiment, the I/O request may eligible for performance throttling based, at least in part, on the associated importance level for performing the received I/O request and one or more characteristics of the received I/O request. Embodiments of the present invention provide systems, methods, and computer program products for throttling the I/O request and transmitting the I/O request to a storage controller.

Abstract: Embodiments of the present invention provide systems, methods, and computer program products for managing computing devices to handle an input/output (I/O) request. In one embodiment, the I/O request may eligible for performance throttling based, at least in part, on the associated importance level for performing the received I/O request and one or more characteristics of the received I/O request. Embodiments of the present invention provide systems, methods, and computer program products for throttling the I/O request and transmitting the I/O request to a storage controller.

Abstract: Embodiments of the present invention provide systems, methods, and computer program products for managing computing devices to handle an input/output (I/O) request. In one embodiment, the I/O request may eligible for performance throttling based, at least in part, on the associated importance level for performing the received I/O request and one or more characteristics of the received I/O request. Embodiments of the present invention provide systems, methods, and computer program products for throttling the I/O request and transmitting the I/O request to a storage controller.

Abstract: Embodiments of the present invention provide systems, methods, and computer program products for managing computing devices to handle an input/output (I/O) request. In one embodiment, the I/O request may eligible for performance throttling based, at least in part, on the associated importance level for performing the received I/O request and one or more characteristics of the received I/O request. Embodiments of the present invention provide systems, methods, and computer program products for throttling the I/O request and transmitting the I/O request to a storage controller.

Abstract: A computer-implemented method, carried out by one or more processors, for a modified asynchronous replication session. In an embodiment, the method comprises the steps of acquiring a lock on a volume configuration, where the lock prevents changes to the volume configuration between a first volume and a second volume at a remote site. Internal control block information is updated, where the update includes at least a volume serial number of the first volume matching a volume serial number of the second volume. Responsive to updating internal control block information, the acquired lock is released to allow changes to the volume configuration.

Abstract: An input/output (I/O) request is received that indicates a priority for performing the received I/O request by a storage controller. If a base device is not available to handle the received I/O request, whether the received I/O request is eligible for performance throttling is determined. The received I/O request is transmitted to the storage controller indicating whether the received I/O request is eligible for performance throttling. An alias device is allocated to the base device based on the priority for performing the received I/O request. If the throttling information received from the storage controller for the previous I/O request indicates that a request type of the received I/O request is not being throttled, and it is determined that the received I/O request is a new request, then a control block is representing the base device is flagged, indicating that the received I/O request is eligible for performance throttling.