Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Use Backup/Restore to Minimize Upgrade Downtimes


Use Backup/Restore to Minimize Upgrade Downtimes

Author
Message
Jonathan Kehayias
Jonathan Kehayias
SSCrazy
SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)SSCrazy (2.1K reputation)

Group: General Forum Members
Points: 2126 Visits: 1807
Comments posted to this topic are about the item Use Backup/Restore to Minimize Upgrade Downtimes

Jonathan Kehayias | Principal Consultant | MCM: SQL Server 2008
My Blog | Twitter | MVP Profile
Training | Consulting | Become a SQLskills Insider
Troubleshooting SQL Server: A Guide for Accidental DBAs
Pyay Nyein
Pyay Nyein
SSC-Enthusiastic
SSC-Enthusiastic (111 reputation)SSC-Enthusiastic (111 reputation)SSC-Enthusiastic (111 reputation)SSC-Enthusiastic (111 reputation)SSC-Enthusiastic (111 reputation)SSC-Enthusiastic (111 reputation)SSC-Enthusiastic (111 reputation)SSC-Enthusiastic (111 reputation)

Group: General Forum Members
Points: 111 Visits: 404
Thanks for the good article, Jonathan. :-)
Jagadish Kumar Punnapu
Jagadish Kumar Punnapu
SSC-Enthusiastic
SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)SSC-Enthusiastic (151 reputation)

Group: General Forum Members
Points: 151 Visits: 111
I sincerely appreciate this idea Jonathan...
Amit W
Amit W
Right there with Babe
Right there with Babe (772 reputation)Right there with Babe (772 reputation)Right there with Babe (772 reputation)Right there with Babe (772 reputation)Right there with Babe (772 reputation)Right there with Babe (772 reputation)Right there with Babe (772 reputation)Right there with Babe (772 reputation)

Group: General Forum Members
Points: 772 Visits: 105
Thanks for the article!

Just a thought...steps 1-7 can be done using setting up log shipping and the rest can be done using step 8 onwards when moving on to the new server.



publicbutler@imapmail.org
publicbutler@imapmail.org
Valued Member
Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)Valued Member (59 reputation)

Group: General Forum Members
Points: 59 Visits: 101
I have used this method for years. Even with busy and/or large databases, I can move a database server to a new piece of hardware with only about 10 minutes of downtime. I recently used the same method during migration of a number of legacy SQL 2000 boxes to SQL 2005.

- Jay
Noel McKinney
Noel McKinney
SSCrazy
SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)

Group: General Forum Members
Points: 2031 Visits: 797
Good article Jonathan, I've used these steps to move databases to new hardware and datacenter with just a few minutes of downtime. The key is making sure that the application(s) that use the databases are good to go. If possible you need to test such applications on the new hardware first to make sure the configurations are set properly... restore a backup of an actual database for such testing, using a "test" database might not reveal potential problems.

The other thing is to make sure that logins have been propagated to the new server.
alen teplitsky
alen teplitsky
SSCommitted
SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)

Group: General Forum Members
Points: 1883 Visits: 4628
we're usually not as nice

if we do a side by side upgrade we tell people the cut off for R/O access. then we backup and restore on the new hardware. critical databases are on the SAN and we just point people to a replicated copy of the data while we upgrade the hardware
Gethyn Ellis
Gethyn Ellis
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1183 Visits: 2867
Noel McKinney (6/18/2009)
Good article Jonathan, I've used these steps to move databases to new hardware and datacenter with just a few minutes of downtime. The key is making sure that the application(s) that use the databases are good to go. If possible you need to test such applications on the new hardware first to make sure the configurations are set properly... restore a backup of an actual database for such testing, using a "test" database might not reveal potential problems.

The other thing is to make sure that logins have been propagated to the new server.


The sp_help_revlogin stored proc could be useful for moving the logins.

edited to add URL:

http://support.microsoft.com/kb/246133

Gethyn Ellisgethynellis.com
noeld
noeld
SSCertifiable
SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)SSCertifiable (7.1K reputation)

Group: General Forum Members
Points: 7056 Visits: 2048
Ermm... Isn't this just a description of LogShipping ?


* Noel
Gethyn Ellis
Gethyn Ellis
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1183 Visits: 2867
noeld (6/18/2009)
Ermm... Isn't this just a description of LogShipping ?


Yes it is, using a manual log shipping process to keep a large db up to date prior to the migration date. I used this many times and it does save alot time compared to 'doing it all the day'

Gethyn Ellisgethynellis.com
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