LSBackup shows no interest in running, does lsalert affect execution of LSBackup

  • Hi

    Have log shipping set up on Primary to offload *TRns every night.

    At a point in time job failed because of power issues, and Db was shut down @ 17:00 hours, restarted next morning ( Log shipping did not happen over this two week period).

    Now I get an LSalert notification that the lsalert job failed. however LSbackup does not attempt to start.

    Executed as user: NT AUTHORITY\SYSTEM. The log shipping primary database GHADB05.PJX_P_MIG has backup threshold of 2880 minutes and has not performed a backup log operation for 141930 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14420). The step failed.

    is this normal and how do I get restarted

  • What happens when you start it manually?

  • I have not tried this yet

    what I have done is change the alert threshold so that the alert will not trigger.

    waiting to see what happens tomorrow morning ( Job scheduled to run Midnight)

    regards

  • is the schedule enabled?

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

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 4 posts - 1 through 3 (of 3 total)

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