Adding A Mapfile And Maplog To An Updater's Configuration Record; Managing Subvolume Name Mapping For Partitioned Files - HP NonStop RDF J-series RVUs Management Manual

Adding a Mapfile and Maplog to an Updater's Configuration Record

Use the RDFCOM SET command to store the names and paths for an updater's mapfile and
maplog into the updater's configuration record. For example:
RESET VOLUME
SET VOLUME ATINDEX
SET VOLUME CPUS
SET VOLUME PRIORITY
SET VOLUME PROCESS
SET VOLUME UPDATEVOLUME
SET VOLUME IMAGEVOLUME
SET VOLUME MAPFILE
SET VOLUME MAPLOG
ADD VOLUME
The updater's configuration record identifies the primary system source volume ($DATA01),
the backup system destination volume to which it is mapped ($DATA04), and the locations of
the updater's mapfile and maplog on the backup system. This mapfile and maplog are applicable
only to that updater. The mapfile and maplog pathnames cannot contain a node name.
You turn maplog logging off by specifying:
ALTER VOLUME $DATA01 MAPLOG
After the mapfile and maplog information has been stored in the updater's configuration record,
RDFCOM parses the mapping strings specified in the mapfile, logs any errors, and creates an
empty maplog if one does not exist.
When the updater starts in response to an RDFCOM START RDF/UPDATE command, it:
• Checks that the mapfile is not edited or modified by the user since the updater was last
stopped.
• Compares the last modification timestamp and CRVSN number of the mapfile with those
stored in its configuration record. If they match, the updater reads all the mapping strings
from the mapfile and skips their validation. If they do not match, the updater performs
validation of all the mapping strings and generates the appropriate EMS events in response
to errors.
• Reads the image records and applies the mapping rules to them before applying them to
the backup system database.
• If a maplog has been specified, the updater logs the source and destination filename pairs
in the maplog.
• Once started, the updater will not read modifications made to the mapfile until the updater
has been stopped and restarted or until a process takeover occurs.

Managing Subvolume Name Mapping for Partitioned Files

Problems can occur when you map a partitioned file on the primary system to a differently
named subvolume on the backup system. When a file on the primary system is partitioned across
volumes, updater mapping rules can cause the file to be replicated to partitions in separate
subvolumes on the backup system. If this situation occurs, the partitions can become corrupted,
and the updater cannot detect it. When a user application on the backup system attempts to open
both partitioned files, it reports an error.
288 Subvolume Name Mapping
0
2:1
175
$WU01
$DATA04
$DATA01
$data05.napconfg.mapfile
$data05.napconfg.maplog
$DATA01