RDF System Management Manual

Preparing the RDF Environment
HP NonStop RDF System Management Manual—524388-003
2-8
Preparing Databases for RDF Protection
system corresponds to volume $A on the primary system, then all files protected by
RDF on volume $A must be present (and in the same subvolumes) on $B.
Section 3 explains how to copy NonStop SQL/MP databases and Enscribe files to the
backup system after stopping both the TMF product and the applications that use that
product on the primary system. That is the time to copy any files the applications need
to the backup system so that the files are identical on both systems before RDF starts
running.
Section 15, NonStop SQL/MX and RDF explains how to copy NonStop SQL/MX
databases to the backup system after stopping both the TMF product and the
applications that use that product on the primary system.
Taking Online Dumps of Backup Database.
You should take online dumps on the backup system. Before doing so, you must
change the UPDATEROPEN parameter from Protected (the default value) to Shared.
When you are done dumping, you should then change the UPDATEROPEN parameter
back to Protected.
Reload of Backup Database.
If you need to reload the the backup database, you must change the UPDATEROPEN
parameter from Protected (the default value) to Shared. When you are done with the
reload, you should then change the UPDATEROPEN parameter back to Protected.
DSM Catalogs and File Code 900
All files that have the file code 900 are replicated by the RDF product. These consist
of DSM Tape Catalog files as well as some related files. In the case of files having the
file code 900, RDF replication of them to the RDF backup system may provide critical
information if you later lose the primary system to a disaster. Note, however, that if you
also have a DSM Tape Catalog and related files that specifically pertain to the backup
system, you must be careful to place the replicated files in a different location on the
backup system. For example, suppose you have a DSM Tape Catalog and related
files on $CAT.DSMCAT on the primary system, and you have a different DSM Tape
Catalog and related files on $CAT.DSMCAT on the backup system that specifically
pertain to the backup system. In that case you must replicate the DSM Tape Catalog
and related files on the primary system to a different location than $CAT.DSMCAT on
the backup system. For example, you might want to replicate $CAT.DSMCAT.* on the
primary system to $DATA.DSMCAT.* on the backup system. In that way replication of
the DSM Tape Catalog and related files from the primary to the backup system does
not affect the DSM Tape Catalog and related files in $CAT.DSMCAT.* on the backup
system.