September 27, 2013 at 8:01 am
Greetings Earthlings,
I'm setting up logshipping between primary 2008 and destination 2012 servers. It is going well as I am moving from database to database although as I am getting to the larger databases I am seeing potential issue coming up. Here is the workflow to establish log shipping that I have figured out. If you have an improvement to the process then I would welcome to hear it:
Backup DatabaseA on SQL2008
Copy the backup to SQL2012
Restore the database with recovery (I can not restore with standby because it needs to go through an upgrade to 2012)
Backup the now upgraded database to disk
Restore the database with Standby/Read Only
Turn on log shipping jobs (TL backup on 2008, Copy on 2012, TL Apply on 2012)
All works fine from then on.
Temporarily, we do not have enough space on the destination for a backup of the larges logshipped database. Therefore I have tried to utilize restoring to 2012 from the \\sql2008\backupdrive. That worked fine. Backing the upgraded 2012 database to the \\sql2008\backupdrive has failed me. Most likely due to network's unability to maintain quality connection during the 2Terrabyte backup.
September 12, 2016 at 7:07 am
Does this really work between 2008 and 2012?
I have tried this scenario but the transaction logs just won't restore and get skipped, has anyone else done this?
September 12, 2016 at 7:20 am
Molap (9/27/2013)
Backup DatabaseA on SQL2008Copy the backup to SQL2012
Restore the database with recovery (I can not restore with standby because it needs to go through an upgrade to 2012)
Backup the now upgraded database to disk
Restore the database with Standby/Read Only
Turn on log shipping jobs (TL backup on 2008, Copy on 2012, TL Apply on 2012)
All works fine from then on.
Log backups fail to restore with the error indicating the LSNs don't match.
Does this really work between 2008 and 2012?
No, it doesn't work.
p.s. 3 year old thread.
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
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply