Post reply

In Logshipping, Restore job is using the full backup and restoring every time and not taking the t-logs

  • June 7, 2013 at 4:52 am

    #276037

    hi experts,

    I have two servers, one is primary and another is secondary. i have created backup and copy job at primary and restore job at secondary on may 27, 2012.

    these jobs are running 5 days successfully, but restore job every time taking may 27th full backup and then restore it, what is the reason.

    If this is answered already in the forums, plz send me the link. thanks and I appreciate everyone for their work.

  • June 7, 2013 at 5:17 am

    #1622026

    Hi,

    as per your post it seems back and copy are in primary

    and restore is in secondary

    in log-shipping

    ls_backup job will be in primary and

    ls_copy ,ls_restore jobs will be in secondary

    verify this first and you are saying every time it is taking may 27 for restore

    1. first check the configuration of log-shipping like paths every thing is correct

    2. go to the secondary and check any errors

    3. try to run the ls_backup job in primary

    4. try to run the ls_copy and ls_restore jobs in secondary

    verify whether all jobs run success

    if success your log- shipping will be in sycn at both ends

    5 if not try to check all logs in primary and secondary are in sequence if not from the time it is missing logs copy to secondary and try to run all jobs at both end then it will be ok

    6. OR or take a differential backup in primary and copy in secondary and restore with standby read/only and all log will be applied and run the jobs in Primary and secondary

    check the logshipping status and sync is ok or not !!!

    Thanks
    Naga.Rohitkumar

Viewing 2 posts - 1 through 1 (of 1 total)

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