Quantcast
Channel: SQL Server Database Engine forum
Viewing all articles
Browse latest Browse all 12963

log shipping: RESTORE LOG WITH CONTINUE_AFTER_ERROR?

$
0
0

Hi experts,

  I found the restore log on standby node failed with the error message like below. What happen? How do I prevent this error? How do I repair(rebuild a new log shipping DB)?

---  messages ---

Msg 4360, Level 16, State 1, Line 1
RESTORE LOG WITH CONTINUE_AFTER_ERROR was unsuccessful. Execution of the RESTORE command was aborted.
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.

--- errorlog ---

2014-07-16 07:00:00.42 Logon       Error: 18456, Severity: 14, State: 38.
2014-07-16 07:00:00.42 Logon       Login failed for user 'QCISAP\---'. Reason: Failed to open the explicitly specified database '---'. [CLIENT: <local machine>]
2014-07-16 07:01:49.52 spid60      Error: 4360, Severity: 16, State: 1.
2014-07-16 07:01:49.52 spid60      RESTORE LOG WITH CONTINUE_AFTER_ERROR was unsuccessful. Execution of the RESTORE command was aborted.
2014-07-16 07:19:56.38 spid59      FlushCache: cleaned up 247385 bufs with 162904 writes in 278549 ms (avoided 0 new dirty bufs) for db 7:0
2014-07-16 07:19:56.38 spid59                  average throughput:   6.94 MB/sec, I/O saturation: 161105, context switches 305229
2014-07-16 07:19:56.38 spid59                  last target outstanding: 34, avgWriteLatency 35

Viewing all articles
Browse latest Browse all 12963

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>