Blog

The Problem

Most mainframe sites create regular backups of the data and programs on their mainframe. The rationale is that, if the mainframe becomes unavailable for any reason, these tapes can be used to load up an alternate machine and continue business. So far so good.
Unfortunately many of these same sites never fully test the backup tapes they create for a variety of reasons (not enough mainframe time available, full test would disrupt operations, etc). So they are taking the functionality of the backup tapes as a given once they are created. This is a risky approach since the failure of any one of the tapes in a series could potentially wipe out your ability to restore the entire series. Of course, you could revert to an earlier set of tapes assuming you have them, but now you have a patchwork image that has some files more up-to-date than others.

The TurboHercules Approach

This problem can be solved by using TurboHercules as your disaster recovery/business continuity solution.

The Ancillary Mainframe

TurboHercules provides an alternate mainframe that you can run on in the event that your regular mainframe becomes inoperable for any reason (fire, flood, electrical outage, etc). This alternate mainframe has all of the functionality of the mainframe it is configured to backup. All that is needed is an up-to-date copy of the information on the regular mainframe. Once loaded, the TurboHercules alternate can be powered up and IPL’ed within minutes to provide business continuity.

Keeping Your Ancillary Mainframe Up-To-Date

Keeping your TurboHercules mainframe up-to-date is a straightforward process.

0. On your regular mainframe perform your backups to tape or virtual tape in the usual manner. We will be using an alternate package of software on the TurboHercules machine to verify the backups and not your mainframe itself. Therefore, you have the ability to perform these backups on a much more regular basis, even hourly, if desired.
0. Once the backup tapes or tape images are complete, you move them to the TurboHercules system where they will be verified and loaded into the emulated disk images. Please note that during the entire backup/verify/restore process, we will not be running a copy of your mainframe OS. All of the work is carried out by a series of standalone applications running on the TurboHercules system. In effect, the TurboHercules system is configured as a cold backup to your mainframe.
0. Once the images are loaded into the emulated disks on your TurboHercules system, it is ready for operation. If there is a failure with your regular mainframe, the TurboHercules system can be IPLed and brought on-line with data that is as up-to-date as your last backup.
0. As mentioned earlier, the backup/verification/restoration process can easily be automated, especially if you are using a virtual tape library as your mainframe backup destination.

The Failover

When the “event” occurs and your mainframe is rendered inoperable, you move your communications lines to the TurboHercules system as planned, turn on and IPL the TurboHercules machine from its virtual DASD devices and continue operations. A properly scripted failover could easily be performed from cold in less than 5-10 minutes depending on the people running the exercise.

Going Back

Once the regular mainframe or mainframe environment has been repaired you will need to reverse the process detailed above. At a convenient time you perform a complete backup of the TurboHercules system to tape or virtual tape. You then move the communications lines back to the regular mainframe, IPL from the tape images, restore the machine and go back to operations as usual.

by Tom Lehmann, Co-founder of TurboHercules