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

File-label modifications in Enscribe are similar to DDL operations in NonStop SQL/MP and
NonStop SQL/MX in that the modifications do not manipulate the file itself. Instead, file-label
modifications alter attributes of the file, such as the file code, the security, the extent size, and
the audit setting.
The only file-label modifications that RDF replicates are:
To create an audited Enscribe fileCREATE
To increase the number of extents for an audited Enscribe
file
ALTER MAXEXTENTS
To purge data from an audited Enscribe filePURGEDATA
To purge an Enscribe file (if REPLICATEPURGE is
enabled)
PURGE
Purge Operations
The two kinds of purge operations are PURGEDATA and PURGE. RDF replicates PURGEDATA
operations for NonStop SQL/MP tables, NonStop SQL/MX tables, and Enscribe files. RDF replicates
PURGE operations for Enscribe files if REPLICATEPURGE is set on.
Partitioned Files
All partitions of a partitioned Enscribe file or NonStop SQL/MP or NonStop SQL/MX table must
reside on volumes protected by RDF, or none should. Corresponding partitions on each system
must have the same key values.
CAUTION: For partitioned files, it is essential that the partial key value for Enscribe files, or
first key value for NonStop SQL/MP and NonStop SQL/MX tables, on the backup system exactly
match those on the primary system. This is the RDF database administrator’s responsibility.
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 filename 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.
Using SMF With RDF
RDF supports the full use of SMF on both the primary and backup nodes.
There are two basic ways to configure SMF logical volumes:
• Map many physical disks to a single virtual disk Create SMF pools where each is comprised
of many physical volumes and create SMF virtual disks from these pools. In this configuration,
the files on any given virtual disk will be spread across multiple physical disks allowing
you to pool together many physical disks to create a very large virtual disk.
70 Preparing the RDF Environment