HP NonStop RDF, Management Manual

Page: 341 / 478

the primary CPU for all extractors, it puts the primary processes of the extractors in as many
different CPUs as possible to achieve load balancing provided there are enough CPUs. If, for
example, you have six extractors configured, but you only have two CPUs on your standby
system, the monitor places the primary processes of three extractors on one CPU and the primary
processes for the other three extractors on the other CPU. If the monitor process selects the
primary CPU of an extractor and the configured backup CPU is not available on the standby
system, then the extractor does not run as a process pair; it only has the primary process.
RDF Configuration Attributes
RDF Remote Mirror Configuration
When declaring the attributes of the RDF configuration record, you use this optional attribute
to specify whether ZLT is enabled or disabled:
SET RDF REMOTE MIRROR [ ON | OFF ]
The default is off. If this attribute is off, normal RDF operations are unchanged, as is execution
of the RDF TAKEOVER command. If this attribute is on, then you must also set other RDF and
extractor attributes, and the TAKEOVER operation has an additional step: connecting the remote
mirrors to the standby system.
RDF Remote Standby Configuration
If you set the RDF REMOTE MIRROR attribute on, you must also set the system name of a
standby system. This standby system can be either a third system, apart from the primary and
backup systems, or it can be the backup system itself. The syntax for specifying the standby
system name is:
SET RDF REMOTE STANDBY node-name
node-name must be a valid name and must identify a system in your current Expand network.
If you set the standby to a different node than your backup system, the specified system must
be accessible to the backup system.
RDF Configuration Record Validation
When you ADD the RDF configuration record, these checks are performed:
• If you set the RDF REMOTE MIRROR attribute on, but did not issue a SET RDF REMOTE
STANDBY command, the ADD command fails.
• If you set the RDF REMOTE MIRROR attribute off and issued a SET RDF REMOTE STANDBY
command, the ADD command fails.
ZLT is only a feature of the RDF/ZLT product: you cannot add the RDF record with ZLT attributes
if you do not have the RDF/ZLT product installed.
NOTE:
The hardware configuration for use of a remote mirror on the audit trail is not part of
the RDF configuration, nor is it part of any RDF validation. You must have placed the remote
mirror in a location where you can connect it to the standby system at the time of a takeover. If
you fail to do this, the RDF takeover operation fails until you have connected the remote mirror
to the standby system or turned off remote mirroring. See
“ALTER RDF Remote Mirror
Configuration” (page 342) .
Extractor Audit-Trail Configuration
When configuring RDF for ZLT, you must add the complete set of audit trail volumes to which
RDF-protected data volumes are configured. For example, if your RDF configuration only protects
data volumes configured to the Master Audit Trail (MAT), you must specify all audit trail volumes
that are configured in TMF for the MAT (active, overflow, and restore). Because each audit trail
RDF Configuration Attributes 341