December 9, 2013 at 3:25 am
Hi All,
Currently we have a stand alone SQL Server 2008 R2 Ent server. We are planning to move this environment to a Cluster. Once the cluster is ready...the plan is as follows:
1. Copy user databases to the cluster
2. Restore Master and MSDB from stand alone to cluster
My concern is the Server and SQL names. So...the Stand Alone server is called ServerA. When we build the cluster...the name will be ServerB...which we are happy with (not having the same name as the current server). Once I do a restore...we will have the servername = ServerB...but the SQL name
(select @@servername) will be ServerA. I then plan to run the SP_dropserver sp_Addserver to change the SQL name from ServerA to ServerB.
I've done this on a standalone server and it works fine...I just wanted to check if they might be issues with a cluster.
December 9, 2013 at 3:29 am
I generally recommend not restoring master from one server to another. Script the logins, server-level roles and permissions and linked servers and apply on the new server.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 9, 2013 at 3:33 am
Thanks Gail...the reason we are going for this option (restoring) is because there's not much down time. So to ensure as little down time as possible I thought this would be the quickest...but I note your comment.
Thanks again
December 9, 2013 at 3:37 am
To restore master you need to take the server down, restart it in single user mode, restore then restart again. Running scripts to create logins requires no downtime at all. If you're going for minimal downtime, why are you looking at restoring the backup of master?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 9, 2013 at 4:06 am
Denesh Naidoo (12/9/2013)
Thanks Gail...the reason we are going for this option (restoring) is because there's not much down time. So to ensure as little down time as possible I thought this would be the quickest...but I note your comment.Thanks again
Whats preventing you from scripting and applying these in advance?
I always prepare migration servers days (possibly weeks in advance). Consider logshipping databases from the source to the destination too.
December 9, 2013 at 5:01 am
Denesh Naidoo (12/9/2013)
Hi All,Currently we have a stand alone SQL Server 2008 R2 Ent server. We are planning to move this environment to a Cluster. Once the cluster is ready...the plan is as follows:
1. Copy user databases to the cluster
2. Restore Master and MSDB from stand alone to cluster
My concern is the Server and SQL names. So...the Stand Alone server is called ServerA. When we build the cluster...the name will be ServerB...which we are happy with (not having the same name as the current server). Once I do a restore...we will have the servername = ServerB...but the SQL name
(select @@servername) will be ServerA. I then plan to run the SP_dropserver sp_Addserver to change the SQL name from ServerA to ServerB.
I've done this on a standalone server and it works fine...I just wanted to check if they might be issues with a cluster.
You cannot perform this, the "IsClustered" option will be set to false in the stand alone system database. You must script out any objects required (you can do most of this in advance) and move them to the new instance. As your service account and computernames will likely change you'll possibly encounter issues with the service master key too, you have been warned :exclamationmark: :exclamationmark:
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply