Log shipping error

Question

Post reply

Log shipping error

jblovesthegym

Ten Centuries

Points: 1048
More actions
April 11, 2012 at 5:19 am

#96830

Hi all,

A restore job on the secondary has failed with the following message in the log:

'The backup data in '\\XXXXXXXXXXXXXXXX.TRN' is incorrectly formatted. Backups cannot be appended, but existing backup sets may still be usable.'

A subsequent error message reads,

Error: 5180, Severity: 22, State: 1

'Could not open FCB for invalid file ID 0 in database 'XXXXXXXXXX'.

The database, however, is NOT marked suspect (a case I had posted up 2 weeks ago here and wish to avoid again!)

Would appreciate some advice!

JB
April 12, 2012 at 2:17 am

This was removed by the editor as SPAM
April 12, 2012 at 3:36 am

This was removed by the editor as SPAM
April 12, 2012 at 4:11 am

This was removed by the editor as SPAM

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

jblovesthegym Ten Centuries Points: 1048 More actions · Answer 1

prettsons (4/12/2012)

To resolve this error (The backup data in '\\XXXXXXXXXXXXXXXX.TRN' is incorrectly formatted. Backups cannot be appended, but existing backup sets may still be usable.').

First Copy the backup file to some other location and delete the original file from the backup location. Restore the job and it will work fine. After that you can easily restore your database by using backup.

By "restore the job" I presume you mean "re-run the job"?

jblovesthegym Ten Centuries Points: 1048 More actions · Answer 2

prettsons (4/12/2012)

jblovesthegym (4/12/2012)

prettsons (4/12/2012)

To resolve this error (The backup data in '\\XXXXXXXXXXXXXXXX.TRN' is incorrectly formatted. Backups cannot be appended, but existing backup sets may still be usable.').

First Copy the backup file to some other location and delete the original file from the backup location. Restore the job and it will work fine. After that you can easily restore your database by using backup.

By "restore the job" I presume you mean "re-run the job"?

Yes!!

Have you check the article??

I will, but first I need to know how the process above can work; if I get rid of the .trn and simply re-run the restore on the secondary, won't it fail when it sees there is no file to work with? Or does it automatically call the backup job at the primary to send a new file?