May 12, 2008 at 9:44 am
Hey all,
We are upgrading (migrating would be a better way of putting it) a non-clustered SQL 2k server to a clustered configuration. Unfortunately, we have processes connecting to the current server directly via IP address as well as several processes connecting to SQL via IP address. In creating the cluster, there doesn't seem to be a way to have the virtual cluster IP and the virtual SQL IP be the same as it is on the current non-clustered server. We're trying to avoid changing all the connected processes outside the server since we're pressed for time. Has anyone dealt with this scenario before, or have any good sources for information on such an upgrade?
Thanks!
May 12, 2008 at 11:41 am
when you install SQL on the cluster it will ask you for the IP. by default when you create the cluster it only creates the default cluster group. when you install SQL it creates a new group to hold all the sql resources including the IP and network name
you will first have to change the IP of your non-clustered server and the name as well
May 12, 2008 at 12:57 pm
Thanks for the quick answer. You are correct. However, if you enter the IP of the cluster when installing SQL, you will receive a message telling you it's taken and to choose another. And if you try to add the SQL IP to the cluster group as a resource after installing SQL, you receive an error that the cluster IP is already in use. So there doesn't appear to be a way to have the cluster IP and the SQL IP be the same, like they were on the non-clustered SQL server. I haven't seen too much information on the net about migrating a database from a non-clustered to a clustered environment, which is surprising to me. Any ideas?
Thanks!
May 12, 2008 at 1:13 pm
I think it is best to just set up the cluster with new sets of IP address once everything is done and ready to go, your network admin could go to the active directory and have it reroute all the old ip address traffice to the new ip address for the new cluster. Isn't that call DSN alias? Once that is implemented, you could take your time to repoint to the new IP address application by application.
Sopheap
May 12, 2008 at 1:25 pm
you first have to change the IP on the old server and then set up the cluster
for the cluster you will need 4-5 IP's
1 IP for each of the physical nodes
1 IP for the cluster group
1 IP for the SQL instance
and 1 IP for the MSDTC resource if you are going to use it
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply