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

Preparing the RDF Environment
Compaq NonStop™ RDF/IMP and IMPX System Management Manual—522204-001
2-6
Preparing Databases for RDF Protection
If you must unpin one or more audit trail files, you can do so by issuing an
UNPINAUDIT command. Later, when RDF is restarted, you can restore the
necessary audit trail files from tape.
2. TM/MP 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 SQL/MP views on the backup systems
•
Placement of partitioned Enscribe files and 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 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.
Views on the Backup System
If an application uses any SQL/MP 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.
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.