VERITAS Volume Manager 3.5 Administrator's Guide (September 2002)

Chapter 9, Administering Hot-Relocation
Modifying the Behavior of Hot-Relocation
243
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.
Caution 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 vxrelocd is running. You leave hot-relocation
turned on so that you can take advantage of this feature if a failure occurs. However, if
you choose to disable this feature (perhaps because you do not want the free space on
some of your disks to be used for relocation), prevent vxrelocd from starting at system
startup time.
You can stop hot-relocation at any time by killing the vxrelocd process (this should not
be done while a hot-relocation attempt is in progress).
You can make some minor changes to the way vxrelocd behaves by either editing the
vxrelocd line in the startup file that invokes vxrelocd
(/sbin/rc2.d/S95vxvm-recover), or by killing the existing vxrelocd process and
restarting it with different options. After making changes to the way vxrelocd is
invoked in the startup file, you need to reboot the system so that the changes go into
effect.Ifyou choosetokill and restartthe daemoninstead,make sure that hot-relocationis
not in progress when you kill the vxrelocd process. You should also restart the daemon
immediately so that hot-relocation can take effect if a failure occurs.
You can alter vxrelocd behavior as follows:
◆ To prevent vxrelocd starting, comment out the entry that invokes it in the startup file:
# nohup vxrelocd root &
◆ By default, vxrelocd sends electronic mail to root when failures are detected and
relocation actions are performed. You can instruct vxrelocd to notify additional
users by adding the appropriate user names as shown here:
nohup vxrelocd root user1 user2 &
◆ To reduce the impact of recovery on system performance, you can instruct vxrelocd
to increase the delay between the recovery of each region of the volume, as shown in
the following example:
nohup vxrelocd -o slow[=IOdelay] root &
where the optional IOdelay value indicates the desired delay in milliseconds. The
default value for the delay is 250 milliseconds.