upgrade SQLSERVER 2005 to 2012 with logshipping

Hello ,
  I have a database  2005 R2 64 bit SQLserver (standard edition)  that is about 100G that has log shipping enable to a remote machine over the WAN  . The secondary DB is use for disaster recovery and it is in   "read-only state, Now , I would would like to upgrade to SQLServer 2012 . How would the upgrade affect my log shipping jobs?. Do I have to redo the logshipping?

It would be an issue if I have to redo the log shipping since it will take days to transfer a  backup to the remote location using our WAN

Thanks for your help
SiemensSENAsked:
Who is Participating?
 
Kevin CrossConnect With a Mentor Chief Technology OfficerCommented:
Are you planning to fail over to the secondary server OR leave the database offline during the upgrade?

You simply can redo log shipping from scratch on the secondary server after the upgrade as an option by the way.

Anyway, I think you have the order, just remember to backup live transaction log and restore between each step if you do fail over to secondary.
0
 
Kevin CrossChief Technology OfficerCommented:
Yes, you can upgrade log shipping configuration by upgrading the secondary server, then upgrading the primary server to SQL 2012.
http://technet.microsoft.com/en-us/library/cc645954.aspx#UpgradeSecondary
0
 
SiemensSENAuthor Commented:
Thanks but my database is in stand-by mode. So, according to the document it cannot be done..

Is it possible to change the stand-by to no recovery??
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
Kevin CrossChief Technology OfficerCommented:
You can change between the modes, it just does not take effect until the next log backup is restored per Microsoft's documentation.
0
 
SiemensSENAuthor Commented:
Thank you so if I set the database to "no Recovery" then I can upgrade SQLSERVER.

Would this be the proper steps

1: Change the DB to no recovery
2: Pause log shipping
3: upgrade the redundant server (db's in is no recovery mode)
4: Upgrade production
5:restart log shipping

Thanks for your help
0
 
SiemensSENAuthor Commented:
I plan to leave the DB offline for the upgrade.


I don't want to redo the log shipping because my database id 150 GB .  To redo from scratch will require transfering the 150 GB over the WAN and that would take days. So, I would like to avoid this step if possible.

Thanks for your help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.