Migrating from one cluster technology to another or even with-in the same technology is fairly easy. Recently I'm run into an issue where we need to migrate a SQL Server Instance from a HP Polyserve Cluster to a Microsoft Cluster.
There were two issues I found in setting this up:
- Installing SQL Server on a Microsoft Cluster requires a virtual name
- Keeping the exact same Port Number
The reason for the above two issues was to keep the down time to an absolute minimum and ensure there were no changes necessary to the application or infrastructure (firewalls).
Fortunately both HP Polyserve and Microsoft Clustering use virtual names, this is what makes this possible.
I found the following two links helpful:
How to: Rename a SQL Server 2005 Virtual Server
How to change the network IP addresses of SQL Server failover cluster instances
The key to making this happen is to install SQL Server using a temporary Virtual name and IP Address and ensure to use the EXACT Same instance name. Instance names can not be changed with SQL Server 2005 (or at least it's not supported to change them). Changing the port number is pretty standard stuff.
Now you can pre-test your migration of databases and user logins, and load test the new hardware.
At the designated change time we performed the following.
- Take the Microsoft Cluster Off line
- Take the Instance on HP Polyserve and delete the Instance and virtual name (binaries and data files will be kept as a backout plan)
- Using the SQL Server Configuration editor, change the IP address on all nodes in the Microsoft Cluster:
- Using the Cluster Administrator change the SQL Server IP Address
- Using the Cluster Administrator change the SQL Server network name
- Bring the Cluster on-line
The one issue we ran into was with logical networks and VLANS, I don't have a complete understanding of network topology, but only certain logical networks with-in our environment can host different ranges of IP Addresses. Initiall we built the new cluster on a logical network that was unable to host the existing virtual name and the switch failed, ensure to talk to your network, windows and DNS engineers about exactly what your wanting to do so they can build things properly the first time, as they don't like switching and changing things twice any more than DBA's do !