RDF/IMP and IMPX System Management Manual (RDF 1.4+)

Online Database Synchronization
HP NonStop RDF/IMP and IMPX System Management Manual—524388-001
7-17
Partial Database Synchronization Issues
Thus, you now have on tape empty partitions for the entire table. Should you ever
lose a volume to a complete media failure, you can install a new disk and then use the
RESTORE utility with the PARTONLY option to recover the missing partition. Note that
because you have backed up a table with the name you need on the backup system,
you can restore any partition that you need to with the PARTONLY option and without
having to use the MAP NAMES option. Once you have restored the empty partition,
you can use the protocol described below to synchronize the affected partition.
Note that there is no recovery for a media failure that wipes out an individual partition
of a partitioned index. If that happens, you will need to drop the index from the
associated table, thereby eliminating all other partitions of the index. Then you must
create a new index.
Key-Sequenced Tables
The most effective means of describing this method is to use an example. Suppose
you have a table named PART whose primary partition is named $DATA.TEST.PART,
that this table has 50 secondary partitions, and you only need to synchronize the
primary partition. The following set of steps presumes you have just added the volume
needing synchronization to the RDF configuration and you are running with update off.
Again, follow the steps for complete database synchronization, although with some
specific modifications. The complete set of steps with modifications are listed below.
1. If RDF is currently running, issue a STOP RDF command on the primary
system.
2. Purge the RDF control subvolume and then issue an INITIALIZE RDF command of
the following form on the primary system:
INITIALIZE RDF, BACKUPSYSTEM \system, SYNCHDBTIME ddmmmyyyy hh:mm
For the timestamp, follow the guidelines for the INITTIME option.
3. Configure RDF and then issue a START RDF, UPDATE OFF command on the
primary system.
4. Create the entire duplicate table on your backup system with a temporary name at
a temporary location (such as \BACKUP.$DATA.DUP.PART).
The alternative is to create the duplicate table on the primary system at a
temporary location (such as \PRIMARY.$DATA.DUP.PART).
If the table whose primary partition needs to be synchronized has indexes, do not
create indexes for the duplicate table.
Note. Because the SQLCI LOAD operation generates new SYSKEY values in the backup
table, key-sequenced tables containing SYSKEYs cannot be synchronized online.