Paresh Motiwala (8/5/2015)
I have a similar case but the retention for the files is 14 days. The job once failed did not succeed at all.
I even copied one of the files for one of the databases manually, hoping that LogShipping would be smart to pick up from there on.
This is a pretty old thread. you should post a new thread instead.
When you say the job failed- Did you find out why it failed and which job actually failed. It could either be log backup job or copy-backup job or restore backup job.
Let us know where it is actually failing. First check the SQL log on secondary to see what was the last time the log backup got actually restored.
Also, I have to ask you to be a little extra careful. Relying on logshipping agent job alerts for issues is fine but for extra safety you can run a job at secondary server which scans the sql server log(information or error log) to see if a restore of log file has happened in the last 10 minutes or whatever. This way you will have a sureshot way of knowing if logs are actually being restored.
I had a one off case where we were using Redgate scripts for backups and even though the job was not sending any failure alerts but the logs were not being restored.