May 2, 2005 at 3:04 pm
Hello, has anuone done this and has a suggestion to do it in a particular way?
Situation: Running On: Win2k3, SQL2k
A) We have two nodes (node1 and node2) on cluster1 - they are attached to SAN1 - each has 3 virtual server instances - Inst1,2 and 3
B) We purchased a third machine and put it in a different physical location (same domain) attached to a different SAN
C) There will be a 4th server to join the new cluster, therefore creating two paris of servers attached to two different SANs creating two clusters Cluster1 and Cluster2
Question?
I need to move everything from Node2 (in step A) to this new node (called Node3 - attached to a seperate SAN). What is the least problematic way? Can I create 3 new virtual server instances (Inst4,5, and 6), transfer the data and then re-name them later back to Inst1, 2 and 3? Or should I create 3 new instances and tell the users to change their ODBC, etc.... Any other suggestions?
Thanks
A.
May 2, 2005 at 3:15 pm
Don't know much about clustering but I know you can't rename an instance
* Noel
May 3, 2005 at 8:52 am
Since they are in the same domain, you can't name them appropriately (and as Noel stated, you can't rename instances).
However, in Windows 2003, I know it is possible to set up a geographically dispersed cluster; I'm not sure of the SQL implications to this. You'll want to research it at MS's website:
http://www.microsoft.com/windowsserver2003/techinfo/overview/default.mspx
Good luck!
May 3, 2005 at 1:15 pm
To start with here's a few handy links:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;314546
http://support.microsoft.com/default.aspx?scid=kb;en-us;246133&Product=sql2k
http://support.microsoft.com/kb/224071/EN-US/
http://support.microsoft.com/kb/240872/EN-US/
http://support.microsoft.com/default.aspx?scid=kb;EN-US;295732
As for connections via ODBC, well, you've already gone down the hard path by using computernames or fully qualified domain names. When you move from one virtual instance to another there is no choice but to change the ODBC DSNs. However you can make life easier moving forward if you use some DNS 'aliasing'. Persently you have cluster1/inst1 and you need to move it to cluster3/inst3. If you would have had a DNS 'alias' called say 'app1' (pointing to cluster1/inst1) it would be a piece of cake. You could move cluster1/inst1 to cluster3/inst3 then just modify the DNS 'alias' app1 to point to cluster3/inst3 and you're done.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply