April 4, 2012 at 9:11 am
Hi,
I have a two part questions about implementing Log Shipping.
1. Can Log Shipping be implemented from SQL Sever 2005 to SQL Server 2008? What I mean by this is that can the source be SQL Server 2005 and the destination be SQL Server 2008?
2. There is already a DB maintenance that backs up transaction log every 30 minutes. When we implement the Log Shipping process, would this be a problem since the log file is sent to the destination server?
Thanks,
April 4, 2012 at 9:14 am
1. Yes, but it's not very useful. If the primary ever fails and you have to switch to the secondary, there will be no way to go back to the SQL 2005 primary
2. Yes. When log shipping is running, no other job or process can back the log up without breaking log shipping.
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
April 4, 2012 at 9:35 am
GilaMonster (4/4/2012)
2. Yes. When log shipping is running, no other job or process can back the log up without breaking log shipping.
Gail, thanks for your replay.
What is the best way to handle this? We would like to keep the DB maint. in place and at the same time send data to the destination every hr.
April 4, 2012 at 9:37 am
Don't. Log shipping replaces your log backups with its own log backups.
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
April 4, 2012 at 9:46 am
OK. Thank you for you help on this.
April 5, 2012 at 4:53 am
GilaMonster (4/4/2012)
1. Yes, but it's not very useful. If the primary ever fails and you have to switch to the secondary, there will be no way to go back to the SQL 2005 primary
It is useful for upgrading large database server to a new version of SQL Server in minimal time.
April 5, 2012 at 6:01 am
MysteryJimbo (4/5/2012)
GilaMonster (4/4/2012)
1. Yes, but it's not very useful. If the primary ever fails and you have to switch to the secondary, there will be no way to go back to the SQL 2005 primaryIt is useful for upgrading large database server to a new version of SQL Server in minimal time.
Yes, but it's not very useful for a DR setup unless it's an interim step in an upgrade of the primary.
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 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply