SQL Server Performance

Point in time restore on primary server

Discussion in 'SQL Server Log Shipping' started by johnc, Apr 28, 2004.

  1. johnc New Member

    I've implemented log shipping using the excellent article on this site but have a question about restores. The transaction log is being backed up every 15 minutes to a particular disk directory and is overwritten each time. When I try to do a test restore on the primary server to a particular point in time through EM, I select the last daily full backup and each of the transaction log backups up to the point I want to restore (each of these actually point to the same file). The restore fails with error 4305 - The log in this backup set begins at LSN ###, which is too late to apply to the database. An earlier log backup that includes LSN ### can be restored. How can I get the restores to work on the primary server? Thanks

    John
  2. satya Moderator

    The error 4305 indicates that the restore operation found a gap between the last restore and the transaction log that you attempted to apply. So, to resolve this error you should restore transaction logs in the same order in which they were backed up.



    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  3. johnc New Member

    I think I understand the error but the problem I have is that there is only one physical transaction log backup file because it gets overwritten every 15 minutes when the backup log job runs. Should the backup log job be creating a new unique file each time it runs? I know that is what used to happen when I just had a transaction log backup scheduled as a maintenance plan.

    John
  4. satya Moderator

    Yes it should create a new log file whenever job executes every 15 minutes, that is what happens even at my end.

    Check at your end for the schedule of events and files.


    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

Share This Page