|
|
|
|
|
The site reattachment daemon, vxsited, provides automatic reattachment of sites. vxsited uses the vxnotify mechanism to monitor storage coming back online on a site after a previous failure, and to restore redundancy of mirrors across sites.
If the hot-relocation daemon, vxrelocd, is running, vxsited attempts to reattach the site, and allows vxrelocd to try to use the available disks in the disk group to relocate the failed subdisks. If vxrelocd succeeds in relocating the failed subdisks, it starts the recovery of the plexes at the site. When all the plexes have been recovered, the plexes are put into the ACTIVE state, and the state of the site is set to ACTIVE.
If vxrelocd is not running, vxsited reattaches a site only when all the disks at that site become accessible. After reattachment succeeds, vxsited sets the site state to ACTIVE, and initiates recovery of the plexes. When all the plexes have been recovered, the plexes are put into the ACTIVE state.
Note
vxsited does not try to reattach a site that you have explicitly detached by using the vxdg detachsite command.
The automatic site reattachment feature is enabled by default. The vxsited daemon uses email to notify root of any attempts to reattach sites and to initiate recovery of plexes at those sites. To send mail to other users, add the user name to the line that starts vxsited in the /etc/init.d/vxvm-recover startup script, and reboot the system.
If you do not want a site to be recovered automatically, kill the vxsited daemon, and prevent it from restarting. To kill the daemon, run the following command from the command line:
Locate the process table entry for vxsited, and kill it by specifying its process ID:
If there is no entry in the process table for vxsited, the automatic site reattachment feature is disabled.
To prevent the automatic site reattachment feature from being restarted, comment out the line that starts vxsited in the /etc/init.d/vxvm-recover startup script.