Logshipping Copy/Load Schedule
-
How can I amend the copy/load schedule for logshipping to be done once a day rather than re-occuring. When I amneded the jobs created by the maintennace plan, the restore fails but copy works.
Thanks for any ideas.
-
Make sure the copy has completed before the restore begins.
-
To check file status, check out...
Thanks to this forum & David B.
Once you understand the BITs, all the pieces come together
-
The files are successfully copied and there is enough delay for the restore to begin. The load is delayed for 15 minutes. These responses bear no relevance to my question.
-
Edit your maintenance plan for log shipping, select the log shipping tab, click on the destination server and select edit, select thresholds tab, and change the load time delay to 24 hours. This should accomplish what you asked.
From BOL:
"Load time delay
Set the amount of time you want the destination server to delay before it restores the transaction log from the source server. The default for this option is zero minutes, indicating that the destination server should immediately restore any transaction log backups. Changing the time delay would provide a cushion of time if something goes wrong on the source server, allowing you to correct the problem before the corrupted log is restored onto the destination server."
David
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
-
What you are suggesting won't achieve the same result. If the tran backup is done at 9am today for example, the load/restore won't happen until next day at 9am. That is not what I want.
I will prefer to amend the restore job created on the secondary and the maintenance plan will pick up the changes.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply