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-8
Considerations When Synchronizing Entire
Databases
Different SQL/MP Product Versions
If you have different versions of the NonStop SQL/MP product on your primary and
backup systems, refer to the HP NonStop SQL/MP Version Management Guide for
information about what you can do and how to do it.
Three of the more common issues are as follows:
•
If your primary system has a higher version of the NonStop SQL/MP product than
the backup system, then the tables on the primary system must not make use of
features not supported by the lower product version. Failure to comply with this
will result in errors when attempting to create the duplicate tables.
•
You can create the duplicate tables on the backup system and then load them over
the network from the primary system, but you must be knowledgeable about issues
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)