RDF/IMP and IMPX System Management Manual (RDF 1.4+)
Installing and Configuring RDF
HP NonStop RDF/IMP and IMPX System Management Manual—524388-001
3-2
Stopping the Software
Stopping the Software
After you stop all applications protected by TMF, stop TMF itself by issuing a STOP 
TMF command through the TMFCOM interactive interface. (You only need to stop your 
applications and TMF if you are going to use the TIMESTAMP parameter of the INIT 
RDF command or if you are going to omit the timestamp parameter in all forms). For 
information about issuing this and other TMFCOM commands, see the HP NonStop 
TMF Reference Manual.
Preparing the Tables and Files
Now prepare your tables and files.
Separating NonStop SQL Tables
It is recommended that you avoid registering NonStop SQL tables protected by RDF in 
the same catalogs as tables that are not protected by RDF. Separating protected tables 
from unprotected ones simplifies the comparison of primary system catalogs with 
backup system catalogs.
Compressing Audit Data for Tables and Files 
Although not required by RDF, using the AUDITCOMPRESS file attribute will enhance 
RDF performance. TMF compresses the audit data generated for NonStop SQL tables 
and Enscribe files for which AUDITCOMPRESS is on. For applications involving 
updates of only a few bytes to large existing rows or records, this audit compression 
greatly reduces both the amount of audit information the extractor must read and send 
to the receiver and the corresponding amount of RDF traffic on the communications 
line.
For NonStop SQL tables and indexes, AUDITCOMPRESS is the default. If the value 
has been changed to NO AUDITCOMPRESS for a table, you can use an ALTER 
TABLE command, entered through the NonStop SQL Conversational Interface 
(SQLCI), to reset the default value:
ALTER TABLE table-name AUDITCOMPRESS;
To set the AUDITCOMPRESS attribute for an Enscribe file, use the File Utility Program 
(FUP) to enter an ALTER command:
FUP ALTER filename, AUDITCOMPRESS
Preparing the Backup System
Before starting RDF, you need to copy every database, program, and file that the 
primary system applications use to the backup system so that the backup system can 
take over in the event of a primary system failure. In the backup copies, you need to 
change any occurrences of the primary system name to the backup system name. 
RDF replicates the database; you should use the HP NonStop Autosync product to 










