Insufficient Log Data

The mirror database, "UOP_PIMB", has insufficient transaction log data to preserve the log backup chain of the principal database. This may happen if a log backup from the principal database has not been taken or has not been restored on the mirror database. (Microsoft SQL Server, Error: 1478)

I've taken a backup while the database is online and applied it to my "other" server. What do I need to do to have both in sync to get mirroring to work. My way around this is to restore the backup to my primary.

thanks.



Answer this question

Insufficient Log Data

  • WYaple

    Correct. Usually, you must restore a log backup after restoring the full backup to the server that will be the initial mirror.

    You don't _always_ have to restore a log backup. For example, create a new database, take a full backup and restore it to the partner server. You can start mirroring without doing a log backup/restore.

    BOL has been changed so that it now states that you should restore a log backup to the mirror before starting mirroring.

    If you really want to know _why_ you sometimes need to restore a log backup, grab me at a conference and we'll talk for 15 minutes or so. It was quite the interesting bug that we found around this.

    Thanks,

    Mark



  • Nikolay Yordanov

    Hallo,

    I had the same problem so i restored the Datanase and the transactionlog but I now received another errormessage:

    "The remote copy of database "mirror_Test" has not been rolled forward to a point in time that is encompassed in the local copy"

    this issue however was resolved after i backed up and restored the Database and the Transactionlog 3 times in a row .

    this was only a small database in our testLab but is there a explaination / solution for this problem so i dont have to backup and restore our 60 Gb production db 3 times ( or more ) in a row

    thanks in advance & Kind regards

    Maarten


  • Stephan Meier

    Hi, Mark,

    We are trying to use COPY_ONLY option to backup the FULL and LOG, and use that to create the mirror db. We got same error. Is this a known limitation of COPY_ONLY option (we want to use COPY_ONLY option so that it won't affect our regular backups)

    Thanks!

    George

  • rlopez_icr

    Even though the BOL don't mention this, I have always had to apply a full backup AND a transactional backup to the mirror server. A full backup did not suffice. Can anyone confirm this

  • Mat123

    What conferences are in the near future for sql server 2005 that you'll be at (North America)

    thanks.


  • rmfought

    Tech Ed this June in Boston.

    Also, anything SQL related in Seattle. PASS usually. Looks like they are going to be here (Seattle) in November.

    Then there is this:

    http://msevents.microsoft.com/cui/WebCastEventDetails.aspx EventID=1032290575&EventCategory=4&culture=en-US&CountryCode=US

    Thanks,

    Mark



  • Insufficient Log Data