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

Installing and Configuring RDF

Compaq NonStop™ RDF/IMP and IMPX System Management Manual—522204-001

3-2

Preparing the Tables and Files

Now prepare your tables and files.

Separating SQL/MP Tables

It is recommended that you avoid registering SQL/MP 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 SQL/MP 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 SQL/MP 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 SQL/MP 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.

If the names of any volumes or devices the applications might use on the backup system

are different from the names on the primary system, you must also change any

references to these volumes or devices.

It is strongly recommended that the backup system have one volume for every volume

protected by RDF on the primary system and that each backup volume have the same

name as the corresponding primary volume. If the backup volume names are not

identical to the primary volume names, then you need to update every backup

partitioned file and every backup file that has alternate keys so that each points to the

right volume name.

RDF requires that TMF be started on the backup system, the database on the backup

system reside on configured data volumes, the data volumes be physically up, and the

files and tables be audited. BEGINTRANS should not be disabled.