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

Usage Guidelines
For the DELETE command to have any effect, a configuration record must already exist for the
secondary image trail or updater process associated with the volume name supplied (that is,
someone must have previously issued an ADD IMAGETRAIL or ADD VOLUME command for the
volume).
When you issue a DELETE VOLUME command, RDF responds:
• The extractor process stops sending image data for the volume specified in the DELETE VOLUME
command.
• The updater process associated with this volume will not be started.
Use the DELETE VOLUME command if an update volume on the backup system becomes unusable
and you want RDF to continue maintaining the other volumes. In such a case, you must stop RDF
at the primary system, issue the DELETE VOLUME command, and then restart RDF.
When it is convenient to do so, you can resynchronize the affected volume, configure a new
updater process by issuing appropriate SET VOLUME commands, and then issue an ADD VOLUME
command to restart RDF protection for the affected primary volume.
Before you can remove an image trail with the DELETE IMAGETRAIL command, you must delete
all updater processes that are configured to that image trail. The DELETE IMAGETRAIL command
then deletes the configuration record for the image trail and all image files currently belonging to
that trail. Thus, the network connection to the backup system must be available when you enter
this command.
If you need to change an updater’s image trail volume, it is recommended that you stop TMF; wait
for RDF to stop; delete the volume; re-add the volume back into the configuration, associating it to
a different image trail volume; and then restart the TMF and RDF subsystems. This is the only way
to ensure that the backup database will remain synchronized with the primary database.
Examples
Assume that RDF is protecting primary system data volumes $DATA01, $DATA02, and $DATA03,
and that all three volumes are configured to the MAT. Assume also that the changes are being
replicated to backup system volumes $DATA1, $DATA2, and $DATA3, and that the updaters for
those volumes are acquiring their audit data from secondary image trail volumes $SECIT1, $SECIT2,
and $SECIT3, respectively.
To delete the configuration records for the updater process and secondary image trail associated
with $DATA03, enter the following commands:
]DELETE VOLUME $DATA03
]DELETE IMAGETRAIL $SECIT3
Now assume that RDF is protecting primary system data volume $DATA06, which is configured
to auxiliary audit trail AUX01. Assume also that the changes are being replicated to backup system
volume $DATA6, and that the updater for that volume is acquiring its audit data from secondary
image trail volume $SECITB.
To delete the configuration records for the updater process and secondary image trail associated
with auxiliary audit trail AUX01, enter the following commands:
]DELETE VOLUME $DATA06 ATINDEX 1
]DELETE IMAGETRAIL $SECITB ATINDEX 1
EXIT
The EXIT command ends your current RDFCOM session.
EXIT
Where Issued
Primary or backup system.
RDFCOM Commands 189