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

Online Database Synchronization
Compaq NonStop™ RDF/IMP and IMPX System Management Manual—522204-001
7-2
Database Considerations When Synchronizing
Entire Databases
5. When the load or backup operations are done, issue the RDFCOM STOP SYNCH
command on the primary system. This command issues a message to the extractor.
When the extractor completes its role in the online synchronization operation, it
resumes its normal operation. For more detailed information, see “Phases of Online
Database Synchronization” later in this section.
6. 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.
Note that for SQL tables you must manually create the catalogs on the backup
system.
If you used the BACKUP utility to save entry-sequenced tables and files, and
unstructured Enscribe files, in step 4, use the RESTORE utility with the OPEN and
AUDITED options to restore them on the backup system.
For ENSCRIBE files with alternate key files, after restoring the files to the backup
system you must manually alter the the system name of the alternate key file in the
file label. 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 SQL indexes because their labels
are automatically corrected by the MAP NAMES option of the RESTORE utility.
7. After all the duplicate tables and files have been copied to the backup system and
the extractor has logged the message indicating it has completed its role in the
online synchronization operation, issue an RDFCOM START UPDATE command
on the primary system.
Database Considerations When Synchronizing Entire Databases
The database considerations for online synchronization fall into four categories:
1. SYNCHDBTIME issues
2. CREATE/LOAD issues for SQL tables and Enscribe files
3. Different versions of SQL/MP on the primary and backup systems
4. Moving the duplicated tables and files to the backup system
Note. If you are replicating only the master audit trail (MAT), you may start the updaters as
soon as the extractor issues its 782 event message. If you are also replicating one or
more auxiliary audit trails, however, you must also wait for all of the auxiliary extractors to
report 0:00 RTD times before starting the updaters.