Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 8 Recovery Procedures : Restoring Individual Page Data Sets

Restoring Individual Page Data Sets
The following sections outline the steps required to recover individual page data sets in a number of different recovery scenarios. The steps you follow depend upon your overall approach to data recovery.
Recovering Page Data Sets
To restore the data:
1.
2.
3.
4.
If updates are pending (via the redolog and cache data sets), the Data Object Broker automatically applies the updates as part of initialization.
Restoring a Page Data Set Using a Continuous Backup
To restore a page data set that is backed up using the continuous backup method, you must restore the data set from the most recent backup. You must then apply all outstanding journaled page images from the time of the backup to the point of failure. The job flow is as follows:
1.
Flush all pending journal update information from the Data Object Broker into the continuous backup process as shown below:
2.
3.
You must always run the S6BBRPTR (Batch Pointer Check) utility, against newly created data sets to ensure their integrity.
4.
Restoring a Page Data Set with an External DASD Backup
To restore page data sets by using an external DASD backup utility:
1.
2.
 
Recovery to a Previous Full External Backup
External DASD backup utilities can be used to perform backups of the Pagestore provided records are not relocated within VSAM control intervals. All segments should be offline when the backups are taken and no updates should be pending.
With the Data Object Broker down, a typical recovery procedure would be as follows:
1.
2.
Clear residual update information in all Data Object Broker operational data sets (the redolog, caches, and journals) as shown below:
3.
This decision depends on whether the external database server or the peer TIBCO Object Service Broker is also restored. You can abort in-doubt transactions from the S6BTLADM (Administration Menu) utility.
4.
Refresh your continuous backup, if you are using it, from a complete backup taken after the restore completed. This stops any invalid page images created after the point of full backup but prior to the restore process being completed, from being circulated within the continuous backup process.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved