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-9
Designing Transactions for RDF Protection
Partitioned Files
All partitions of a partitioned Enscribe file or SQL/MP table must reside on volumes
protected by RDF, or none should. Corresponding partitions on each system must have
the same key values.
If you are using RDF to replicate the creation of partitioned files and an RDF takeover
operation occurs in the midst of a set of creations, some partitions might have been
created while others were not, because each partition of a partitioned file is created
independently.
Temporary Disk Files
File creation, modification, and updates are not replicated for audited temporary disk
files. All audit data is filtered out by the extractor on the primary system for file names
of the form $volume.#nnnnnnn.
A file name that begins with # (pound sign) indicates a temporary disk file; this type of
file name is returned when only the volume name is specified in a call to the file system
CREATE procedure or FILE_CREATE_ procedure.
Caution. For partitioned files, it is essential that the partial key value for Enscribe files, or first
key value for SQL/MP tables, on the backup system exactly match those on the primary
system. This is the RDF database administrator’s responsibility.
If the partitions are not mapped correctly on the backup system, then some updates might be
applied to the wrong partition, producing a corrupt database.