Break cluster and move databases to new server

Question

Hello everyone.  I have a question that may be basic but I am by no means a SQL person.  Right now we have a SQL 2005 cluster running on VM ESXi with a celerra backend storage.  Some drives are mapped Raw.  We recently put in a new VNX and we are not able to migrate the SQL server over due to how the drives are mapped.  I am thinking that I want to build a new SQL server and move the databases.  The new build will not be a cluster since we have point in time recovery manager from EMC.  Now my thinking is, can I break the cluster, move the 2nd node to the new ESXi and storage and present new storage or would it be best to just build a new server?  Is it easy enough to change an instance name after SQL is running?  Several applications refer to the SQL Cluster and they are critical so I need something with least amount of downtime.  Would doing backup of all of SQL and then a restore to the new system be best?  Any thoughts or direction?  Thanks

---

Joe M

Answer 1

The most straightforward and reliable method is to build a new server, migrate the databases using backup/restore, test the new server, and cut-over by shutting down the old servers and either reconfiguring the client applications or renaming the new server to have the same network name as the old server's SQL Cluster Client Access point. 

You can also use DNS redirection instead of renaming the new server, although using a DNS hostname alias for your server requires some additional security configuration.  EG http://blogs.msdn.com/b/dbrowne/archive/2012/05/21/how-to-add-a-hostname-alias-for-a-sql-server-instance.aspx

David

David

---

David http://blogs.msdn.com/b/dbrowne/

Answer 2

Thanks. I was kind of thinking that.  Now when I change server name, I also need to change SQL Instance name correct?

---

Joe M

Answer 3

Here's the BOL article on it:

Rename a Computer that Hosts a Stand-Alone Instance of SQL Server

David

---

David http://blogs.msdn.com/b/dbrowne/