Log Shipping on SQL 2005 is failing because of a gap in the log chain. The schedule is every 15 minutes, the backup and copy jobs run without issue. The failure occurs early in the morning when there are no users, maintenance activities, or scheduled jobs - this has happened twice since we applied SP2. The database that is participating in the log shipping is approximately 20Gb, and recovery takes several hours.
Are there any known issues with log shipping on SP2? Any ideas why this might be happening? Is there any other information I can provide to help debug this issue?
This seems to be a duplicate of another message. Please see following URL for replies to this question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1567987&SiteID=1
No comments:
Post a Comment