UNCLASSIFIED
Hi Joel,
The beauty of veritas is that it does not care about the SCSI disk names
to make the disk group, and, over time, I have learned to let them go as
well.
What we need to concentrate on is the disk media names. The names in
the DISK column below. So, according to vxdisk
UNCLASSIFIED
Hi Joel,
Well, everything is looking good. I'd run vxdiskadm again and chose
option 3, to remove that disk, silo2dg17.
Any volumes in the NEEDSYNC state will recover by themselves. Any
others, will need a manual recover. Something like:
# vxrecover -b mysqlData07-L05
For
UNCLASSIFIED
Hi Joel,
I am unsure as to why vxrecover has wedged itself like this. It does
look like it is trying to abort it's current task and cannont for some
reason. I would err on the side of caution and leave it until the next
maintenance window and reboot the box. However, Veritas
