Friday, March 23, 2012

logshipping mystery.

Hey All,
Hope this is the right place for this post.

I set up logshipping between two databases recently. everything looks fine. the backup, copy and restore jobs are all suceeding(from the job log). the problem is no Tlogs are being restored in secondary database. The restore job skips all the tlogs and says it did not find any tlog back up file to restore!! The jobs finishes with this:

007-07-17 14:40:30.59 Could not find a log backup file that could be applied to secondary database 'SaaSNet_dataStore'.
2007-07-17 14:40:30.59 The restore operation was successful. Secondary Database: 'SaaSNet_dataStore', Number of log backup files restored: 0
2007-07-17 14:40:30.59 Deleting old log backup files. Primary Database: 'SaaSNet_DataStore'
2007-07-17 14:40:30.59 The restore operation was successful. Secondary ID: '5808a414-2ada-41d2-a8a0-2cf84f85174a'

Appreciate your help


the problem was that we had a maintenance job running on the source sql server(doing hourly Tlog backups).

the job created gaps in the logshipping tlogs sequence numbers, which threw off the restore phase.

we resolved the issue by removing the specific databses from the tlog maintenance job(since logshipping is backing up the tlog for those databases anyway) and that did it. I had to redo the logshipping config afterwards to start fresh.

|||
the problem was that we had a maintenance job running on the source sql server(doing hourly Tlog backups).

the job created gaps in the logshipping tlogs sequence numbers, which threw off the restore phase.

we resolved the issue by removing the specific databses from the tlog maintenance job(since logshipping is backing up the tlog for those databases anyway) and that did it. I had to redo the logshipping config afterwards to start fresh.

No comments:

Post a Comment