Unable to backup System State on a 2008 R2 Server

Have a 2008 R2 SP1 Server, patched to the current state, and we can not perform a system state / BMR backup. The backup starts, VSS creation always succeeds, but between 30 and 80% (it's never at the same point) the backup fails with event 5, error 2147943567.
The eventlog message says the the problem should be in the "Details message":
I can not see the reason for the failure in the eventlog message above.
In Windows Server Backup, the logged error message is "a device is not connected".
The server is running on VMware and has just one virtual hard disk (drive C:) All other servers running on the same VMware plattform don't have this problem. Also, there are no warnings or errors in the system and application eventlog of the affected server.
Have also tried to run a backup with completely disabled Antivirus scanner, but the backup stops with the same error.
What can we do? Thank you all in advance for any advice.
Franz

Hi Mandy
Thank you for your feedback.
chkdsk c: /r doesn't find any errors.
Windows Backup is launched by the DPM Agent, so the backup destination will be a remote location (the DPM Server).
How can we "decrypt" the WindowsBackup Logfiles? When loading and converting these etl files into the event viewer, we get events with several event ID's with a text like "GUID=5e6a17c3-26e3-0585-9640-54fcebccd5d2 (No Format Information found)."
Thank you in advance for any further advice.
Kind regards, Franz

Similar Messages

  • SBS 2003 SP2: VSS errors; unable to create system state backup (NTBACKUP)

    NTBACKUP system state on W2k3 server fails after "thinking" for ~10 mins and "creating" shadow copy; almost no disk activity, almost no CPU load. Errors in the Application
    log:
    Source: SQLVDI EventID: 1
    Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=3392. Thread=29348. Client. Instance=. VD=Global\{9B35142B-C687-4766-9707-BC387534BA38}1_SQLVDIMemoryName_0. 
    Several of them.
    Then: 
    EventID: 8019
    Source: NTBackup
    End Operation: Warnings or errors were encountered. 
    Consult the backup report for more details.
    Then: 
    Source: VSS
    EventID: 12305
    Volume Shadow Copy Service error: Volume/disk not connected or not found. Error context: CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9,0xc0000000,0x00000003,...).
    And finally:
    EventID: 12293
    Source: VSS
    Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details PostFinalCommitSnapshots({de0d580b-68ce-4eae-a046-b5b5b7a80235}, 1) [hr = 0x80042308].
    When creating shadow copy on the system volume, the operation may take ~40-90 mins. On the data volume -- <1 min.
    "vssadmin list writers" shows:
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001 Microsoft Corp.
    Writer name: 'System Writer'
       State: [10] Failed
       Last error: Retryable error
    Writer name: 'SqlServerWriter'
       State: [10] Failed
       Last error: Retryable error
    Writer name: 'MSDEWriter'
       State: [1] Stable
       Last error: No error
    Writer name: 'FRS Writer'
       State: [10] Failed
       Last error: Retryable error
    Writer name: 'NTDS'
        State: [1] Stable
       Last error: No error
    Writer name: 'IIS Metabase Writer'
       State: [10] Failed
       Last error: Retryable error
    Writer name: 'Event Log Writer'
       State: [1] Stable
       Last error: No error
    Writer name: 'COM+ REGDB Writer'
       State: [1] Stable
       Last error: No error
    Writer name: 'Dhcp Jet Writer'
       State: [10] Failed
       Last error: Retryable error
    Writer name: 'Certificate Authority'
       State: [10] Failed
       Last error: Retryable error
    Writer name: 'WINS Jet Writer'
       State: [10] Failed
       Last error: Retryable error
    Writer name: 'Registry Writer'
       State: [1] Stable
       Last error: No error
    Writer name: 'Microsoft Exchange Writer'
       State: [1] Stable
       Last error: No error
    Writer name: 'TermServLicensing'
       State: [10] Failed
       Last error: Retryable error
    Writer name: 'WMI Writer'
       State: [10] Failed
       Last error: Retryable error
    Here is what I tried to do:
    1. Restarted that thing.
    2. Cleaned the security log.
    3. Installed Windows Server 2003 Hotfix rollup KB940349-v3.
    4. Stopped both SBSMONITORING and SHAREPOINT instances of MSDE, SQL 2005, SQL 2005 VSS and tried to perform the system state backup then. Stopped Exchange 2003 before launching NTBACKUP as well.
    5. "regsvr32 sqlvdi.dll" in MSDE directory.
    6. Renamed "System Volume Information" on all volumes and VSS has re-created them.
    7. chkdsk /f was fun on all volumes, no major issues found.
    8. Installed Hotfixes KB967551, KB975928-v2 (someone recommended).
    9. Disabled SQL Server VSS Writer (SQLVDI errors disappeared from the application event log, VSS and NTBACKUP errors stayed).
    10. Re-registered the DLLs as per Shaon Shan's post at http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/346fa42c-a476-457f-bcf3-59f87e444b55
    The above had no effect on the issue whatsoever, except a little change at item 9 as mentioned.

    Hi there.
    I just had that problem. I saw friday my backup from my sbs 2003, was not completing becasuse it said it couldn´t creat a shadow copy in the external drive... It kept giving me errors os VSS and Volsnap... But strange thing is, i have VSS turned off in all
    drives, and from months no problems with backups... So i went in Event viewer and look at it with attention, i saw a error that keep coming up from time to time (because we change the external drive form week to week). And i realize that there's a disk error
    event...
    Couldn´t run checkdisk from server, dont now why.. So i disconnected the drive, connected to my laptop, and ran a CheckDisk /F /X. ... It had BAD SECTORS! So i ran check disk... waited like 10-20 minutes. And then i ran it again just in case, and the 2nd
    time was much more faster, like 3-6 minutes. 
    I disconnected from laptop, and connected to server. I went to the Backup wizard (in server managment), and press Backup now... 
    It hang 5-10 second in Creating Shadow copy..... And it started making the Backup :_D
    I've seen all errors that were reported exactly as mine. I ran the Hotfix, all stayed the same, i followed all manual steps and still the same... and the problem was always in the external drive, which had bad sectors. 
    Hope it will help the next person that needs this info!

  • Event IDs 136 and 137 0x80000000000000 in System Log on Windows 2008 R2 Server, Exchange 2010 in Cluster

    Hi,
    I'm having an issue with one of my exchange 2010 Servers. We had a power outage and upon recovery, I cannot start Services Net.Pipe Listener Adapter and Net.Tcp Listener Adapter (And thus cannot Start IIS and provide Exchange Client Services.) This is a
    physical server (Not VMWare or Hyper-V)
    The System event log has lots of Event 136's and 137s on Ntfs with the keyword - 0x80000000000000 - The General Messages are: The default transaction resource manager on volume C: encountered an error while starting and its metadata was
    reset.  The data contains the error code.
    and
    The default transaction resource manager on volume OS encountered a non-retryable error and could not start.  The data contains the error code.
    XML Output as follows:
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Ntfs" />
      <EventID Qualifiers="32772">136</EventID>
      <Level>3</Level>
      <Task>2</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated
    SystemTime="2014-11-17T18:10:37.788942300Z" />
      <EventRecordID>315532</EventRecordID>
      <Channel>System</Channel>
      <Computer>server.domain.com</Computer>
      <Security />
      </System>
    - <EventData>
      <Data />
      <Data>C:</Data>
      <Binary>1C00040002003000020000008800048000000000060019C000000000000000000000000000000000060019C0</Binary>
      </EventData>
     </Event>
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Ntfs" />
      <EventID Qualifiers="49156">137</EventID>
      <Level>2</Level>
      <Task>2</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated
    SystemTime="2014-11-17T18:10:37.788942300Z" />
      <EventRecordID>315531</EventRecordID>
      <Channel>System</Channel>
      <Computer>server.domain.com</Computer>
      <Security />
      </System>
    - <EventData>
      <Data />
      <Data>OS</Data>
      <Binary>1C0004000200300002000000890004C000000000020100C000000000000000000000000000000000020100C0</Binary>
      </EventData>
      </Event>
    When I attempt to start the services - I get the following errors:
    The Net.Pipe Listener Adapter service depends on the Windows Process Activation Service service which failed to start because of the following error: 
    Transaction support within the specified resource manager is not started or was shut down due to an error.
    The Net.Pipe Listener Adapter service depends on the Windows Process Activation Service service which failed to start because of the following error: 
    Transaction support within the specified resource manager is not started or was shut down due to an error.
    I have tried the "fsutil resource setautoreset true" fix without success.
    Any ideas or direction would be much appreciated. Restoring this server will be extremely difficult.
    Thanks!

    We can close this question.
    From an elevated prompt, I ran 'fsutil resource setautoreset true' and attempted to remove the files with .blf and regtrans-ms file extensions from C:\Windows\System32\config\TxR. but these files were locked by system processes. (They are also
    tagged with the hidden file attrib so you may not see them at first)
    So, I booted the system with a Windows 2008 R2 Install Disk, selected repair OS and selected the command prompt. I then performed a chkdsk /f c: and selected "Y" to unmount the drive. It made some repairs.
    With the system booted from the install disk, and chkdsk executed, the locks were freed and I was able to delete the files from C:\Windows\System32\config\TxR.
    Once the system rebooted, the services came back fine and everything was back to normal.

  • Unable to list SFTP Directory on windows 2008 r2 server from internet

    Hi experts,
    I have configured a SFTP on windows 2008 r2 server. And i am using the Filezilla on client machine to connect to SFTP server.
    The connection works properly on internal network but it displays error when i connect from internet.
    Error: GnuTLS error -53: Error in the push function.
    Response: 550 Data channel timed out.
    Error: Failed to retrieve directory listing
    This machine is publish with public IP and port22. The connection and authorization process gets complete but stops are Directory Listing.
    PLease suggest the troublshooting steps..
    Let me know if any more info is rquired.

    Hi,
    Do you also use the Filezilla to configure SFTP server? Since you use Filezilla on client machine to connect to SFTP server, I would suggest you ask for help from Filezilla forums for better and accurate answer.
    https://forum.filezilla-project.org/
    Best Regards,
    Mandy 
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Has anybody had an issue with System State Backups on a Dell PowerEdge R510 Server running Server 2008 R2?

    Hi,
    We have recently had issues running system state backups on our 2008 R2 Domain Controllers.  They are running on Dell PowerEdge R510 Physical Hardware.  Whenever you initiate a system state backup,  the Domain Controller becomes unresponsive
    forcing us to physically reboot it.   Nothing in the Event logs or the Dell Open Management Hardware Software indicates issues with Phyiscal disks but we can always replicate the issue by starting the system state backup. 
    The system state backup is initialted as a batch file that runs as a scheduled task.   the commands run are as follows:
    WBADMIN START SYSTEMSTATEBACKUP -backupTarget:[drive letter] -quiet
    We have 4 Domain Controllers with identical disk configurations.  When the DCs were setup I confirmed the system state backups were working but the issue started occuring sometime in Dec 2014.  We are going to run the Dell Hardware Update Utility
    to update the RAID, BIOS, Firmware updates but Has anyone experienced a similar issue that may have been triggerd by a Microsoft Patch?
    Thanks,
    Kevin C.
    kconway@fnalgov
    

    Hi Kevin,
    This issue could be due to the Mountmgr.sys driver incorrectly maintains a global mutex. This behavior causes a deadlock situation in the Mountmgr.sys driver.
    Please install the hotfix in the article below to resolve the issue:
    A computer stops responding because of a deadlock situation in the Mountmgr.sys driver in running Windows 7 or in Windows Server 2008 R2 
    http://support.microsoft.com/kb/2614892
    Best Regards,
    Mandy
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Windows Server 2008 R2 - System State Backup - Application Log: CAPI2 513

    When performing a system state backup from wbadmin, I get...
    Creating a shadow copy of the volumes specified for backup...
    Creating a shadow copy of the volumes specified for backup...
    Please wait while system state files to back up are identified.
    This might take several minutes...
    Summary of the backup operation:
    The backup of the system state failed [12/15/2011 6:38 PM].
    Log of files successfully backed up:
    C:\windows\Logs\WindowsServerBackup\Backup-15-12-2011_18-38-05.log
    Log of files for which backup failed:
    C:\windows\Logs\WindowsServerBackup\Backup_Error-15-12-2011_18-38-05.log
    The operation ended before completion.
    The system writer is not found in the backup.
    In the event log, I get...
    Log Name: Application
    Source: Microsoft-Windows-CAPI2
    Date: 12/15/2011 6:38:24 PM
    Event ID: 513
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: Server1.domain.com
    Description:
    Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.
    Details:
    AddCoreCsiFiles : GetNextFileMapContent() failed.
    System Error:
    The parameter is incorrect.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-CAPI2" Guid="{5bbca4a8-b209-48dc-a8c7-b23d3e5216fb}" EventSourceName="Microsoft-Windows-CAPI2" />
    <EventID Qualifiers="0">513</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2011-12-15T23:38:24.430498600Z" />
    <EventRecordID>144157</EventRecordID>
    <Correlation ActivityID="{0450BC50-F800-0002-8457-553A80BBCC01}" />
    <Execution ProcessID="1240" ThreadID="4360" />
    <Channel>Application</Channel>
    <Computer>Server1.domain.com</Computer>
    <Security />
    </System>
    <EventData>
    <Data>
    Details:
    AddCoreCsiFiles : GetNextFileMapContent() failed.
    System Error:
    The parameter is incorrect.
    </Data>
    </EventData>
    </Event>
    The System Writer is not showing up when I view vssadmin list writers.
    I have already tried every tip in the following links:
    http://technet.microsoft.com/en-us/library/cc734021(WS.10).aspx
    http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/bb760434-de80-4cb6-ae9e-bd253e4b037c/
    I have also run sfc /scannow and rebooted.  No luck.
    I think the reason none of the tips at the above links work for me is that the System Error is NOT access denied like many others are getting, but is instead
    The parameter is incorrect.  I think that's the key.
    Any ideas why I am getting this error and why my System Writer is nowhere to be found?

    Hi,  
    You mentioned that “The System Writer is not showing up when I view vssadmin list writers.”
    you may reboot the related services or re-register the writers, please refer to:
    How to Re-register Volume Shadow Copy Service (VSS) Components on Windows 2008/Windows 2003.
    http://www.symantec.com/business/support/index?page=content&id=TECH70486
    Best regards,
    Jeff Ren
    Please 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.

  • Windows Server 2008 R2 System State Backup fails "the parameter is incorrect"

    Hi,
    I'm having the same problem as I've found in a few other threads.
    http://social.technet.microsoft.com/forums/en-us/windowsbackup/thread/C633B2E6-1161-4146-BC09-C2712231F0EE
    and
    http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/0b0f2d9c-e3b1-4f85-a6d2-2e15e5a15bc1
    I've tried running the vshadow.exe -wm2 > out.txt command and searching the output for invalid paths, but I can't seem to find any paths that looks incorrect.
    I've also done a registry search under HKLM\CurrentControlSet\Services for the / character and didn't come up with any in any paths either.
    The server is a pretty new install. DC, DNS, DHCP, File and Print services. It has been running in production for about a week for a small business. Their previous server desperately needed changing over, so it got pushed in fairly quick. I never assumed
    I would have had trouble with the system state backing up!. It would be nice to get it working so I can sleep at night :). The old DC is still running, so all is not lost in a failure, but still... I guess also once I've demoted the old DC, I can restore AD
    just by restoring the entire system image (Don't have to worry about USN sync if only single DC), but I would still like a system state backup.
    Thanks, Ryan

    Hi,
    Try to apply the following hotfix.
    System state backup error in Windows Server 2008, in Windows Vista, in Windows 7 and in Windows Server 2008 R2: "Enumeration of the files failed"
    http://support.microsoft.com/kb/980794
    You may have to restart the computer after you apply this hotfix.
    Jeff Ren TechNet Community Support beneficial to other community members reading the thread.

  • Error [0x8007007b] when backing up system state in windows backup for windows 2008 R2

    running wbadmin system state results in the following error log:
    Error in backup of C:\windows\\systemroot\ during enumerate: Error [0x8007007b] The filename, directory name, or volume label syntax is incorrect.
    Having searched all over the web, the consensus seems to be that this error means that some service has a bad image path. I even sound a nifty powershell script that discovers services with possible problems. I fixed the problems it brought up in the registry
    (there was only one), but I still get that error... I've been backwards and forwards through the list of services many times, and I don't see any problems.. Anybody got an idea??

    Hi, 
    The issue cause by the following aspects:
    1. The path incorrectly points to Windows\\systemroot\system32\drivers
    2. Multiple SCSI controller drivers are being loaded at boot time and one or more is not needed. The failing SCSI controller driver is creating an issue for the WBAdmin/VSS backup process.
    To resolve this issue, change the value in the registry key for
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LSI_SAS and change the Imagepath, from \SystemRoot\system32\drivers\lsi_sas.sys to System32\drivers\lsi_sas.sys 
    Note: After making above registry changes, the machine might not boot normally. Follow below mentioned steps to recover from the boot issue.
    1. Boot the machine into Windows Recovery Environment (WinRE).
    2. Open Regedit and navigate to each of the following registry keys to verify their Start values are correct.
    HKLM\System\CurrentControlSet\service\LSI_FC
    HKLM\System\CurrentControlSet\service\LSI_SAS
    HKLM\System\CurrentControlSet\service\LSI_SAS2
    HKLM\System\CurrentControlSet\service\LSI_SCSI
    3. The Start value should be 0x3 for each driver that is NOT the SCSI controller driver determined earlier. Change the Start value as needed. 
    Values and meanings for the Start value: 
    0x0 = Load on boot 
    0x1 = System 
    0x2 = Auto Load 
    0x3 = Load on demand 
    0x4 = Disabled
    4. Reboot the machine in normal mode.
    5. Re-run the WBAdmin command, the backup should work correctly.
    Regards, 
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • How to Delete Non-System State Backups in Windows 2008R2

    Hello,
    I am running a Windows 2008R2 server which uses Windows Server Backup to do the backups. We are using the backup-tool to create non-system state backups of the data-directories on this machine. The backup is done on a dedicated disk connected through iscsi
    (to a Synology box). This backup disk has become too small and we have now replaced the Synology box with a bigger one. Here i created a new LUN again for the backup purposes.
    Now for my question; The wbadmin.exe tool supplied with W2008R2 does not offer a way to delete the old backups. I know that in Win2012 (which we we also have running) I could add the new iscsi location and then (when enough backups are available on the new
    target) use wbadmin.exe delete backup  to delete the old non-system state backups; e.g.
     wbadmin delete backup -version:08/07/2013-21:00
    This (very undocumented) feature of Windows 2012 and higher works quite nice and is exactly what i am searching for on the W2008R2 machine; a way to delete the old backups (and under the hood delete the corresponding snapshots)
    I've done quite a bit of research and it should be possible to do something similar in 2008 but then manually, The howto is described in the following link: http://blogs.technet.com/b/filecab/archive/2009/06/22/backup-version-and-space-management-in-windows-server-backup.aspx .
    Basically it describes that you should use DiskShadow.exe to remove e.g. the oldest snapshot with a  command like :
    Delete shadows OLDEST \\?\Volume{7fc1871b-2e1f-11dd-a339-001e4fb7af35}
    Windows Server backup (wbadmin) should then on the next run 'see' this deletion and update its list of available backups:
    "You can perform the same steps manually to delete backups on demand. However, the backup catalog update cannot be done manually and it will happen instead during
    the next backup."
    I've done this on our box and it indeed removes the shadows from the list. However, in the Windows Backup 'dashboard' it still lists the backups as available. Also after a new backup has finished (according the the article this is when it should 'update'
    its backup catalog). When I try to restore a backup from a date that i just removed it gives a nice message that this is impossible because the snapshot is not available (duh :)) ;
    Unable to browse Local disk. The shadow copy of the backup stored on the backup destination cannot be found.
    So it seems that the aforementioned method works; it removes the snapshot and frees diskspace, but it doesn't update the Windows Backup catalog. As a result the management tool (GUI) still lists the backups which are no longer available! How can i change
    this? Is there any way to do this? I found one article which mentions that the Dashboard bases its screen on the Windows Logs and not on the actual VSS snapshots available:
    http://forum.wegotserved.com/index.php/topic/23757-start-afresh-with-server-backup/ (WHS) In my situation however this seems unlikely because i don't have any logs that date back as far as my backups go.
    In my opinion this is a real bug and it leaves us with a in-consequent backup schema. Does anyone have similar situations or even a solution to my problem?
    Kind Regard, Martin

    Hi Mandy,
    Yes! I think i got my answer and I now get how windows backup works in Windows 2008 :-) It turns out that I dismissed some suggestions a bit too soon. The answer lies in the command mentioned earlier : 
    Wbadmin delete catalog
    This command does delete all the backups from a perspective of the Windows Backup UI, but leaves the VSS snapshots intact. This means that the backups are still available, but you just can't restore them with the User Interface. In order to 'update' the
    UI with the current available snapshots (which you can list with diskshadows list shadows all), you have to re-add the existing media on which the backups took place using the Wizard of the UI. It will then inform you that existing backups are available and
    if you want to keep these for restore purposes. If you click 'yes', and THEN perform a backup ... All the current available backups will be shown in the User Interface :-) 
    So for my steps taken to change from one iscsi (iscsi1) to another (iscsi2):
    - Add the 2nd iscsi target with the Windows Backup UI
    using Backup schedule , Modify backup -> [desired options] => Add more backup destinations -> iscsi2
    - Remove the 1st iscsi target with the Windows Backup UI
    using Backup schedule , Modify backup -> [desired options] => Remove current backup destinations -> iscsi1
    - Run some backups on the new destination. Old restore points are now still available. When enough restore points are available on the new volume iscsi2 start deleting old data from iscsi1 as follows:
    - Run diskshadow
    diskshadow
    - list all the current snapshots
    list shadows all
    - remove all the snapshots of iscsi1  (repeat until all shadows are gone of iscsi1)
    delete shadows oldest \\?\volume{yourvolumeid}\
    - delete the windows backup catalog
    wbadmin delete catalog
    - Restart the windows backup UI and re-add your schedule on the new volume iscsi2. It will now ask if you want the keep the existing data for restore purposes; click yes. 
    - After the next backup only the backups of volume iscsi2 will be listed and everything is fine ! 
    I Hope my post will help others with similar questions. It was quite a search before I understood the way it works. Basically as long as your VSS snapshots are still available and listed by diskshadow you still have the backups and you will be able to get
    this in sync with the steps above (delete schedule and re-add originating targets containing the snapshots). After the next backup the UI will update itself. 
    (In my case someway along the way I lost my originating snapshots, but because I already had my new backup set it didn't bother me; It kept me from having to delete all 510 old backups :) with diskshadow)
    Regard, Martin

  • System State Backup fail. Writer name: 'NTDS' : State: [11] Failed : Last error: Non-retryable error

    Hello!!! Everybody,
    I have Win Server 2008 R2 contain Domain controller (No Hyper-V). I have to take "SYSTEM STATE DATA BACKUP". I have ran following command on this Server.
    c:\>wbadmin start systemstatebackup -backuptarget:d:
    but backup was not successful & I got following error in command prompt.
    " A VOLUME SHADOW COPY SERVICE OPERATION HAS OCCURRED : <0X800423f4>. THE WRITER EXPERIENCED A NON-TRANSIENT ERROR. IF THE BACKUP PROCESS IS RETRIED,THE ERROR IS LIKELY TO REOCCUR."
    I also ran following command to know exact problem.
    c:\>vssadmin list writers
    I got following error
    Writer name: 'NTDS'
       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
       Writer Instance Id: {21c57902-5037-467b-b9a3-72ed41c9723e}
       State: [11] Failed
       Last error: Non-retryable error
    I also checked Event Viewer & got following 3 noserror.
    (1) Event ID : 8229, Source : VSS
    A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried, the error is likely reoccur.
    Process ID : 608
    (2) Event Id : 412, Source : ESENT. Task Category: Logging/Recovery
    lsass (636) Unable to read the header of log file "\\?\Globalroot\device\harddiskvolumeshadowcopy2\Windows\NTDS\edb.log".Error:546
    (3)Event Id : 521 Source : Backup
    The backup operation that started at  '‎2014-‎05-‎13T01:44:31.444000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review
    the event details for a solution, and then rerun the backup operation once the issue is resolved.
    I have also restart the server but problem is not resolved. I have no SQL in my Server.
    I also re-register the VSS components with the help of following website.
    Website Link :  https://kb.acronis.com/content/45776
    You are requested please solve my problem on very urgent basis.

    You can refer below link for your issue
    http://waynestorey.com/blog/2012/01/18/windows-backup-fails-with-event-id-521-error-code-2155348129/
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical | Twitter:
    Mai Ali

  • Wbadmin System State Backup "Parameter is incorrect"

    Hello,
    We have two physical Windows Server 2008 R2 x64 Standard Domain Controllers and the system state backup on both fails with the same error.
    We issue the command:
    wbadmin start systemstatebackup -backuptarget:c:
    (NOTE: We did the REG fix to allow backups to the system volume)
    and we get  this as the output:
    C:\Windows\system32>wbadmin start systemstatebackup -backuptarget:c:
    wbadmin 1.0 - Backup command-line tool
    (C) Copyright 2004 Microsoft Corp.
    Starting to back up the system state [28/02/2010 21:26]...
    Retrieving volume information...
    This will back up the system state from volume(s) System(C:) to c:.
    Do you want to start the backup operation?
    [Y] Yes [N] No y
    Creating a shadow copy of the volumes specified for backup...
    Creating a shadow copy of the volumes specified for backup...
    Please wait while system state files to back up are identified.
    This might take several minutes...
    Summary of the backup operation:
    The backup of the system state failed [28/02/2010 21:27].
    Log of files successfully backed up:
    C:\Windows\Logs\WindowsServerBackup\Backup-28-02-2010_21-26-31.log
    Log of files for which backup failed:
    C:\Windows\Logs\WindowsServerBackup\Backup_Error-28-02-2010_21-26-31.log
    The operation ended before completion.
    The parameter is incorrect.
    C:\Windows\system32>
    This happens on both servers and the two backup log files mentioned in the output are both empty.
    There's no other information that I can find so I don't know what the "parameter" is or why it is incorrect.
    Has anyne come across this problem and know what the error is referring to?
    Thanks
    Sunil

    I received a PowerShell script from Suhas and ran it on the affected server, the script output gave:
    1.
         Service Name    : RMAGENT
         Service Caption : RMAGENT
         Registry key    : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\RMAGENT\ImagePath
         Value           : \\PRIMARY\admin$\Microsoft DPM SRT\RFCAgent.exe
         Reason          : The service path contains a double slash. Network paths or paths containing a double slash are not supported.
    2.
         Service Name    : RMAGENT
         Service Caption : RMAGENT
         Registry key    : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\RMAGENT\ImagePath
         Value           : \\PRIMARY\admin$\Microsoft DPM SRT\RFCAgent.exe
         Reason          : The service path does not have a proper path format. Only paths beginning with [<Drive>]:\ format are supported.
    The "RMAgent" is from Microsoft Data Protection Manager 2007 System Recovery Tool (DPM-SRT) and I think is the remote agent that DPM-SRT uses to backup the remote system.
    The DPM-SRT RMAgent isn't supported and doesn't work on Windows Server 2008 R2 systems and I am not sure how it ended up installed on the server. Removing this service should solve the problem and allow the System State Backups to work. The DPM-SRT agent wasn't listed in the "Programs and Features" and so couldn't be installed from there (if it was I would have spotted this a long time ago and probably solved the problem). Instead, I used the information at:
    http://www.howtogeek.com/howto/windows-vista/how-to-delete-a-windows-service-in-vista-or-xp/
    To delete the RMAgent service: sc delete "RMAgent" in an Administrator CMD prompt. This removed the registry entries shown in the script output above. When this was done, I ran the script again just to be sure there was nothing else and indeed the RMAgent entries had gone and there were no other items that needed attention.
    Finally, I tried "webadmin start systemstatebackup -backuptarget:C:" again in an administrator CMD prompt and it completed successfully.
    I would like to thank Abhinav Mathur and Suhas Rao in particular for their very helpful script.
    Sunil

  • DPM 2012 R2 CU 4 - issue w/ system state backup completing on non domain servers with T2embed.dll

    I am really new to DPM and just took over a system that has servers being backed up that are not part of the domain. The volumes backup fine and system state will not complete. In looking at the protection group server the WindowsImageBackup folder is created
    and the backup starts however it will fail and DPM server will say Replica is inconsistent.  Back on the protected server in the backup event log, it fails w/ error code 2155347997.  In the backup error log file in C:\windows\logs\windowsserverbackup. 
    It says "Error in backup of C:\windows\system32\t2embed.dll during read.  Error [0x80070005] Access is denied.
    We have about 4 other servers that are not domain joined and they are getting similar errors w/ t2embed.dll in that system32 directory or in the WinSXS folder.   All servers are 2008 SP2 or 2008 R2 SP1.
    Thank you in advance for you help

    Hi,
    DPM has no control over errors that Windows server backup receives, but check permissions and Remove the DENY permission for EVERYONE on the below files:
    C:\Windows\system32\t2embed.dll
    C:\Windows\winsxs\amd64_microsoft-windows-font-embedding_31bf3856ad364e35_6.1.7601.17514_none_13e628b635935244\t2embed.dll
    C:\Windows\winsxs\x86_microsoft-windows-font-embedding_31bf3856ad364e35_6.1.7601.17514_none_b7c78d327d35e10e\t2embed.dll
    Please 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. Regards, Mike J. [MSFT]
    This posting is provided "AS IS" with no warranties, and confers no rights.

  • Windows 2012 System State Backup Fails

    We have a Windows 2012 Domain Controller VM that we would like to backup the System State using DPM. Agent has been installed and the Windows Backup has been added.
    When the backup runs in DPM, the job fails. Here is the error code:
    DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 517, WSB Error Code:  0x12363C0). (ID 30229 Details: Internal error code: 0x80990ED0)
    When we try and create the backup using Windows Backup, the following error is in the log file:
    following error code '0x807800C5' (There was a failure in preparing the backup image of one of the volumes in the backup set.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
    We have tried attaching a separate drive and backup to a shared location. Both fail.
    We have tried backup of just a few files on the DC instead of the System State, this fails as well.
    All VSS Writers show as Stable with no errors
    Server has the latest updates
    Server has been rebooted, same issue
    VM is Windows 2012 on a Windows 2008 R2 clustered host and is using Dynamic Disks (not fixed disks).
    Anyone have any thoughts on what could be going on?

    Hi,
    If any of the following are true, you will not be able to backup a system state to that volume.
    • Make sure that the target volume has no shadow copy before the backup starts.  
    • If a system state backup is stored on a source volume, backup settings should be configured for full backups. By default, settings are configured for full backups.  
    • Periodically check that no other user or program maintains a shadow copy on the target volume.  
    • Do not keep volume level backups and system state backups in the same location.  
    • The volume used to store the system state backup needs twice the amount of free space as the size of the system state backup until the backup completes
    Meanwhile please check if it is caused that you are backing up to a critical drive. Try modify the following key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wbengine\SystemStateBackup\ 
    Set the value of this entry as follows: 
    Name: AllowSSBToAnyVolume 
    Data type: DWORD 
    Value data: 1 
    If you have any feedback on our support, please send to [email protected]

  • Failed system state backup on Passive Node

    I have a Windows Server 2012 R2 cluster that has a service that is installed on shared storage.  On the passive node, the system state backups are failing because the path to the service executable does not exist.    KB980794 existed
    for Server 2008, which contained a hotfix and a registry key that could be added to exclude the paths to binaries that should not be included in the system state backup. 
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SystemWriter\ExcludedBinaryPaths
    Is there a similar method of excluding these paths in Windows Server 2012 that will allow the VSS snapshot to execute successfully?

    Hi,
    Thanks for your posting.
    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
    Thank you for your understanding and support. 
    Best Regards,
    Mandy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • System state synchronizations and express full backups of protected 2012 R2 machines overload DPM server.

    I have one DPM 2012 R2 UR2 server which is running on Windows 2008 R2 and 2 protection groups (A, and B). The server uses direct attached storage for all replicas and recovery volumes.
    Group A protects the system state and bare metal recovery of 25 Windows 2008R2 servers. It creates recovery points using express full backup each night at 6PM. The servers range from file/print, SQL, domain controllers, terminal servers, web servers, etc. Total
    data 3TB.
    Group B protects the system state and bare metal recovery of only 3 Windows 2012R2 servers. It creates recovery points using express full backup each night (morning) at 1AM. The servers are 1 domain controller, 1 WSUS server, and 1 server that runs VMware VCenter.
    Total data 90GB.
    During group A's nightly backup, which takes approximately 2 hours, the DPM server becomes noticeably slower but remains functional. I can open Windows update and check for updates, copy files to and from network locations, launch intenet explorer, etc. It's
    stressed since 25 servers are creating backups on it but it remains functional.
    During group B's nightly backup the DPM server grinds to a complete halt. Launching internet explorer takes an hour (literally), 10 minutes will pass before I get a menu after clicking the start button. Basically it becomes completely unresponsive until the
    backups finish which typically doesn't happen because I'm forced to cancel them upon arriving at work...8 hours later.
    I read that DPM uses the built in Windows Backup to protect system state and bare metal recovery. Did something change in Windows Backup from 2008R2 to 2012R2 that would cause this? Why can my DPM server easily backup 25 Windows 2008R2 machines at once in 2
    hours yet freezes solid for 8 hours or more when backing up only 3 Windows 2012R2 machines?
    I left performance monitor running during the night and it showed an average disk queue length of 49 during group B's backup but everything else was normal. Seems the disks on the DPM server are the bottleneck but again I ask why can my DPM server easily backup
    25 Windows 2008R2 machines at once in 2 hours yet freezes solid for 8 hours or more when backing up only 3 Windows 2012R2 machines? Both protection groups use the same disks.
    How can I fix this?
    Teenage angst has paid of well, now I'm bored and old.

    Hi CS,
    You can also run a performance monitor.
    For some basic perfmon counters to help narrow down the possible bottleneck:
    Perf Counters for DPM
    Logical Disk/Physical Disk
    \%idle
    • 100% idle to 50% idle = Healthy
    • 49% idle to 20% idle = Warning or Monitor
    • 19% idle to 0% idle = Critical or Out of Spec
    \%Avg. Disk Sec Read or Write
    • .001ms to .015ms  = Healthy
    • .015ms to .025 = Warning or Monitor
    • .026ms or greater = Critical or Out of Spec
    Current Disk Queue Length (for all instances)
    80 requests for more than 6 minutes.
    • Indicates possibly excessive disk queue length.
    Memory
    \Pool Non Paged Bytes*
    • Less that 60% of pool consumed=Healthy
    • 61% - 80% of pool consumed = Warning or Monitor.
    • Greater than 80% pool consumed = Critical or Out of Spec.
    \Pool Paged Bytes*
    • Less that 60% of pool consumed=Healthy
    • 61% - 80% of pool consumed = Warning or Monitor.
    • Greater than 80% pool consumed = Critical or Out of Spec.
    \Available Megabytes
    • 50% of free memory available or more =Healthy
    • 25% of free memory available = Monitor.
    • 10% of free memory available = Warning
    • Less than 100MB or 5% of free memory available = Critical or Out of Spec.
    Processor
    \%Processor Time (all instances)                                                                  
    • Less than 60% consumed = Healthy
    • 51% - 90% consumed = Monitor or Caution
    91% - 100% consumed = Critical
    Please 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. Regards, Mike J. [MSFT]
    This posting is provided "AS IS" with no warranties, and confers no rights.

Maybe you are looking for