asked on
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.
Storage SoftwareMicrosoft SQL Server 2008Microsoft SQL Server
Last Comment
marrowyung
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
AHAHHAHA
very clear mind. glad to have you keep helping me instead of someone else who come and just blame.
my boss fixed it after work with consultant and finally it is really what I said.
has to restore from the beginning.
very clear mind. glad to have you keep helping me instead of someone else who come and just blame.
my boss fixed it after work with consultant and finally it is really what I said.
has to restore from the beginning.
or we need to do a full backup restore again and kick off log shipping again?
and the DB doing this log shipping has merge replication setup, any concern on recreating the log shipping?
I think no as we just back that DB up and then the log shipping wizard will create the job again for us , then starting copying transaction log again?
so the steps is :
1) untick the "enable this as a primary database in a log shipping configuration " in the database properties page and let SQL server handle the job remove.
2) do full backup on primary and copy the backup to secondary and restore as non recovery mode.
3) then tick the option in 1) ?