Symantec logo

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 startup file that invokes vxrelocd. This file is /lib/svc/method/vxvm-recover in Solaris 10, or /etc/init.d/vxvm-recover in previous releases of the Solaris OS.

You can alter the behavior of vxrelocd as follows:

On a Solaris 10 system, after making changes to the way vxrelocd is invoked in the startup file, run the following command to notify that the service configuration has changed:

# svcadm refresh vxvm/vxvm-recover

For previous releases of the Solaris OS, reboot the system.

You can also stop hot-relocation at any time by killing the vxrelocd process (this should not be done while a hot-relocation attempt is in progress).

When executing vxrelocd manually, either include /etc/vx/bin in your PATH or specify vxrelocd's absolute pathname, for example:

# PATH=/etc/vx/bin:$PATH

# export PATH

# nohup vxrelocd root &

Alternatively, you can use the following command:

# nohup /etc/vx/bin/vxrelocd root user1 user2 &

See the vxrelocd(1M) manual page.