RDF/IMP, IMPX, and ZLT System Management Manual

Online Database Synchronization
HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002
7-3
Synchronizing Entire Databases Online
detailed information, see “Phases of Online Database Synchronization” later in this
section.
7. If the duplicate tables and files were created on the primary system in step 4, use
BACKUP/RESTORE or FUP DUP operations to copy them to the backup system.
For ENSCRIBE files with alternate key files, after restoring the files to the backup
system, if the name of the alternate key file is in network form, then you must
manually alter the system name of the alternate key file in the file label, replacing
the name of the primary system with that of the backup.
For example, suppose that on the primary system (\PRIMARY) you have a file
named $DATA.TEST.PART0100 with an alternate key file named ALTF0100.
After restoring both files to the backup system (\BACKUP), you must then use a
FUP ALTER command to alter the file label of PART0100 to point to the alternate
key file on the backup system.
FUP ALTER $DATA.TEST.PART0100,
ALTFILE ( 0, \BACKUP.$DATA.TEST.ALTF0100 )
Note that the above command does not pertain to NonStop SQL/MP indexes
because their labels are automatically corrected by the MAP NAMES option of the
RESTORE utility.
The same issue pertains to Enscribe partitioned files. If the primary partition
references secondary partitions that include the primary system name, you must
alter the primary system name to that of the backup system.
If you have an RDF network for replicating network transactions, then you will need
to alter the partition names to reference the correct names of the backup systems
where the partitions are located.
8. When your loaded database is on the backup system and the extractor has logged
the message indicating it has completed its role in the online synchronization
operation, issue the RDFCOM START UPDATE command on the primary system.
Note. If your updaters are protecting data volumes that are all configured to the master
audit trail (MAT), you can start the updaters as soon as the duplicate database is on the
backup system and the extractor has issued the RDF event 782. If, however, your
updaters are also protecting data volumes that are configured to one or more auxiliary
audit trails, you must also wait for all of the auxiliary extractors to report 0:00 RTD times
before starting the updaters.