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

your applications to resume, with full RDF protection, within minutes after the loss of
your primary system, provided the two backup systems are not too far behind.
— Loopback configuration—where the primary and backup systems are the same system.
This has no value from a disaster protection standpoint, but can be useful for testing
purposes. Data from a set of volumes can be replicated to a different set of volumes on
the same node.
RDF does not require an identical one-to-one volume relationship between volumes on
the primary system and those on the backup system. Backup volume names do not
have to match primary volume names. The subsystem can direct audit information
from more than one audited volume on the primary system to a single volume on the
backup system, provided that no more than one partition of a file exists on any backup
volume. (For information on partitioned files, see the Guardian User’s Guide.)
• Application independence
RDF is application-independent; it can protect data for any application that uses NonStop
SQL/MP and NonStop SQL/MX tables and indexes or Enscribe record manager files audited
by TMF.
RDF supports these audited file types: key-sequenced, entry-sequenced, and relative (for
NonStop SQL/MP or Enscribe) and Enscribe queue files. Unstructured Enscribe files are not
supported.
RDF Subsystem Overview 41