Tier 4 - active secondary site

Tier 4 provides a more advanced level of disaster recovery. You will lose data in the disaster, but only a few minutes- or hours-worth.

You must assess whether the loss of data will prevent your company from continuing in business, and what the cost of lost data will be.

Figure 1 summarizes the tier 4 solution.
Figure 1. Disaster recovery tier 4: active secondary site
This diagram illustrates two fully operational data centers, each a complete replica of the other. Each site backs up the other, and recovery relies on the continuous transmission of data over ESCON and VTAM links. Recovery is indicated as taking from minutes up to hours. The other points made by this diagram are discussed in the text.

Tier 4 closes the gap between the point-in-time backups and current online processing recovery. Under a tier 4 recovery plan, site one acts as a backup to site two, and site two acts as a backup to site one.

Tier 4 duplicates the vital data of each system at the other's site. You must transmit image copies of data to the alternate site on a regular basis. You must also transmit CICS® system logs and forward recovery logs, after they have been archived. Similarly, you must transmit logs for IMS™ and DB2® subsystems. Your recovery action is to perform a forward recovery of the data at the alternate site. This allows recovery up to the point of the latest closed log for each subsystem.

You must also copy to the alternate site other vital data that is necessary to run your system. For example, you must copy your load libraries and JCL. You can do this on a regular basis, or when the libraries and JCL change.

The benefits of tier 4 are:
  • Recovery is fast, with the required hardware and software already in place at the secondary site.
  • Recovery is more complete than in the tier 1 to 3 solutions. You can recover all data to the end of the log for each of your data subsystems.
  • Recovery risk is low, because you can easily test your procedures.
The drawbacks are:
  • Recovery is more difficult to manage, as you have to ensure that all the logs and copies are transmitted to the other system.
  • This solution introduces synchronization problems. Logs for different data subsystems are transmitted at different times. When you complete your recovery at the secondary site, you could find that your VSAM data is complete up to 30 minutes before the disaster, whereas your DB2 data is complete up to 15 minutes before the disaster. If your data must be synchronized, you may have to develop further procedures to resynchronize data in different subsystems.
  • Cost is higher than for the tier 1 to 3 solutions, because you need dedicated hardware, software, and communication links.


dfht2ie.html | Timestamp icon Last updated: Sunday, 4 June 2017