RDF System Management Manual

Online Database Synchronization
HP NonStop RDF System Management Manual—524388-003
7-9
Considerations When Synchronizing Entire
Databases
regarding differences in table and catalog versions. Consult the HP NonStop
SQL/MP Version Management Guide.
•
You can create and load the duplicate tables on the primary system and then move
them to the backup system using SQLCI DUP commands or BACKUP/RESTORE
and tapes. In either case, however, the tables must be registered in a catalog on
the backup system. Again, you must be knowledgeable about issues regarding
differences in table and catalog versions. Consult the HP NonStop SQL/MP
Version Management Guide.
Moving Duplicated Tables and Files to the Backup System
If you created the duplicate files and tables directly on the backup system and loaded
them from the primary system, you can start the RDF updaters without any further
considerations.
If you created the duplicate files and tables on the primary system and then moved
them over to the backup system, however, you must be aware of the following:
•
If you move duplicate partitioned Enscribe files whose volume mappings differ
between the primary and backup systems, you must use a FUP ALTER command
to alter the file labels of the duplicate files on the backup system so they reflect the
correct volume mapping of the various partitions on the backup system.
For example, suppose you have a partitioned Enscribe file on the primary system
whose primary partition is on $DATA1 and secondary partition is on $DATA2. If,
on the backup system, the primary partition is on $DATA1 but the secondary
partition is on $DATA3, you must change the volume name in the file label of the
duplicate secondary partition from $DATA2 to $DATA3 as follows:
FUP ALTER $DATA1.subvol.file, PART (1,$DATA3)
•
If you move duplicate Enscribe alternate key files, you must alter the system name
in the file label of the duplicate file or table to specify the backup system.
For example, if you moved a duplicate Enscribe alternate key file named
ALTF0100 associated with the file PART0100, you must change the system name
in the file label of the duplicate alternate key file to that of the backup system as
follows:
FUP ALTER $DATA1.TEST.PART0100
ALTFILE (0,\backup.$DATA.TEST.ALTF0100)
•
If you use the SQLCI DUP command to move duplicate partitioned NonStop
SQL/MP tables, you must use the MAP NAMES option to specify the backup
system name.
•
If you use the SQLCI DUP command to move NonStop SQL/MP tables with index
tables, you must use the MAP NAMES option to specify the backup system name.