Satish-1028188 (9/18/2012)
Thanks Perry, your suggestions make sense, I would see now, How I can impliment this in my case.Thanks Sudhakar, yes (in last few cases) it was in-between t-log backups which caused these failure, I am digging more to find if there were any other causes...
As Perry mentioned, make sure that the log backups are defined by Log shipping schedule. You should monitor the msdb backup tables to know how the backups are running. It should be only done by the sql agent. If a user is taking a backup, it is going to break the LSN chains. also make sure that the cleanup jobs run only when logs are shipped successfully.
I would also go to each log shipping job manually and make it write the output to a report file and I would like to append the data each time the job runs to keep a track of behavioral patters of failures.
Chandan