SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Restoring Master DB from a StandAlone server to a Cluster


Restoring Master DB from a StandAlone server to a Cluster

Author
Message
Denesh Naidoo
Denesh Naidoo
SSC-Addicted
SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)

Group: General Forum Members
Points: 473 Visits: 1681
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.
GilaMonster
GilaMonster
SSC Guru
SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)

Group: General Forum Members
Points: 222683 Visits: 46294
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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Denesh Naidoo
Denesh Naidoo
SSC-Addicted
SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)

Group: General Forum Members
Points: 473 Visits: 1681
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
GilaMonster
GilaMonster
SSC Guru
SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)SSC Guru (222K reputation)

Group: General Forum Members
Points: 222683 Visits: 46294
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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


MysteryJimbo
MysteryJimbo
SSCertifiable
SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)SSCertifiable (5.1K reputation)

Group: General Forum Members
Points: 5123 Visits: 15346
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.
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53547 Visits: 17672
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 Exclamation Mark Exclamation Mark

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search