RDF System Management Manual for J-series and H-series RVUs (RDF 1.10)

Recovery
Either use the OPEN command to open an RDF CONFIG file in an existing RDF control subvolume,
or initialize a new RDF configuration with the INITIALIZE RDF command.
The control subvolume \sys.$SYSTEM.subvol is not empty. The files on
the control subvolume must be purged. Please note, these files might
belong to another RDF configuration.
sys
is the name of the primary system.
subvol
is the name of the local RDF control subvolume.
Cause
You tried to execute an INITIALIZE RDF command, but RDF control files (such as CONFIG or
CONTEXT) already exist on the local control subvolume.
Effect
The INITIALIZE RDF command aborts.
Recovery
You must purge $SYSTEM.subvol.* on the primary system before you can retry the INITIALIZE
RDF command. Before doing so, however, be sure that the existing files do not belong to a
different RDF configuration that is still valid.
The EXTRACTOR must be a named process
Cause
You must specify a process name for the extractor process before issuing an ADD command.
Effect
The start command fails.
Recovery
You must reconfigure RDF with a named extractor process.
The last record in the local imagetrail on volume-name.subvolume-name
could not be found in the remote trail
volume-name
is the name of the image trail’s volume
subvolume-name
is the name of the image trail’s subvolume.
Cause
The COPYAUDIT command could not find the last record in the local image trail on the remote
image trail. This problem indicates that the receiver’s RETAINCOUNT value was probably not
set high enough and that, as a result, some image files on the remote system were purged.
Effect
The COPYAUDIT command aborts.
Recovery
There is no recovery action. The COPYAUDIT command cannot be executed because image
files needed for this command were already purged from the remote system.
The MAPFILE filename is not found
filename
is the name of the updater mapfile specified in the updater configuration.
RDFCOM Messages 457