Abstract: RDF/QAR bandwidth reduction is a GDDR feature that allows for separate synchronous-only RDF groups from sites DC1->DC2 to be included in the QAR consistency group definition without RDF/A protection. The devices in these sync-only RDF groups form perfect quadruplets like regular QAR devices, but the RDF groups from sites DC1->DC3 and DC2->DC4 are not included in QAR-A and QAR-B Multi Session Consistency group definitions. Instead, these sync-only pairing RDF groups are replicated to the secondary region using ADCOPY-DISK mode or not replicating at all (suspended). The sync-only devices have no QAR recovery capability from sites DC3->DC4, but device pairing from DC3->DC4 is present via sync-only RDF groups.

Abstract: A data protection server running on a Geographically Dispersed Disaster Restart (GDDR) node provides auto-restart of generation of snapsets of versioned data groups (VDGs). Queries are sent to remotely monitor the state of VDG snapset generation at each of a plurality of datacenters at which a host application image is replicated and snapped. Responsive to determining that snapset generation of a VDG at a remote site has ceased, a command is sent to that site to prompt auto-restart of generation of snapsets of the VDG. If the VDG is undefined at the remote site, then a command is sent to the remote site to prompt auto-import of a definition of the VDG before auto-restarting generation of snapsets of the VDG. Either or both auto-import and auto-restart may be enabled or disabled for different VDGs, and auto-restart may be suspended if the VDG data is frozen.

Abstract: A method, comprising: retrieving a VDG definition; processing the VDG definition to identify a primary storage system and one or more secondary storage systems; detecting a consistency formation event; transmitting a first instruction to initialize one or more data structures for a first snapshot of a volume that is stored in the primary storage system; transmitting, to each of the secondary storage systems, a respective second instruction to initialize one or more data structures for a respective snapshot of a copy of the volume that is stored in that secondary storage system; suspending servicing of input-output (I/O) by the primary storage system; transmitting to the primary storage system a third instruction to complete the first snapshot of the volume; transmitting to each of the secondary storage systems a respective fourth instruction to complete a respective snapshot of the copy of the volume; and resuming servicing of I/O.

Abstract: A method, comprising: retrieving a VDG definition; processing the VDG definition to identify a primary storage system and one or more secondary storage systems; detecting a consistency formation event; transmitting a first instruction to initialize one or more data structures for a first snapshot of a volume that is stored in the primary storage system; transmitting, to each of the secondary storage systems, a respective second instruction to initialize one or more data structures for a respective snapshot of a copy of the volume that is stored in that secondary storage system; suspending servicing of input-output (I/O) by the primary storage system; transmitting to the primary storage system a third instruction to complete the first snapshot of the volume; transmitting to each of the secondary storage systems a respective fourth instruction to complete a respective snapshot of the copy of the volume; and resuming servicing of I/O.

Abstract: An Orchestrated Data Recovery (ODR) Cyber Protection Automation (CPA) operates to ensure one-to-one creation of snapsets of a production site and corresponding snapsets of a cyber vault. During an initiation phase, the ODR CPA monitors synchronization of a snapset of production volumes from the production site to the cyber vault. If additional snapsets of the production volumes are created prior to completion of synchronization of the first snapset, the additional snapsets are also synchronized to the cyber vault. Once the initial synchronization of the storage volumes has been completed, the ODR CPA causes a Storage Volume Creation and Management System (SVCMS) to create a snapset of the storage volumes at the cyber vault. Subsequently, each time a snapset is created of the production site, the ODR CPA orchestrates synchronization of the snapset to the cyber vault and creation of a corresponding snapset at the cyber vault.

Abstract: A consistency group is defined to include a set of required devices on a set of storage systems. Write patterns on each of the required devices are monitored and write patterns on each of the other devices on the set of storage systems is monitored. Pairs of devices are formed, in which each pair includes one required device and one other device. Write patterns of the pairs of devices are compared to determine respective percentage coordinated write probabilities for pairs of devices. Write patterns of the pairs of devices are also compared to determine ratios of write operations for pairs of devices. A coordinate write probability above a threshold, or a determined ratio of write operations that occurs sufficiently frequently, is interpreted as an indication that one of the other devices should be included in the consistency group. A learning process is trained and used to analyze the write patterns.

Abstract: A consistency group is defined to include a set of required devices on a set of storage systems. High activity devices are determined, and write dependencies between each high activity device and each low activity devices are monitored. A set of high importance devices is determined to include the high activity devices and low activity devices with a high write dependency on at least one of the high activity devices. Comparative write patterns between the high importance devices and low importance devices are used to determine a set of candidate devices for removal from the consistency group. The high importance devices, rather than all devices of the consistency group, are also used to determine a set of devices that have inadvertently not been included in the consistency group.

Abstract: A consistency group is defined to include a set of required devices on a set of storage systems. High activity devices are determined, and write dependencies between each high activity device and each low activity devices are monitored. A set of high importance devices is determined to include the high activity devices and low activity devices with a high write dependency on at least one of the high activity devices. Comparative write patterns between the high importance devices and low importance devices are used to determine a set of candidate devices for removal from the consistency group. The high importance devices, rather than all devices of the consistency group, are also used to determine a set of devices that have inadvertently not been included in the consistency group.

Abstract: A consistency group is defined to include a set of required devices on a set of storage systems. Write patterns on each of the required devices are monitored and write patterns on each of the other devices on the set of storage systems is monitored. Pairs of devices are formed, in which each pair includes one required device and one other device. Write patterns of the pairs of devices are compared to determine respective percentage coordinated write probabilities for pairs of devices. Write patterns of the pairs of devices are also compared to determine ratios of write operations for pairs of devices. A coordinate write probability above a threshold, or a determined ratio of write operations that occurs sufficiently frequently, is interpreted as an indication that one of the other devices should be included in the consistency group. A learning process is trained and used to analyze the write patterns.

Abstract: The system and methods disclosed herein relate to an improved hardware configuration for geographically dispersed data restart (“GDDR”) systems. Specifically, the teachings herein allow users to reduce the number of operating systems required to run multiple GDDR systems simultaneously by employing multitenancy principles in the system design. The embodiments cover a system for operating multiple GDDR complexes wherein the individual control systems typically required to run each GDDR complex are combined into a single logical partition. We also disclose methods and computer executable products for operating multiple GDDR complexes wherein the individual control systems typically required to run each GDDR complex are combined into a single logical partition.

Abstract: The system, products, and methods disclosed herein relate to an improved configuration for geographically dispersed data restart (“GDDR”) systems. Specifically, the teachings herein ensure a particular GDDR instance does not react to messages issued from address spaces outside of its affinity group. We use the term message “affinity group” to mean the combination of a particular GDDR instance and its set of Mainframe Enablers started tasks. By ensuring that the particular GDDR instance does not react to messages intended for recipients outside of its affinity group, we improve computer functionality and efficiency by facilitating further partitioning of the logical partition. Once the logical partition is further partitioned into additional address spaces, it is possible to run Mainframe Enablers and/or additional GDDR instances independent of the particular GDDR instance of concern.

Abstract: The system, products, and methods disclosed herein relate to an improved configuration for geographically dispersed data restart (“GDDR”) systems. Specifically, the teachings herein ensure a particular GDDR instance does not react to messages issued from address spaces outside of its affinity group. We use the term message “affinity group” to mean the combination of a particular GDDR instance and its set of Mainframe Enablers started tasks. By ensuring that the particular GDDR instance does not react to messages intended for recipients outside of its affinity group, we improve computer functionality and efficiency by facilitating further partitioning of the logical partition. Once the logical partition is further partitioned into additional address spaces, it is possible to run Mainframe Enablers and/or additional GDDR instances independent of the particular GDDR instance of concern.