Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)

The comment fields of all the subdisks on the destination disk remain marked as
UNRELOC until phase 3 completes. If its execution is interrupted, vxunreloc can
subsequently re-use subdisks that it created on the destination disk during a
previous execution, but it does not use any data that was moved to the destination
disk.
If a subdisk data move fails, vxunreloc displays an error message and exits.
Determine the problem that caused the move to fail, and fix it before re-executing
vxunreloc.
If the system goes down after the new subdisks are created on the destination
disk, but before all the data has been moved, re-execute vxunreloc when the
system has been rebooted.
Warning: Do not modify the string UNRELOC in the comment field of a subdisk
record.
Modifying the behavior of hot-relocation
Hot-relocation is turned on as long as the vxrelocd process is running. You should
normally leave hot-relocation turned on so that you can take advantage of this
feature if a failure occurs. However, if you choose to disable hot-relocation (perhaps
because you do not want the free space on your disks to be used for relocation),
you can prevent vxrelocd from starting at system startup time by editing the
/sbin/init.d/vxvm-recover startup file that invokes vxrelocd.
If the hot-relocation daemon is disabled, then automatic storage reclamation on
deleted volumes is also disabled.
You can alter the behavior of vxrelocd as follows:
Administering hot-relocation
Modifying the behavior of hot-relocation
422