RDF/IMP, IMPX, and ZLT System Management Manual

Preparing the RDF Environment
HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002
2-7
Preparing Databases for RDF Protection
2. TMF includes the functional capability of audit overflow volumes. You should
always configure them with at least one overflow audit volume.
3. If you are required to do a takeover, it is recommended that you take online dumps
of the backup database before restarting the applications that will use it.
Preparing Databases for RDF Protection
When preparing databases on the primary system for RDF protection, you must
consider the following system aspects:
•
Copies of files for the backup database
•
Copies of NonStop SQL/MP views on the backup systems
•
Placement of partitioned Enscribe files and NonStop SQL/MP tables
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/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.
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.
Caution. Although RDF no longer requires you to configure TMF with a dump process that
dumps to tape, you should nevertheless configure TMF for dumping to tape if you want to
achieve full TMF protection for your primary database. In addition, if the RDF extractor is
running behind and you stop the TMF and RDF subsystems before RDF has caught up to the
TMF shutdown point, when you subsequently restart TMF, the TMP might roll over the files
before the RDF extractor can process them.