January 16, 2009 at 1:10 pm
I am trying to find out if it is possible to configure Logshipping between SQL Server 2008 and SQL Server 2005.
Has anyone tried it or can point me to any article?
Thank You
January 16, 2009 at 2:16 pm
I tried on my laptop where both SQL 2005 and SQL 2008 Standard Edition are installed. And found the following:
--If set the 2005 instnace as primary, it won't let me add the 2008 instance as secondary, as it is beyond its scope.
--If set the 2008 instnace as primary, i will not even be able to initialize the Logshipping, i.e. not be able to restore the fullbackup of the 2008 db onto the targeted (secondary) 2005 instance. Guess, again, the 2005 engine doesn't recognize the 2008 backup.
So I guess the answer would be NO..
January 16, 2009 at 2:44 pm
That information is actually not correct.
You CAN do LogShipping from 2005 to 2008 (without STANDBY mode)
You are requiered to use SQL 2008 UI tools ... if You want to use UI for configuration.
* Noel
January 16, 2009 at 3:13 pm
Sorry for the incorrect answer above.
Yes, noeld is correct. It can be done to logshipping SQL 2005 DB to a SQL 2008 Server.
Connect to the SQL2005 instance within your SQL2008 management studio.
Then configure the logshipping for the 2005 DB as primary from there...it will go through smoothly..
Thanks for the correction, noeld.
January 16, 2009 at 3:18 pm
sunny Brook (1/16/2009)
Sorry for the incorrect answer above.Yes, noeld is correct. It can be done to logshipping SQL 2005 DB to a SQL 2008 Server.
Connect to the SQL2005 instance within your SQL2008 management studio.
Then configure the logshipping for the 2005 DB as primary from there...it will go through smoothly..
Thanks for the correction, noeld.
It was not my intention to put this bluntly.
I am sorry if it looked like that.
I was simply trying to help the PO.
* Noel
January 17, 2009 at 9:28 am
Just ensure to set the destination as NO RECOVERY and not STANDBY.
August 27, 2012 at 3:54 am
Hi,
If we keep SQL 2005 as primary and 2008 as secondry :-
The databases don't get upgraded along the way. The upgrade doesn't occur until the database is recovered. For this reason, it is not possible to log ship up version in stand-by mode. You can do it if you leave the database offline (restoring mode). If you try to use stand-by mode, you'll get an error message stating that the backup is from a different version of SQL Server becuase it can't run crash recovery until the database is upgraded.
What is your motivation behind Log Shipping? Log shipping is often used to provide a warm standby. If you use it in this way and you need to fail over to the standby server, you now have no way to swap the log shipping roles, as you can't then log ship back from the 2008 server to the 2005 server.
Regards
Sachin
August 27, 2012 at 6:27 am
Sachin Butala-182900 (8/27/2012)
Hi,If we keep SQL 2005 as primary and 2008 as secondry :-
The databases don't get upgraded along the way. The upgrade doesn't occur until the database is recovered. For this reason, it is not possible to log ship up version in stand-by mode. You can do it if you leave the database offline (restoring mode). If you try to use stand-by mode, you'll get an error message stating that the backup is from a different version of SQL Server becuase it can't run crash recovery until the database is upgraded.
What is your motivation behind Log Shipping? Log shipping is often used to provide a warm standby. If you use it in this way and you need to fail over to the standby server, you now have no way to swap the log shipping roles, as you can't then log ship back from the 2008 server to the 2005 server.
Regards
Sachin
+1
While it is possible to configure the log shipping from SQL Server 2005 to SQL Server 2008, keep it in mind that once you performed the failover you will not be able to restore your databases back on SQL Server 2005 again.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply