Posted: 6/26/2013 5:55:12 AM EDT
|
We have this ancient SQL 2005 Cluster on a pair of Windows Server 2003 R2 x64 servers plumbed to an EMC Clarion. We are replacing the EMC with a NetApp FAS2240-2, and have migrated 2 other SQL clusters to NetApp storage without issue, including one that is practically identical in terms of OS and SQL version.
This particular cluster appears to have issues with the SQL instances, as NetApp's SMSQL product does not see the instance names. If I type the instance name in manually, maybe after 4 or 5 tries it will connect to the smaller of the 2 instances (the one with 30 DB's), but the ERP system on the other instance never completely enumerates. It has over 700 databases. The drop-down menu for the SMSQL Configuration Wizard shows one cluster name, and one domain controller. Other cluster systems will show every SQL instance in the domain. I've checked DNS, AD, SQL Configuration, etc., opened a ticket with NetApp suport, sent them nsanity dumps of snapdrive and snapmanager for both members of the cluster with no answers yet. I think it is a windows issue, this domain was built way, way, way before my time here. Would it be worth a call to M$ support? I'm ready to dump it all on the vendor for the ERP and let them come up with a plan to migrate the entirety of the SQL instance to new systems. That may not be an option since their last patch broke the security database relationship with the 700+ user db's and management is a bit gun shy to rely on them. |