RDF System Management Manual for J-series and H-series RVUs (RDF 1.10)

The next examples of BACKUP and RESTORE commands show how to copy all files from the
primary system volumes $DATA01, $DATA02, $DATA03, and $DATA04 to the magnetic tape
device named $TAPE and how to restore these files to volumes of the same name on the backup
system. You must include the AUDITED parameter in both the BACKUP and RESTORE commands.
BACKUP $TAPE,($DATA01.*.*,$DATA02.*.*,$DATA03.*.*,
$DATA04.*.*), AUDITED
RESTORE $TAPE,($DATA01.*.*,$DATA02.*.*,$DATA03.*.*, $DATA04.*.*), AUDITED
Synchronizing Databases With FUP
You can use the FUP DUP command to copy Enscribe database files from the primary system to
the backup system. If you use FUP DUP, the “FUP ALTER filename , NO AUDIT” command is
performed implicitly for each backup file that corresponds to a primary file protected by RDF. You
will therefore need to turn the audit flags back on for all the data volumes on the backup system
after the FUP DUP operation is complete.
NOTE: For this copy operation to work correctly, do not specify the SAVEALL parameter in the
FUP DUP command.
Synchronizing Partitioned Files
When synchronizing partitioned files, you must consider one major difference between NonStop
SQL/MP tables and Enscribe files: a NonStop SQL/MP catalog has a description of all indexes
of a table and partitions of a partitioned table, but a partitioned Enscribe file has no associated
catalog.
To ensure the consistency of a NonStop SQL/MP catalog, you must copy all partitions of a NonStop
SQL/MP table and its dependent indexes at one time rather than on a partition basis. You can
use either the SQLCI DUP command or the BACKUP and RESTORE utilities to copy the partitions.
For an Enscribe file, you can use the FUP DUP command or the BACKUP and RESTORE utilities to
copy the individual indexes and partitions. Then use FUP ALTER to incorporate the other partitions
and any alternate indexes into the primary partition.
If the volume names for partitions on the backup system are different from the volume names on
the primary system, you need to change the volume references for those partitions.
Backing Up Application Programs and Files
To enable the backup system to take over in the event of a primary system failure, you need to put
usable copies of all program files, OBEY command files, and other files your applications use on
the backup system. You can do this by using the NonStop Autosync product. After copying these
files, you might need to change names to reflect the backup system’s naming conventions, and
you might need to recompile some programs.
The following practices are recommended:
• SQL compile all NonStop SQL/MP programs after moving them to the backup system. A static
recompilation reduces the applications’ startup costs after an RDF takeover operation.
Alternatively, you can use the late binding feature. To do this, the SIMILARITY CHECK attribute
for all referenced tables and protection views must be enabled and the program compiled
with the CHECK INOPERABLE PLANS parameter.
• Use DEFINEs for all NonStop SQL/MP objects where possible; this simplifies the commands
for your OBEY command files and the commands for your NonStop SQL/MP DDL operations.
Preparing the Backup System 67