Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

what are the high level steps to move a server from one datacenter to another datacenter Expand / Collapse
Author
Message
Posted Monday, June 24, 2013 2:42 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Wednesday, August 20, 2014 5:21 AM
Points: 412, Visits: 1,020
what are the high level steps to move a server from one datacenter to another datacenter ?


Thanks
Post #1466632
Posted Monday, June 24, 2013 11:03 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, August 21, 2014 7:44 AM
Points: 1, Visits: 84
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
Post #1466973
Posted Monday, June 24, 2013 11:56 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Today @ 1:04 AM
Points: 1,202, Visits: 1,671

Turn off power
Wait for screams
Turn on power
Organise outage window with screamers
Move server

Post #1466984
Posted Monday, June 24, 2013 11:59 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Wednesday, August 20, 2014 5:21 AM
Points: 412, Visits: 1,020
thanks..
Post #1466985
Posted Wednesday, June 26, 2013 6:31 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 4:14 AM
Points: 2,868, Visits: 3,215
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 2014, 2012, 2008 R2, 2008 and 2005. 28 July 2014: now over 30,000 downloads.
Disclaimer: All information provided is a personal opinion that may not match reality.
Concept: "Pizza Apartheid" - the discrimination that separates those who earn enough in one day to buy a pizza if they want one, from those who can not.
Post #1467625
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse