none
Windows Server 2008 Backup Failure

    Question

  • I have freshly installed system running Windows Server 2008 Standard configured to run AD/DHCP/DNS/File/Print/IIS/WSUS

    I am trying to run an initial 'Backup Once' to get a full system backup of the current state.

    Each time I have tried to run the backup I get a failure with the Event ID 521 - error code 2155348129.

    Having searched the support forums I have found several cases where this error occurs, but none that seem to match my exact case.

    Please advise if I have missed anything already covered based on my case details.

    My Case Details:

    This server has a single 2TB hard disk with 1 volume which is has the status:
    (System, Boot, Page File, Active, Crash Dump, Primary Partition)

    I am using a 160GB USB external hard disk as the backup target.

    When running the backup I have noticed the following events/symptoms each time:

    • Event log (source: ESENT, Event ID: 412)
      lsass Unable to read the header of logfile
      \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2\Windows\NTDS\edb.log. Error - 546
    • Each time after the backup fails I run vssadmin list writers I find that Writer name: 'NTDS' has failed with Non-retryable error. Performing a reboot clears this error only for it to fail again after each backup attempt.
    • There is an error that doesn't seem to correspond with the failed backup attempts but it may be relevant: (source: CAPI2, Event ID: 513)
      Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.
      Details:
      AddCoreCsiFiles : BeginFileEnumeration() failed.
      System Error: Access is denied.
    • I have also noticed that corresponding with each attempt to backup there is a Directory Service error (source: ActiveDirectory_DomainService, Event ID: 1168)
      Internal error: An Active Directory Domain Services error has occurred.Additional Data
      Error value (decimal): -546
      Error value (hex): fffffdde
      Internal ID: 160207ce
    Thursday, December 20, 2012 3:24 AM

Answers

  • Found the answer.

    Ran Hotfixes KB2553708 & KB2470478 and now it works.

    Turns out on server 2008 some ESENT applications can have difficulty with hard disks that have 4k blocks (Advanced Format) and these hotfixes resolve this issue.

    Thursday, December 27, 2012 4:04 AM

All replies

  • Did you have installed SP2 on the server?

    Run vssadmin list writers and post the output here.

    Run chkdsk C: and then reboot the server.

    Do the above steps and report back the result.


    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, December 20, 2012 5:20 AM
  • The OS was fully patched before any attempt to backup was made, yes SP2 is installed.

    *********vssadmin list writers output**********

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {4fd17142-7c93-4198-8d29-292e1d3a2604}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'FSRM Writer'
       Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
       Writer Instance Id: {df00127c-7c4d-49d4-b6c4-dabc404f87e7}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {340bdc04-7e51-42c6-8dc0-ea62264fd3a6}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {7fda176d-7790-4bb3-9390-437e893e322b}
       State: [1] Stable
       Last error: No error

    Writer name: 'DFS Replication service writer'
       Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
       Writer Instance Id: {c768f983-db2e-46ff-a69d-8fd348bcbe48}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'NTDS'
       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
       Writer Instance Id: {8bf4c6c1-8851-4801-9e82-914dc4a43f17}
       State: [11] Failed
       Last error: Non-retryable error

    Writer name: 'Dhcp Jet Writer'
       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
       Writer Instance Id: {1a29ded3-f065-459e-a431-dccef0df1d2a}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {b9a3de81-d3e9-44e0-8814-2b962156a2b9}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {129a456c-d5a9-46b2-85b6-e97ff7ec48f8}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {94725b9a-7216-4e3f-b241-adae4c69621b}
       State: [1] Stable
       Last error: No error

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {c13a691d-c9ab-45a3-be7b-c90d806f6ff9}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {fd3dc0b5-3a6a-4d42-839d-5107250a7b1a}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {df3a35a5-f41d-42c4-9728-e10a6bcde702}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {8fa48dfe-c9be-474c-b85c-cdacfc5ef018}
       State: [1] Stable
       Last error: No error

     

     *******End of Output*********

    Ran chkdsk C: ... no errors reported
    rebooted the server and tried once more, same result.

    Note that I appear to have resolved the issue with CAPI2 reported in my original post using instructions from another thread, but this hasn't affected the result of my backup operation.

    Thursday, December 20, 2012 6:09 AM
  • Try the following hostfix and report back the result:

    http://support.microsoft.com/kb/970770


    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, December 20, 2012 6:34 AM
  • Yes, I had already installed that hotfix before creating this thread...
    Thursday, December 20, 2012 6:40 AM
  • Try disabling SQL Server Writer, rebooting the server and reporting back the result...

    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, December 20, 2012 6:42 AM
  • Just tried with SQL Server Writer stopped, same result, still getting the corresponding ESENT error and the NTDS Writer has failed again.
    Thursday, December 20, 2012 9:58 PM
  • Just an update..

    I have just tried another backup after demoting the server from DC and rebooting. The backup worked 1st time.

    I am going to remove the AD role all together then re-add it and re-promote to DC and see if the backup works after that. My hunch is that there was some kind of corruption in the shadow copy for NTDS.

    Will advise on the results.


    Wednesday, December 26, 2012 11:48 PM
  • Same result..

    After performing the actions in my previous post, still exactly the same outcome/symptoms as previously found.

    So in a nut shell, when the server is promoted as a domain controller the backup fails, when it is demoted the backup works fine.

    Thursday, December 27, 2012 12:42 AM
  • Found the answer.

    Ran Hotfixes KB2553708 & KB2470478 and now it works.

    Turns out on server 2008 some ESENT applications can have difficulty with hard disks that have 4k blocks (Advanced Format) and these hotfixes resolve this issue.

    Thursday, December 27, 2012 4:04 AM
  • Congratulations!

    Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Thursday, December 27, 2012 5:10 AM
  • Thanks for sharing your solution.
    Monday, December 31, 2012 1:21 AM
  • Thanks
    Tuesday, June 18, 2013 11:45 PM
  • I was in a trouble for 15 days. i was not able to take backup of my server 2008. had many error or vss and ad ds was also generating many errors. i tried enormous troubleshooting steps. 

    Finally its solved with above hoxfixes.

    Thank you very much.

    Wednesday, August 14, 2013 11:21 AM
  • Hi All, 

    I had met with the  same error for one of domain controller the while the NTDS writer was showing  the error
    Writer name: 'NTDS'
    State: [11] Failed
    Last error: Non-retryable error 

    so  i had found the cause  of the error here Extensible Storage Engine API ( ESENT)

    after searching i have  got  hot  fix  from MS Windows6.1-KB982018-v3-x64, 

    i have installed this hot fix and  after a reboot NTDS writer came stable and successfully completed the backup 

    https://support.microsoft.com/en-us/help/982018/an-update-that-improves-the-compatibility-of-windows-7-and-windows-ser

    Hope this  helps !!

    Tuesday, October 17, 2017 4:59 AM