Preparing Software And Database Files For Rdf Operations - HP NonStop RDF J-series RVUs Management Manual

1. Enter a FUP INFO command for the current TMF MAT and record the end-of-file (EOF)
value; for example:
FUP INFO $AUDIT.ZTMFAT.*
CODE
$AUDIT.ZTMFAT
AA000003 134 11292672
2. Enter a FUP INFO command for the current MAT 5 minutes later and record the EOF value;
for example:
FUP INFO $AUDIT.ZTMFAT.*
CODE
$AUDIT.ZTMFAT
AA000003 134 11653120
3. If all the TMF audit data is generated on volumes protected by RDF, subtract the first EOF
value from the second EOF value to obtain the number of bytes generated during the 5-minute
period. Then divide the number of bytes by 300 seconds to determine the amount of audit
data generated in a second; for example:
(11653120-11292672)/300 = 1202 bytes per second
The extractor does not necessarily transmit all audit records associated with a particular
transaction. For example, audit records associated with physical operations is not transmitted.
The reason for this is that the backup database is maintained as a logically identical copy of the
primary database, not as a physically identical copy.
The data communications link should have at least two paths (multi-line Expand). Each path
should go through different communications carrier paths or switches, and each should be able
to transmit the peak data rate. It is often sufficient to have a single Expand path driven out of a
single processor, and the use of Expand-over-Servernet, Expand-over-IP, Expand with ATM, or
Expand with Fast Ethernet provides considerable bandwidth. For RDF environments where
multi-line Expand is absolutely required, see
It is almost impossible to calculate the RDF audit transmission rate from the TMF audit generation
rate alone.
HP has developed a sizing tool that can be used to predict accurately the Expand bandwidth
requirements between the primary and backup systems by simulating the RDF extractor. That
utility reads the TMF audit trails and generates detailed information about TMF audit generation
and RDF audit transmission activity. This information is particularly useful when a single system
supports multiple applications and RDF will only be configured to protect a subset of these
applications. This tool was designed and developed as part of the RDF Professional Service.
Contact your service provider for further details.

Preparing Software and Database Files for RDF Operations

The software requirements for the RDF/IMP, IMPX, and ZLT products appear in
EOF LAST MODIF OWNER RWEP TYPE REC BLOCK
10:05 -1
EOF LAST MODIF OWNER RWEP TYPE REC BLOCK
10:10 -1
Preparing Software and Database Files for RDF Operations
GGGG
GGGG
Chapter 13 (page 291).
Table 2-2.
59