Abstract: Provided are a computer program product, system, and method for coordinating establishment of source and target copy relationships on primary and secondary servers. A command is received to establish a primary copy relationship of primary source data in the primary storage to copy to primary target data in the primary storage and a secondary copy relationship of secondary source data in the secondary storage to copy to secondary target data in the secondary storage. A determination is made as to whether a part of the secondary target data in a secondary pre-existing copy relationship at the secondary storage can be withdrawn from the secondary pre-existing copy relationship. In response to determining that the part of the secondary target data in the secondary pre-existing copy relationship can be withdrawn, establishing the primary copy relationship for the primary storage and establishing the secondary copy relationship for the secondary storage.

Abstract: A computer-implemented method according to one aspect includes monitoring a current usage of a backup storage space for a storage volume; comparing the current usage to a capacity threshold; and conditionally increasing a size of the backup storage space, based on the comparing and a predetermined size limitation.

Abstract: A computer-implemented method according to one embodiment includes identifying data to be transferred as part of a point-in-time snapshot copy operation; setting a data consistency application in an idle state; marking the data while the data consistency application is in the idle state; restarting the data consistency application; identifying, by the data consistency application, the marked data; creating, by the data consistency application, a consistency group including the marked data; and performing replication of the consistency group.

Abstract: A computer-implemented method according to one embodiment includes receiving a request to withdraw a point-in-time snapshot copy operation being implemented by a data consistency application; in response to determining that the data consistency application is creating a current consistency group, maintaining the withdrawal request while allowing the creation of the current consistency group by the data consistency application; and in response to determining that the data consistency application is idle, preventing a formation of a new consistency group by the data consistency application during the withdrawal of the point-in-time snapshot copy operation.

Abstract: A computer-implemented method according to one aspect includes receiving an indication of a track range to be released within a storage volume; identifying a data backup within a backup storage space for the storage volume that corresponds to the track range; and releasing the track range within the storage volume in response to determining that the corresponding data backup has expired within the backup storage space.

Abstract: A computer-implemented method according to one aspect includes monitoring a current usage of a backup storage space for a storage volume; comparing the current usage to a capacity threshold; and conditionally increasing a size of the backup storage space, based on the comparing and a predetermined size limitation.

Abstract: A computer-implemented method according to one aspect includes receiving a request to increase a size of a backup storage space for a storage volume; adding additional extents to the backup storage space in response to the request; identifying a current extent location within the backup storage space; determining whether any filled extent locations exist between the current extent location and the additional extents added to the backup storage space; and conditionally utilizing the additional extents added to the backup storage space, based on the determining.

Abstract: A computer-implemented method according to one aspect includes receiving an indication of a track range to be released within a storage volume; identifying a data backup within a backup storage space for the storage volume that corresponds to the track range; and releasing the track range within the storage volume in response to determining that the corresponding data backup has expired within the backup storage space.

Abstract: A computer-implemented method according to one aspect includes receiving a request to increase a size of a backup storage space for a storage volume; adding additional extents to the backup storage space in response to the request; identifying a current extent location within the backup storage space; determining whether any filled extent locations exist between the current extent location and the additional extents added to the backup storage space; and conditionally utilizing the additional extents added to the backup storage space, based on the determining.

Abstract: A computer-implemented method according to one embodiment includes identifying data to be transferred as part of a point-in-time snapshot copy operation; setting a data consistency application in an idle state; marking the data while the data consistency application is in the idle state; restarting the data consistency application; identifying, by the data consistency application, the marked data; creating, by the data consistency application, a consistency group including the marked data; and performing replication of the consistency group.

Abstract: A computer-implemented method according to one embodiment includes determining that a consistency group has not been created within a predetermined period of time; sending a request to create the consistency group, where the request includes an indication that a creation of the consistency group is mandatory; identifying one or more logical storage volumes associated with the request to create the consistency group; marking each of the identified one or more logical storage volumes to indicate that a point-in-time snapshot copy operation is not allowed for the one or more logical storage volumes; creating the consistency group; sending the consistency group from a source site to a destination site; and removing the marking from each of the identified one or more logical storage volumes to indicate that a point-in-time snapshot copy operation is allowed for the one or more logical storage volumes.

Abstract: A computer-implemented method according to one embodiment includes receiving a request to withdraw a point-in-time snapshot copy operation being implemented by a data consistency application; in response to determining that the data consistency application is creating a current consistency group, maintaining the withdrawal request while allowing the creation of the current consistency group by the data consistency application; and in response to determining that the data consistency application is idle, preventing a formation of a new consistency group by the data consistency application during the withdrawal of the point-in-time snapshot copy operation.

Abstract: Various embodiments for configuring a medical database by a processor in communication with at least one storage device in a computing environment are provided. Medical data are assigned to a patient. A plurality of data types is organized for the medical data. Portions of each of the plurality of data types are designated as public and private data. A plurality of access levels is organized for the medical data. Each of the plurality of data types includes the plurality of access levels. A first access level of the plurality of access levels corresponds to the patient. The medical data is classified according to the plurality of data types, for each of the plurality of data types, according to the plurality of access levels, and according to one of the public and the private data. The medical data is encrypted in a hierarchical structure corresponding to each of the plurality of access levels.

Abstract: A computer-implemented method according to one embodiment includes determining that a consistency group has not been created within a predetermined period of time; sending a request to create the consistency group, where the request includes an indication that a creation of the consistency group is mandatory; identifying one or more logical storage volumes associated with the request to create the consistency group; marking each of the identified one or more logical storage volumes to indicate that a point-in-time snapshot copy operation is not allowed for the one or more logical storage volumes; creating the consistency group; sending the consistency group from a source site to a destination site; and removing the marking from each of the identified one or more logical storage volumes to indicate that a point-in-time snapshot copy operation is allowed for the one or more logical storage volumes.

Abstract: A method for invalidating metadata associated with a target count-key-data (CKD) volume is disclosed. The method initially receives a command for a target CKD volume. The command is either an “establish” command for establishing a point-in-time copy relationship, or a “withdraw” command for withdrawing a point-in-time copy relationship. The method determines a track range, spanning a number of data tracks in the CKD volume, associated with the command. Each data track in the track range is associated with a metadata track. For each metadata track whose associated data tracks are fully contained in the track range, the method performs a first procedure. For each metadata track whose associated data tracks are not fully contained in the track range, the method performs a second procedure different from the first procedure. A corresponding apparatus and computer program product are also disclosed.

Abstract: Various embodiments for configuring a medical database by a processor in communication with at least one storage device in a computing environment are provided. Medical data are assigned to a patient. A plurality of data types is organized for the medical data. Portions of each of the plurality of data types are designated as public and private data. A plurality of access levels is organized for the medical data. Each of the plurality of data types includes the plurality of access levels. A first access level of the plurality of access levels corresponds to the patient. The medical data is classified according to the plurality of data types, for each of the plurality of data types, according to the plurality of access levels, and according to one of the public and the private data. The medical data is encrypted in a hierarchical structure corresponding to each of the plurality of access levels.