Sunday, February 28, 2010

Veritas daemon not started at boot after veritas upgrade

1. vxconfigd -k -m disable Starts the vxconfigd daemon in disabled mode

2. vxdctl init Creates a new /etc/vx/volboot file

3. vxiod Verifies if the volume I/O daemons have been configured, should be 10 running

# vxiod set 10 Configures the 10 volume I/O daemons


4. vxdctl enable Probe the disks on the system, find a rootdg disk group on a disk. Importing
other disk groups is possible.
Volume Manager should now be started.


5. vxdctl mode Verify that VERITAS Volume Manager is running. Mode should show running

6. move install-db

cd /etc/vx/reconfig.d/state.d
mv install-db install-db.bak

7. reboot

0 comments:

Post a Comment

 
;