RDF System Management Manual for H-Series RVUs (RDF 1.8)

Table 2-2 Software Requirements
RequirementSoftware
The RDF/IMP, IMPX, and ZLT products protect only files
on the primary system that are audited by the TMF
subsystem.
Files
The RDF/IMPX and ZLT products support the use of TMF
auxiliary audit trails on the primary system (volumes
protected by RDF can store audit data in either the MAT
or an auxiliary audit trail). The backup database files are
audited, and therefore must also reside on TMF data
volumes.
Auditing
The RDF/IMP, IMPX, and ZLT products use Expand
software to connect the primary system to the backup
system.
Communications
On the primary and backup systems, the installed release
version update (RVU) of the operating system must be
supported.
Operating System
On both the primary and backup systems, the installed
RVU of the TMF subsystem must be compatible with the
installed RVU of the operating system.
TMF Subsystem
On both the primary and backup systems, the installed
RVU of the NonStop SQL/MP or NonStop SQL/MX
product must be compatible with the installed RVU of
the operating system.
NonStop SQL/MP and NonStop SQL/MX
CAUTION: The block size of a file or table on the backup system should be identical to the size
on the primary system. If the block sizes differ, you risk corrupting your backup database.
Mixed-Product Installation
RDF/IMP, IMPX, and ZLT are not compatible with RDF, RDF/MP, and RDF/MPX. Therefore, if
you already have any of those earlier RDF products installed, you cannot install RDF/IMP, IMPX,
or ZLT on just one of your systems; you must install it on both the primary and backup systems.
The primary and backup systems need not have the same operating system release version
update (RVU) installed.
Configuring TMF for RDF Operations
TMF attempts to purge old audit-trail files each time it rolls over to a new one. The purge is
performed only if the audit-trail file is not pinned on behalf of RDF.
RDF automatically pins audit-trail files. The only ways TMF can purge an old audit-trail file that
is still required by RDF are:
• If you issue an UNPINAUDIT command while RDF is not running.
• If you stop TMF and restart it without restarting RDF. TMF does not retain pinning on behalf
of RDF when TMF is stopped and then restarted. If you must stop and restart TMF, be sure
to restart RDF before you restart your applications. This causes RDF to re-pin the audit-trail
files it needs, and thereby prevents TMF from purging the files before RDF has finished
processing them.
If you issue an UNPINAUDIT command while audit dumping is disabled and TMF purges an
audit trail that has not yet been processed by RDF, you will have to reinitialize RDF and
resynchronize the databases. If you have configured TMF for audit dumping, however, you will
not need to reinitialize RDF or resynchronize the databases (the extractor will wait until the
needed audit trail is restored and then resumes).
66 Preparing the RDF Environment