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


Chapter 8 Recovery Procedures : Introduction to TIBCO Object Service Broker Recovery

Introduction to TIBCO Object Service Broker Recovery
Purpose of TIBCO Object Service Broker Recovery
The recovery procedures assure the restoration of all data resident within one specific Pagestore. They do not deal with data external to the Pagestore, such as data residing in external database management systems and remote TIBCO Object Service Broker nodes that participated in database units of work coordinated by this specific TIBCO Object Service Broker system. You must administer their recovery through their own respective database management systems.
A recovery of the system is essentially a replacement of all or part of the current system with a backup copy. You normally perform a recovery procedure only when the current system is corrupted (data was inadvertently altered or destroyed) or when there has been a media failure.
When restoring data that participated in units of work traversing TIBCO Object Service Broker and external databases, it is your responsibility to ensure the integrity of the entire unit of work. That is, if you recover a TIBCO Object Service Broker table, page data set, or segment, you must consider the consequences on the entire unit of work and perform related recovery, if necessary, on the other participating external databases.
Validating the Backup
We recommend that you run the S6BBRPTR (Batch Pointer Check) utility against every new backup to ensure the integrity of the backup. If you did not run the S6BBRPTR utility against the backup you plan to use for recovery, you should do so before proceeding.
See Also
TIBCO Object Service Broker for z/OS Utilities for more information on S6BBRPTR.
Deciding How Much To Restore
The first step in any recovery process is to determine the nature and scope of the damage from which you need to recover. There are several possibilities:
In this case, recover these tables from your most recent backup using the S6BBRULA (Recover TDS Table From Archive) utility. For information about the S6BBRULA utility, refer to TIBCO Object Service Broker for z/OS Utilities.
Restore all page data sets on that device to the level they were before the hardware failure. For information about performing a partial system recovery, refer to Restoring A Segment.
You can either restore your entire system to its state just before the occurrence of the program error or restore your system to a specific time by the use of the S6BTLSRP (Select Recovery Pages) utility. Keep in mind that you must use sort exit S6BSPU35 in SPINMRG and BKUPCON instead of S6BSPX35.
For information about a full system recovery, refer to Full Recovery Procedure.
Since there is no damage to the Pagestore in this case, no Pagestore recovery is required. However, you must repair any damaged system data sets before you resume normal application processing.
When restoring to a point in time with database products, you must ensure that all data within the database remains synchronized. If a table, page data set, or segment is restored to a point in time, you must consider the consequences of this on the rest of your system.
Recovery Preparation
Before doing system recovery work, decide on the appropriate recovery level according to what you need and what is possible. Depending on this decision, if necessary, perform some pre-recovery procedures. Your data restoration options include the following:
Option 1: Recover only the data included in your most recent backup copy
If the backup was taken three days ago, at the end of the restore process, the entire TIBCO Object Service Broker system is exactly as it was three days ago. None of the changes made to the system since the backup was taken are reflected. With this option, your latest backup copy is usable as it is. No pre-recovery steps are necessary.
Option 2: Recover data including your most recent backup copy and the latest unmerged SPINOUT data sets
Run BKUPCON, which picks up all SPINOUT generations and merges them into the backup data sets. You can now use the updated backup copy.
Option 3: Recover data including your most recent backup copy, the latest unmerged SPINOUT data sets, and any unspun journal data
Complete the following steps:
1.
The easiest way to achieve this is to bring up the Data Object Broker to resolve any units of work that are pending in its recovery files.
2.
Use the SPINSUBMIT=I command. This forces an immediate spin to clean out the current active journal. For more information on the SPINSUBMIT command, refer to TIBCO Object Service Broker for z/OS Installing and Operating.
3.
Run BKUPCON.
BKUPCON picks up all SPINOUT generations and merges them into the backup data sets.
You can now use the updated backup copy.
Option 4: Restore to a specific time using the S6BTLSRP (Select Recovery Pages) utility
You can use the S6BTLSRP utility to identify a specific time to which you want to recover. It then selects the pages that are time-stamped the closest to this date and time and creates a file from which you can restore data. Refer to Point in Time Recovery and TIBCO Object Service Broker for z/OS Utilities for information on using the S6BTLSRP utility.
Recovery Overview
The basic recovery tasks are as follows:
1.
2.
For example, you can do this using the S6BTLSRP (Select Recovery Pages) utility or by retrieving an archived file.
3.
a.
b.
c.
4.
5.

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