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


what are the high level steps to move a server from one datacenter to another datacenter


what are the high level steps to move a server from one datacenter to another datacenter

Author
Message
charipg
charipg
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2280 Visits: 1193
what are the high level steps to move a server from one datacenter to another datacenter ?


Thanks
rhinohuey
rhinohuey
Grasshopper
Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)

Group: General Forum Members
Points: 15 Visits: 104
High level (assuming local storage and an allotted outage window):

1. Determine what applications (or other dependencies) connect to the server
2. Determine if the server is used for anything other than hosting databases
3. Plan an outage window with adequate time to do the following...
4. Stop any applications making connections to the databases
5. Take full (and trans log backups if in full recovery) backups of all databases including master, model, and msdb to reliable remote storage
6. Backup any other important files on the server (don't forget SSRS files, SSIS packages, etc)
7. Stop database (and any other necessary) services
8. Power down server
9. Move and re-rack/cable server at new data center
10. Power on server
11. Start database services
12. Start applications and ensure they can connect to the databases
13. Verify all jobs/scheduled backups are working correctly
Andrew G
Andrew G
SSCarpal Tunnel
SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)SSCarpal Tunnel (4.1K reputation)

Group: General Forum Members
Points: 4099 Visits: 2282
Turn off power
Wait for screams
Turn on power
Organise outage window with screamers
Move server

:-D
charipg
charipg
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2280 Visits: 1193
thanks..
EdVassie
EdVassie
SSChampion
SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)SSChampion (14K reputation)

Group: General Forum Members
Points: 14226 Visits: 3901
The high-risk approach is to shut down the servers, move them to the new DC, then start them up. It can be done, and I know of organisations that have been successful in doing this, but they knew it was high risk. I have also known of a truck crashing with the result that a lot of kit was too bent to be used.

If anything breaks you could have a service outage until you buy a new server and get everything installed and tested (maybe a week or two or more).

The low risk approach is to build a new environment in the new data centre, while you keep the old environment running. Seriously consider replication from old to new so that you have the same data in both locations. This allows you to do a phased cutover, with very quick fall-back to your old environment if anything breaks.

When we moved from hosted to AWS, we implemented SQL P2P replication, so we had the same daat in the two old data centres and the two new AWS Availability Zones. We then used Route53 to cut over traffic in 5% intervals, so we could be sure that things were behaving before we committed to AWS. This approach had some complexity (P2P across 4 locations), but the ability to switch workload around in a second or two very significantly reduced risk.

You should look at what options are available to you, then work out the risks of each approach and present this to your management. They will sign off on what they consider best for the business, and it is then down to you to implement it. If they go for a high risk approach, make sure your CV is up to date before you start the move - if the company folds because a truck crashes, at least your personal DR plan will be in place.

Original author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005. 14 Mar 2017: now over 40,000 downloads.Disclaimer: All information provided is a personal opinion that may not match reality.Quote: When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist. - Archbishop Hélder Câmara
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