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
SanjayAttray
SanjayAttray
Hall of Fame
Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)Hall of Fame (4K reputation)

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


Yep. it is.

SQL DBA.
Adam Haines
Adam Haines
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: 2324 Visits: 3135
Good job Jonathan Smile



My blog: http://jahaines.blogspot.com
Ronzo
Ronzo
Mr or Mrs. 500
Mr or Mrs. 500 (553 reputation)Mr or Mrs. 500 (553 reputation)Mr or Mrs. 500 (553 reputation)Mr or Mrs. 500 (553 reputation)Mr or Mrs. 500 (553 reputation)Mr or Mrs. 500 (553 reputation)Mr or Mrs. 500 (553 reputation)Mr or Mrs. 500 (553 reputation)

Group: General Forum Members
Points: 553 Visits: 741
I'd probably add a step at the end.

After the applications are up and you're sure they're all pointed at the new server and working fine, bring the old database back on-line (or restart the old SQL Server), and perform a final full backup. This is useful for ensuring you have a copy of the database as it existed in its old environment at the time of cutover. As you noted, sometimes the new database may not be restorable on the old server (different SQL versions). And depending on auditing requirements, you may need a restorable backup for off-site storage. It also gives you a picture of the data as it existed at the point of cutover.


Have Fun!

Ronzo

Cameron Mayfield
Cameron Mayfield
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 55
Very good information. Thank you for sharing.
Robert Davis
Robert Davis
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1702 Visits: 1623
If you are upgrading SQL 2005 to SQL 2008 or an earlier version of SQL 2005 to a newer version (such as SP1 to SP3), then you can do this with database mirroring. Then you don't need to do the tail backup or any of the manual steps when it comes time to switchover. You just need to perform a failover.

Best part is, you can update the client conenction strings ahead of time to have the new server as the principal and the old server as the mirror and the client will automatically switch to the new machine.

And if you want, you could then upgrade the old server and keep using it as a mirror for the new server.



My blog: SQL Soldier
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring
Microsoft Certified Master, SQL Server MVP
Database Engineer at BlueMountain Capital Management
daeguboog
daeguboog
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 17
Good article, very informative. You might want to spell check your article the next time you submit one. Justifiably or not, it can hurt your credibility if you submit an article with multiple spelling errors and typos to a professional forum. Just takes a second to run it through a spell checker.
Jonathan Kehayias
Jonathan Kehayias
SSCommitted
SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)

Group: General Forum Members
Points: 1822 Visits: 1807
daeguboog (6/18/2009)
Good article, very informative. You might want to spell check your article the next time you submit one. Justifiably or not, it can hurt your credibility if you submit an article with multiple spelling errors and typos to a professional forum. Just takes a second to run it through a spell checker.


Perhaps you could point out the typo that you believe exists. This was written in Microsoft Word, and it passes a spell check, and manually reviewing it, there are no typos that I can find.

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
Jonathan Kehayias
Jonathan Kehayias
SSCommitted
SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)SSCommitted (1.8K reputation)

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


Yep, its basically manual log shipping. I've never used log shipping to accomplish this task because databases in my environment that I would be moving like this are already in FULL recovery. I generally off my existing backup set to perform all but the tail log restores. However, I have found in explaining this on the forums that people asking how to minimize down times, aren't in FULL recovery, and it is easier to explain how to manually do this, than to get them to setup log shipping to accomplish the same thing.

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
Robert Davis
Robert Davis
SSCommitted
SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)SSCommitted (1.7K reputation)

Group: General Forum Members
Points: 1702 Visits: 1623
Jonathan Kehayias (6/18/2009)
Perhaps you could point out the typo that you believe exists. This was written in Microsoft Word, and it passes a spell check, and manually reviewing it, there are no typos that I can find.


I didn't notice any when I read it the first time, but I read it again after seeing the above posts, and there are several typos, but on the positive side, all of the typos are spelled correctly.

top instead of to, to instead of too, its instead of it's. Nothing major, and I wouldn't have noticed if it hadn't been pointed out.


I would like to say that the part below is not correct. A tail log backup is not a normal backup. to perform a tail log backup, you have to use the NoRecovery option on the backup log command. And when you do a tail log backup, it leaves the database in a restoring state so the database is not online any more. You don't have to take it offline.

Perform a final Transaction Log backup on the old server (this is called the tail log backup), and then take the database offline if it is a shared server




My blog: SQL Soldier
Twitter: @SQLSoldier
My book: Pro SQL Server 2008 Mirroring
Microsoft Certified Master, SQL Server MVP
Database Engineer at BlueMountain Capital Management
Misha_SQL
Misha_SQL
SSChasing Mays
SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)

Group: General Forum Members
Points: 607 Visits: 983
Great approach. Thank you for the article!



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