troubleshooting Question
SQL server log shipping job failure
hi all,
our log shipping failed because the network link between primary and secondary is too busy for the whole day and copying a 6GB log takes 23 hours and we stop it until now, which the network is going ok, log file can be copy.
but the restore job keep failing, application log has this :
and the log history message just said :
the log retention period is 2 days, I am not sure what happened?
please share experience.
our log shipping failed because the network link between primary and secondary is too busy for the whole day and copying a 6GB log takes 23 hours and we stop it until now, which the network is going ok, log file can be copy.
but the restore job keep failing, application log has this :
The log shipping secondary database <server>.<DB>has restore threshold of 180 minutes and is out of sync. No restore was performed for 11229 minutes. Restored latency is 63 minutes. Check agent log and logshipping monitor information.
and the log history message just said :
The job failed. The Job was invoked by Schedule 15 (DefaultRestoreJobSchedule). The last step to run was step 1 (Log shipping restore log job step.).
the log retention period is 2 days, I am not sure what happened?
please share experience.
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 3 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.
Our community of experts have been thoroughly vetted for their expertise and industry experience.
The Distinguished Expert awards are presented to the top veteran and rookie experts to earn the most points in the top 50 topics.