Reputation
Top tag
Next privilege 50 Rep.
Comment everywhere
Badges
5
Newest
 Supporter
Impact
~149 people reached

  • 0 posts edited
  • 0 helpful flags
  • 1 vote cast
Feb
23
awarded  Scholar
Feb
23
awarded  Supporter
Feb
23
accepted Unable to restore (error 3456)
Feb
23
comment Unable to restore (error 3456)
thanks so very much for your super-informative answer.
Feb
22
comment Unable to restore (error 3456)
Thomas - the db was online until just prior to step 13. However it was in RESTRICTED_USER so that no app activity could occur. I will have to check with management to verify if it's ok to share the .mdmp. Thanks again for your help.
Feb
22
comment Unable to restore (error 3456)
Robert - thanks so much for your reply. Timeline: Feb 6th, 9:45pm copy only full backup Feb 7th, 2:11 pm, first tlog backup Feb 7th, 2:47 pm, second tlog backup Anything further I might do or research to determine why this happened? As I mentioned above, I executed these steps without issue on a different db. My manager is thinking of opening a support case with MS, but I'm not sure much would be revealed by doing that. Corrupt is corrupt. The question is why.
Feb
21
comment Unable to restore (error 3456)
Verified that each backup has CHECKSUM enabled.
Feb
21
comment Unable to restore (error 3456)
I forgot to mention that applying the 2nd tlog backup caused a stack dump in the SQL error log.
Feb
21
comment Unable to restore (error 3456)
I did verify that the full db backup had 0 errors by running CHECKDB. I will have to check to see if CHECKSUM was used.
Feb
21
awarded  Editor
Feb
21
revised Unable to restore (error 3456)
edited title
Feb
21
comment Unable to restore (error 3456)
Thanks for your reply, Thomas. I see now that the title of my post was incorrect. I don't need a point in time recovery, but a full restore to the end of the 4th tlog backup. So setting BULK_LOGGED should not have caused any issues with that. I don't see how what I did would have caused the 2nd tlog backup to fail - all commands were supported by SQL Server, and I ran the exact same steps (although not on the same data) on a smaller database, and was able to restore the 2nd tlog backup without issue.
Feb
21
awarded  Student
Feb
21
asked Unable to restore (error 3456)
Jun
17
awarded  Informed
Jun
17
answered Find procedures that haven't been called in <n> days