Appendix 5: Test Plan Example - Business Continuity and HIPAA Business Continuity Management in the Health Care Environment [Electronic resources] نسخه متنی

Appendix 5: Test Plan Example

I TEST CLASSIFICATION

A. PRODUCTION PROCESSING ENVIRONMENT BACKUP SITE

This exercise is intended to test The Healthcare Organization's (TC)'s ability to recover the fundamental Operating System/Applications and re-establish the production environment for ABC Data Center in the backup center in Compterville, Nevada.

The ABC Data Center is comprised of:

10 Production Stratus 310, 320, 330 type CPU's;

A Data General MV60000 CPU for back-end processing;

Dedicated telecommunications links for Frame Relay, Deluxer and dial in access.

To support this environment for Disaster Recovery, TC has developed it is own internal hardware infrastructure in Compterville, Nevada. This infrastructure consists of:

10 Stratus CPU's

A Data General MV60000 that performs back-end processing;

Dedicated telecommunications links for Deluxer and dial in access.

This backup hardware in Compterville, Nevada is dedicated to the recovery of these platforms in the event of a disaster in the ABC Data Center. This Disaster Recovery hardware is located in The Healthcare organization's Compterville Data Center. Built into this data center is full connectivity to all of the ABC customers.

The recovery is structured so that both platforms can be recovered within 4 hours in Compterville. Both platforms (Stratus and Data General) are powered up with operating system running, system/application software, and applications data recovered. The Merchant master files and application software on these platforms are very stagnant, and as a result, TC has a process in place, which applies updates to these files on a weekly basis. TC ships backups of this data and software from ABC to Compterville overnight on a weekly basis and by transmitting files directly to Compterville. These tapes are then applied to the Stratus and Data General systems that night.

The testing itself will be done from the Compterville, Nevada Data Center. TC's Disaster Recovery Team will facilitate the test. The analyst will also be monitoring the test to ensure that procedures are being followed and any exceptions being noted. There will be sufficient System Administrators and Operations staff on-site to conduct the test. Applications support will be provided by the production applications support staff in the respective locations. Connectivity for this support will be done with its current LAN infrastructure.

TEST DATES AND TIMES

The test dates for the exercise are April 22, 20xx at 04:00 EDT through April 22, 20xx at 06:00 EDT. The assumed disaster date will be April 22, 20xx. The test will be 27 contiguous hours in duration. The date set on the CPU at the test will be April 22, 20xx, and the time will be "wall clock time CDT." Due to the duration of the test, TC will designate specific staff who will occupy the multiple shifts required to complete it. Attached to this document is a copy of the shift schedule. A designated TC Test Team will conduct the test.

TEST LOCATION AND HARDWARE

Again, the Disaster Recovery hardware in Compterville, Nevada mimics the production environment in ABC, Washington. This equipment was purchased / leased for the purpose of backup for the ABC Data Center.

To gain an understanding of how the data was moved from ABC to Compterville, one must understand the production environment. The Production Stratus CPUs in ABC are setup in a mirrored disk environment.

Each system has a production and a back up (or mirrored) disk. The DR systems in Compterville were developed by first performing a logical then physical split of the production/back up disk in ABC. This was done by performing the following:

The disks purchased for Compterville were shipped into ABC.

The backup mirrored disks in ABC were removed and production ran from the single set of disks.

The new disks from Compterville were then inserted into the ABC backup disk slots.

The production data disks were then copied to the mirrored disk. This took anywhere from 5 minutes to 1.5 hours per disk.

The original backup mirrored disks which were pulled from the production Stratus CPU, were shipped to Compterville.

Once the disks arrived in Compterville, they were inserted in to the respective Stratus CPU's as the primary disk.

In Compterville, a process was then initiated to copy the production disk to the backup mirrored disk.

A process of clearing both the CIF data base on the Stratus and the GDB data base on the Data General is performed. Once this is completed, both the production and mirrored disk are synchronized. The baseline systems are now developed and the systems are available for DR testing or recovery.

Weekly backups are taken on the Data General and Stratus processors in ABC and shipped to Compterville where they are applied to the DR systems. Weekly back ups are sufficient as the information located on the databases is relatively stagnant. This synchronization takes approximately 6 hours.

TEST LOCATION PHONE NUMBERS:

Compterville Data Center for Stratus: 999-555-4262

Compterville Data Center for Data General: 999-555-7325

ASSUMPTIONS

No live transactions will be run through the Disaster Recovery test. Only test transactions will be used for the test

The system is functional and the plan is written as if it were a real disaster with the exception of providing telecommunications connectivity to all of the banks and users.

Telecommunications connectivity via TNS will occur to enter the test transactions as if a merchant were entering the transactions. All eight production cut-offs will be run at their normal timeframes. All reports and microfiche will be produced but not sent out to users. A Help Desk representative will be performing the online portion of the test. Since the Stratus and Data General CPU's do not support an automated job scheduler, all batch processes will be run manually as they do today in production. Testing on the Stratus CPU's will be conducted solely from the mirrored disk. This will preserve the baseline system on the production disk in case of a true disaster in ABC. This does not affect the outcome of the test. That data was copied disk-to-disk as part of the building of the CPUs in Compterville. The host would then be kept up to date with merchant data via weekly updates copied to tape from ABC.