Veritas did found troubles with a SAN T3 so it did close its connection to the T3.
Now during boot we have issues that the server will NOT boot if we not send a control-c at steps during boot process
1.) when it comes to
VxVM starting special volumes (swapvol roolvol var site)
Configuring /dev and /devices
VxVM general startup
--> at this position it stays for hours and not coming back
I only can do a control-c buth then it does not find all SAN T3 connections later on...
what could this be ?
at the end of our investigation we think it is maybe a possibility to rebuilt/restore the Veritas DB ??
What VxVM version do you have?
Old versions of VxVM would spend substantial time checking each ASL/APM to see if it was connected to an array (but minutes, not hours).
This was fixed in a more recent version (5.0MP3 perhaps?). Prior versions can be tuned by removing ASLs you aren't using.