Abstract: A host system communicates to a production system that performs point-in-time copy operations to a backup system to generate a logical corruption protection (LCP) copy of a production copy that comprises a data set, wherein the point-in-time copy operations perform copying at a media level in which physical tracks are copied from the production system to the backup system, and wherein the point-in-time copy operations avoid using information on the data set or file structure that is included in a media on which the data set is stored. In response to a detection of a logical corruption in the data set, a recovery application executing in the host system recovers the data set from the LCP copy.

Abstract: Provided are a computer program product, system and method for data storage volume record management for application-level recovery in accordance with the present description. In one embodiment, logical volume movement is addressed when performing enterprise application recovery. In one embodiment, a host-based recovery product in accordance with the present description, can detect logical volume movement from one physical device to another and proactively prevent application level recovery that potentially may result in data loss. In one embodiment, a time-based capturing of pairings of logical and physical volume identifiers or descriptors within storage configuration records and sub-records are used to surgically recover volumes of an application from enterprise level protection copy of physical media. This history of pairings facilitates many types of logical volume to physical media remapping, such as the regular migration of data to replacement storage controllers which can occur at various times.

Abstract: Provided are a computer program product, system and method for data storage volume record management for application-level recovery in accordance with the present description. In one embodiment, logical volume movement is addressed when performing enterprise application recovery. In one embodiment, a host-based recovery product in accordance with the present description, can detect logical volume movement from one physical device to another and proactively prevent application level recovery that potentially may result in data loss. In one embodiment, a time-based capturing of pairings of logical and physical volume identifiers or descriptors within storage configuration records and sub-records are used to surgically recover volumes of an application from enterprise level protection copy of physical media. This history of pairings facilitates many types of logical volume to physical media remapping, such as the regular migration of data to replacement storage controllers which can occur at various times.

Abstract: Embodiments relate to a system, program product, and method for dynamically capturing environmental configuration changes related to applications such that application-level recoveries may be performed from enterprise-level image copy backups.

Abstract: Embodiments relate to a system, program product, and method for optimizing the throughput of an archival application through storage volume and file selection and assignment of a finite number of storage controller data movement threads associated with a plurality of storage controllers. Data directed to be transferred from one or more storage controllers to non-cloud-based storage is transferred through standard I/O features. Data directed to be transferred from the storage controllers to cloud object storage devices is managed through an archival application that manages the finite number of storage controller data movement threads to provide efficient and effective transfer of the data.

Abstract: A host system communicates to a production system that performs point-in-time copy operations to a backup system to generate a logical corruption protection (LCP) copy of a production copy that comprises a data set, wherein the point-in-time copy operations perform copying at a media level in which physical tracks are copied from the production system to the backup system, and wherein the point-in-time copy operations avoid using information on the data set or file structure that is included in a media on which the data set is stored. In response to a detection of a logical corruption in the data set, a recovery application executing in the host system recovers the data set from the LCP copy.

Abstract: Embodiments relate to a system, program product, and method for optimizing the throughput of an archival application through storage volume and file selection and assignment of a finite number of storage controller data movement threads associated with a plurality of storage controllers. Data directed to be transferred from one or more storage controllers to non-cloud-based storage is transferred through standard I/O features. Data directed to be transferred from the storage controllers to cloud object storage devices is managed through an archival application that manages the finite number of storage controller data movement threads to provide efficient and effective transfer of the data.

Abstract: Embodiments relate to a system, program product, and method for dynamically capturing environmental configuration changes related to applications such that application-level recoveries may be performed from enterprise-level image copy backups.

Abstract: Provided are a method, system, and article of manufacture for converting backup copies of objects created using a first backup program to backup copies created using a second backup program. A plurality of backup copies of versions of an object are created using a first backup program, wherein the object has an object name. The first backup program is used to restore at least one of the backup copies to a restored version of the object having a name different from the object name. A second backup program is used to create a backup copy of each restored version of the object. A name of a designated object is assigned to each backup copy created using the second backup program. Metadata of each backup copy created using the second backup program is updated with metadata for the designated object.

Abstract: Provided are a method, system, and article of manufacture for converting backup copies of objects created using a first backup program to backup copies created using a second backup program. A plurality of backup copies of versions of an object are created using a first backup program, wherein the object has an object name. The first backup program is used to restore at least one of the backup copies to a restored version of the object having a name different from the object name. A second backup program is used to create a backup copy of each restored version of the object. A name of a designated object is assigned to each backup copy created using the second backup program. Metadata of each backup copy created using the second backup program is updated with metadata for the designated object.

Abstract: Provided are a method, system, and article of manufacture for converting backup copies of objects created using a first backup program to backup copies created using a second backup program. A plurality of backup copies of versions of an object are created using a first backup program, wherein the object has an object name. The first backup program is used to restore at least one of the backup copies to a restored version of the object having a name different from the object name. A second backup program is used to create a backup copy of each restored version of the object. A name of a designated object is assigned to each backup copy created using the second backup program. Metadata of each backup copy created using the second backup program is updated with metadata for the designated object.

Abstract: An apparatus, system, and method are disclosed for recovering multivolume data. In one embodiment, a backup module physically backs up a plurality of source volumes to plurality of backup volumes. A data set size module may also capture a data set size for a data set during the physical backup. A retrieval module retrieves metadata for the data set from a catalog. A location module locates the data set on the plurality of backup volumes using the metadata. A recovery module recovers the data set as a recovered data set from the plurality of backup volumes. In one embodiment, a verification module verifies that the recovered data set is successfully recovered.

Abstract: Provided are a method, system, and article of manufacture for converting backup copies of objects created using a first backup program to backup copies created using a second backup program. A plurality of backup copies of versions of an object are created using a first backup program, wherein the object has an object name. The first backup program is used to restore at least one of the backup copies to a restored version of the object having a name different from the object name. A second backup program is used to create a backup copy of each restored version of the object. A name of a designated object is assigned to each backup copy created using the second backup program. Metadata of each backup copy created using the second backup program is updated with metadata for the designated object.

Abstract: A system and method for managing servers. The system comprises a plurality of servers for processing messages, at least one client for transmitting messages to and receiving messages from the servers, and processor means for maintaining a list indicating whether at least one of the servers is eligible to process messages. Preferably, the servers are adapted to process messages of different types; and the processor means includes means to indicate on said list whether, for each of the different types of messages, at least one of the servers is eligible to process each of the different types of messages. Also, in the preferred embodiment, each of the clients includes means to read the list, before the client transmits a message of a given type to one of the servers, to determine whether at least one of the servers is eligible to process messages of the given type.

Abstract: Disclosed are a queue management system and a method of managing a queue. This system and method are for use with a parallel processing system including a plurality of clients and a plurality of processors. The clients receive messages and transmit the messages to a shared queue for storage, and the processors retrieve messages from the shared queue and process said messages. The queue management system includes a mirror queue for maintaining a copy of each message transmitted to the shared queue by one of the clients; and the queue management system stores to the mirror queue, a copy of each message transmitted to the shared queue by that one of the clients. The mirror queue provides the system with continuity in case of an outage of the shared queue. In the event of such an outage, each instance of an application can simply discontinue using the shared queue and process requests from the mirror queue. The mirror queue is used until the shared queue is once again available.

Abstract: A system and method for managing servers. The system comprises a plurality of servers for processing messages, at least one client for transmitting messages to and receiving messages from the servers, and processor means for maintaining a list indicating whether at least one of the servers is eligible to process messages. Preferably, the servers are adapted to process messages of different types; and the processor means includes means to indicate on said list whether, for each of the different types of messages, at least one of the servers is eligible to process each of the different types of messages. Also, in the preferred embodiment, each of the clients includes means to read the list, before the client transmits a message of a given type to one of the servers, to determine whether at least one of the servers is eligible to process messages of the given type.

Abstract: An apparatus, system, and method are disclosed for managing multiple copy versions of a source volume. In one embodiment, the apparatus includes a replication record management module, a pre-pairing record management module, and a copy record module. The replication record management module is configured to maintain a current replication record that is descriptive of a current copy version of the source volume. The pre-pairing record management module is configured to maintain a future pre-pairing record that is descriptive of a future copy version of the source volume. The copy record module is configured to create a copy record from a pre-copy record. The pre-copy record may be either the current replication record or the future pre-pairing record. The apparatus, system, and method beneficially maintain multiple records to describe different states for a particular copy version and dynamically handle changes to a source pool, a target pool, or both in a data copy environment.

Abstract: An apparatus, system, and method are disclosed for recovering multivolume data. In one embodiment, a backup module physically backs up a plurality of source volumes to plurality of backup volumes. A data set size module may also capture a data set size for a data set during the physical backup. A retrieval module retrieves metadata for the data set from a catalog. A location module locates the data set on the plurality of backup volumes using the metadata. A recovery module recovers the data set as a recovered data set from the plurality of backup volumes. In one embodiment, a verification module verifies that the recovered data set is successfully recovered.

Abstract: A queue management system and a method of managing a queue. This system and method are for use with a parallel processing system including a plurality of clients and a plurality of processors. The clients receive messages and transmit the messages to a shared queue for storage, and the processors retrieve messages from the shared queue and process said messages. The queue management system includes a mirror queue for maintaining a copy of each message transmitted to the shared queue by one of the clients; and means, running on said one of the clients, for storing to the mirror queue, a copy of each message transmitted to the shared queue by said one of the clients. The mirror queue provides the system with continuity in case of an outage of the shared queue. In the event of such an outage, each instance of an application can simply discontinue using the shared queue and process requests from the mirror queue. The mirror queue is used until the shared queue is once again available.

Abstract: A technique for determining an optimal number of tasks for processing requests is provided. It is determined whether there are one or more first requests that have not been processed. A parallelism assessment is performed for simulating the assignment of said first requests to one or more task representations.