SQL 2000 cluster with Veritas Volume Manager
Ran into an issue yesterday where the RTM SQL 2000 install on a Windows 2003 cluster would freeze or hang between the IP addresss entry and the Disk Selection screens. No error…just hang.
Looked in Cluster Admin and found that the SQL group was named “data” and the disk resource was named “data”
We changed the disk resource to “data1” and everything was fine after that.
Not sure if the Veritas Volume manager software had anything to do with it, but it did present some issues earlier in the install.
Takeaway: Name your SQL Group something obvious, like “SQL Group” or “SQL2000”