SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


"Could not find a log backup file that could be applied to secondary database"


"Could not find a log backup file that could be applied to secondary database"

Author
Message
sickpup
sickpup
Old Hand
Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)

Group: General Forum Members
Points: 313 Visits: 267
Hello all,

I'm running into some trouble setting up log shipping (on a 2008 R2 installation) and I'm hoping someone can point me in the right direction.

I'm using the setup wizard to configure everything to ship logs from DB X on Server A, to DB X_Reporting on Server B. Everything goes smoothly, with no errors, regardless of whether I create the DB X_Reporting from scratch (using the wizard) or overwrite an already existing DB X_Reporting... and regardless of whether I take an immediate backup, or use the most recent backup that already exists.

The problem is this - Once everything has been set up, when the LSRestore job runs, it doesn't error out, but gives the following:

Searching through log backup files for first log backup to restore. Secondary DB: 'X_Reporting'

Skipped log backup file. Secondary DB: 'X_Reporting', File: '\\xxxxxxxxxdevdb01\Reporting_Refresh\X_Reporting_20130917033002.trn'

Could not find a log backup file that could be applied to secondary database 'X_Reporting'

Number of log backup files restored: 0


The backup step (on the primary) works fine. The copy step works fine. All the permissions are good, and the files are getting moved to where they are supposed to be.

LSN issue? Even if I take the backup immediately?

Thanks.
Dhananjay-440114
Dhananjay-440114
SSC-Addicted
SSC-Addicted (417 reputation)SSC-Addicted (417 reputation)SSC-Addicted (417 reputation)SSC-Addicted (417 reputation)SSC-Addicted (417 reputation)SSC-Addicted (417 reputation)SSC-Addicted (417 reputation)SSC-Addicted (417 reputation)

Group: General Forum Members
Points: 417 Visits: 307
Yes its look like after reading your post to be a LSN Issue. I will suggests you to just take a Full Backup and Restore on secondary. It will surely resolve LSN issue.
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (56K reputation)SSC Guru (56K reputation)SSC Guru (56K reputation)SSC Guru (56K reputation)SSC Guru (56K reputation)SSC Guru (56K reputation)SSC Guru (56K reputation)SSC Guru (56K reputation)

Group: General Forum Members
Points: 56817 Visits: 17747
sickpup (9/17/2013)
Hello all,

I'm running into some trouble setting up log shipping (on a 2008 R2 installation) and I'm hoping someone can point me in the right direction.

I'm using the setup wizard to configure everything to ship logs from DB X on Server A, to DB X_Reporting on Server B. Everything goes smoothly, with no errors, regardless of whether I create the DB X_Reporting from scratch (using the wizard) or overwrite an already existing DB X_Reporting... and regardless of whether I take an immediate backup, or use the most recent backup that already exists.

The problem is this - Once everything has been set up, when the LSRestore job runs, it doesn't error out, but gives the following:

Searching through log backup files for first log backup to restore. Secondary DB: 'X_Reporting'

Skipped log backup file. Secondary DB: 'X_Reporting', File: '\\xxxxxxxxxdevdb01\Reporting_Refresh\X_Reporting_20130917033002.trn'

Could not find a log backup file that could be applied to secondary database 'X_Reporting'

Number of log backup files restored: 0


The backup step (on the primary) works fine. The copy step works fine. All the permissions are good, and the files are getting moved to where they are supposed to be.

LSN issue? Even if I take the backup immediately?

Thanks.

You should be able to repair the log shipping plan by taking a differential backup from the primary and restoring this to the secondary.

How often are your full backups running?
Have you checked for any other log backup jobs\operations running against your primary database?

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Mr. Kapsicum
Mr. Kapsicum
SSCrazy
SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)SSCrazy (2K reputation)

Group: General Forum Members
Points: 2049 Visits: 1037
seems like,,, an other transaction back up is being taken.

check, whether any other plan is running simultaneously !!
sickpup
sickpup
Old Hand
Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)

Group: General Forum Members
Points: 313 Visits: 267
Thanks, all. As some of you predicted, we still had a transaction log backup job running against the primary database - completely seperate from the log shipping sequence. I removed that, and now everything is running perfectly.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search