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

Preparing the RDF Environment
HP NonStop RDF/IMP and IMPX System Management Manual—524388-001
2-7
Preparing Databases for RDF Protection
Audited Backup Database Files
The backup system must have copies of all files that RDF protects. For a successful
takeover of business operations in the event of a primary system failure, the backup
system should also have copies of all the files needed by the primary system
applications (including alternate key files and index files, for example). For each
audited data file that resides on the primary protected volume, a corresponding audited
file must exist on a volume configured for an updater process on the backup system.
The volume name on the backup can differ from that on the primary, but the subvolume
names must be identical on both systems. For example, if volume $B on the backup
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 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.
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.
Views on the Backup System
If an application uses any NonStop SQL shorthand or protection views on a volume
protected by RDF, audit data for transactions on the views refers only to the underlying
tables and not to the views. Views and their underlying base tables must be present on
the backup system after a takeover operation so that applications can continue without
interruption.
All base tables underlying the views must also reside on volumes protected by RDF on
the primary system.
Partitioned Tables and Files
If any partition of a partitioned NonStop SQL table or Enscribe file exists on a volume
protected by RDF, then all partitions for that file need to be on volumes protected by
RDF. All partitions of a file protected by RDF must be on the same system.