Publication Date: 2010-Nov-05
The IP.com Prior Art Database
Most Business Continuity and/or Disaster Recovery solutions for data centers require a sophisticated solution which combines software and hardware elements, to continuously run business applications, switching to a second or third data center in the case of a failure at the primary data center. Given a set of volumes or Disk Subsystems, a combination of data mirroring and automation techniques offers a way to have a consistent copy of the data in a remote site, for Business Continuity and Disaster Recovery purposes. However, human intervention is currently required to identify the volumes to be mirrored, and to maintain the mirroring configuration. This paper suggests a way to programmatically ensure that the mirroring configuration always mirrors the volumes used in the production site.
Page 01 of 2
A common problem is that if the data configuration at the primary site is changed, there is no mechanism to verify that the change in data configuration is reflected in the replication of DASD between the primary and other data centers. If the DASD replication policy does not take account of changes to the data configuration at the primary site, any disaster recovery policy may ultimately fail, or business-critical data will be lost after the recovery.
This paper proposes a method to check continuously, or as often as is required, that all data on-line used by all applications on all systems is included in the data replication performed for Business Continuity and/or Disaster Recovery. This will ensure that if a disaster occurs, or there is a planned site swap event, you can be confident of business continuity, or of being able to restart with no lost data.
A tool can run in a Parallel Sysplex GDPS/PPRC environment, the tool performing the following steps:
1) Obtain the list of all z/OS on-line volume using a system macro service called UCBSCAN
2) Obtain the list of all mirrored volumes managed by GDPS/PPRC using a GDPS macro service called VPCEQURY
3) Compare the two lists and check that any volumes not included in data replication are in an exclude list compiled by the user
4) If any volume that is not in the exclude list is found on-line, but is not in the GDPS configuration, an alert is issued to the system itself and to the Master focal point syste...