The IMS, Db2, and VSAM processes
This topic describes the processes you would perform to add VSAM to the overall IMS and Db2 disaster recovery plan.
At the local site
Perform the following steps at the local site. The first five steps are VSAM-only processes. The sixth and seventh steps are modifications to the existing processes that are required for IMS and Db2 only recovery.
Step | Action | Description |
|---|---|---|
1 | Perform the RUV backup process. | The RUV backup process creates local and offsite backup stacked tapes and registers them in the RUV repository. Files can be specified individually or by group (using the RUV VSAM Group feature). This process is usually scheduled to run based on processing windows; it might run weekly or daily. |
2 | Perform the RUV archive process. | The RUV archive process extracts recovery data from the system and user logs, formats the data into the RUV archive format, and registers the archives in the RUV repository. This process is usually scheduled to run based on transaction volume; it might run hourly or several times per day. |
3 | Perform the RUV archive accumulation process. | The RUV archive accumulation consolidated process combines the archives from multiple archive processes into a single consolidated archive. This process is performed for the user data and for the unit of work data. If the RUV Batch Journaling feature is being used and logs are available, these logs are included. This process creates local and offsite copies and should be scheduled to complete shortly before the daily shipment to the offsite location. |
4 | Perform the RUV repository backup process. | The RUV repository backup process creates a local copy and an offsite copy of the RUV repository. The repository contains registration information for your files, groups, backups and archives. The offsite copy should be sent to the DR site along with the backups and archives. This process should be scheduled to complete shortly before the daily shipment to the offsite location. |
5 | Perform the RUV pull list process. | The RUV pull list process runs a Backup report for all backups and archives in the Staging location, and then it changes the location for those backups and archives to the Offsite location. The files that are listed in these reports should be shipped to the offsite location. This process should be scheduled to complete shortly before the daily shipment to the offsite location. |
6 | Generate the PIT using the REXX EXEC. | Run the RECOV.REXX script to extract the recovery point from the IMS RECON report, format the recovery point into the appropriate Db2 and VSAM recovery formats, and update Db2 and VSAM recovery JCL. This process should be scheduled to complete shortly before the daily shipment to the offsite location. |
7 | Backup Recovery JCL Library | Take a backup of the recovery JCL PDS file and ship to the offsite location along with the IMS, Db2 and VSAM backups and archives/logs. |
The following figure shows the IMS, Db2, and VSAM components of the coordinated recovery process at the local site:
At the remote site
When a disaster is declared (or simulated), perform the following steps to recover the VSAM files:
Step | Action | Description |
|---|---|---|
1 | Restore recovery JCL. | Restore the recovery JCL that was created in Step 6 of the local site process. |
2 | Catalog data sets. | Catalog the backups, archives, and repository backup that were created in Steps 2, 3, and 4 of the local site process. Technically, it is not required for these data sets to be cataloged. If they are not cataloged, RUV calls for them by VOLSER during recovery. |
3 | Start the RUV subsystem. | Start the RUV subsystem. |
4 | Restore the RUV repository. | Restore the RUV repository by using the RUVREPRS program. |
5 | Inactivate local files and activate offsite files. | Run the RUVTOGL program to inactivate local backups and archives and activate the offsite files. |
The following figure shows the IMS, Db2, and VSAM components of the coordinated recovery process at the remote site:
