none
Windows Server Backup Completed with warnings RRS feed

  • Question

  • We have a server running Windows Server 2016 Essentials with Windows Server Backup backing up to a WD My Passport external hard drive. Over the past year, we've seen random warnings where backups were "Completed with warnings" and the bare metal restore portion failed. These warnings happen inconsistently from once a month to several times a month (6 times last month). We don't see any patterns that cause it to fail or succeed. There aren't any other scheduled tasks or backups running during this time.

    The eventlog has several errors at the backup time:

    1. Source: DeviceSetupManager Event ID: 131 - Metadata staging failed, result=0x8007000D for container '{00000000-0000-0000-FFFF-FFFFFFFFFFFF}'

    2. Source: VSS Event ID: 8229 - 

    A VSS writer has rejected an event with error 0x800423f2, The writer's timeout expired between the Freeze and Thaw events.
    . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. 
    
    Operation:
       Thaw Event
    
    Context:
       Execution Context: Writer
       Writer Class Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Name: Registry Writer
       Writer Instance ID: {f2595c5a-ccdf-4122-aa1e-d7fff661237e}
       Command Line: C:\Windows\system32\vssvc.exe
       Process ID: 7764

    3. Many Source: SPP errors Event ID: 16389

    Writer System Writer experienced retryable error during shadow copy creation. Retrying...  More info: .
    
    Writer ASR Writer experienced retryable error during shadow copy creation. Retrying...  More info: .
    
    Writer Shadow Copy Optimization Writer experienced retryable error during shadow copy creation. Retrying...  More info: .
    
    Writer FRS Writer experienced retryable error during shadow copy creation. Retrying...  More info: .
    
    Writer Registry Writer experienced retryable error during shadow copy creation. Retrying...  More info: .
    
    Writer COM+ REGDB Writer experienced retryable error during shadow copy creation. Retrying...  More info: .
    
    Writer MSSearch Service Writer experienced retryable error during shadow copy creation. Retrying...  More info: .
    
    Writer Windows Server Storage VSS Writer experienced retryable error during shadow copy creation. Retrying...  More info: .
    
    Writer WMI Writer experienced retryable error during shadow copy creation. Retrying...  More info: .
    
    Writer Certificate Authority experienced retryable error during shadow copy creation. Retrying...  More info: .
    
    Writer NTDS experienced retryable error during shadow copy creation. Retrying...  More info: .
    
    Writer IIS Config Writer experienced retryable error during shadow copy creation. Retrying...  More info: .
    
    Writer Dhcp Jet Writer experienced retryable error during shadow copy creation. Retrying...  More info: .
    
    Writer IIS Metabase Writer experienced retryable error during shadow copy creation. Retrying...  More info: .

    4. Source: Disk  Event ID: 51 - An error was detected on device \Device\Harddisk2\DR133 during a paging operation.

    5. Many Source: FilterManager Event ID: 3 - Filter Manager failed to attach to volume '\Device\Harddisk2\DR134'.  This volume will be unavailable for filtering until a reboot.  The final status was 0xC03A001C.

    We tried the following without success:

    1. Replacing backup drive
    2. Increase freeze-thaw timeout per https://success.solarwindsmsp.com/kb/solarwinds_backup/Error-VSS-error-0x800423f2-The-writer-s-timeout-expired-between-the-Freeze-and-Thaw-events?q=VSS%20error%200x800423f2

    Any help would be appreciated, thanks.

    Wednesday, November 13, 2019 10:51 PM

All replies

  • Simply you can restart the server.

    But try below troubleshooting steps too,

    Find the failed VSS writers and their associated services, and restart them:

    1. Click the Start button then type CMD. When the command prompt icon appears, right-click it and select Run as Administrator.

    2. Type vssadmin list writers to find each of the VSS writers in a failed state. If the command hangs and does not return any output, this suggests the Volume Shadow Copy service or one of its dependent tasks might be in a bad state, causing the VSS writer audit to fail.

    Figure 1: Admin command prompt (click to enlarge)

    3. Restart the service to clear the failed state. If the service will not restart, reboot the production machine.

    4. Make a list or take a screenshot of all failed VSS writers.

    5. Find the VSS writer's associated Service Display Name in the table below and restart the service.

    Figure 2: Failed VSS Writer (click to enlarge)

    6. Open services.msc and stop any VSS related services that are running.

    7. Re-run the command vssadmin list writers in an administrative command prompt to confirm the state has changed to Stable with no errors.

    Figure 3: Stable VSS writer (click to enlarge)

    7. Try another backup. If the VSS writers fail again, you must reboot the machine.

    VSS Writer Service Name Service Display Name
    ADAM $instanceName Writer ADAM_$instanceName $instanceName
    ASR Writer VSS Volume Shadow Copy
    BITS Writer BITS Background Intelligent Transfer Service
    Certificate Authority CertSvc Active Directory Certificate Services
    COM+ REGDB Writer VSS Volume Shadow Copy
    DFS Replication service writer DFSR DFS Replication
    DHCP Jet Writer DHCPServer DHCP Server
    FRS Writer NtFrs File Replication
    FSRM writer srmsvc File Server Resource Manager
    IIS Config Writer AppHostSvc Application Host Helper Service
    IIS Metabase Writer IISADMIN IIS Admin Service
    Microsoft Exchange Replica Writer MSExchangeRepl Microsoft Exchange Replication Service
    Microsoft Exchange Writer MSExchangeIS Microsoft Exchange Information Store
    Microsoft Hyper-V VSS Writer vmms Hyper-V Virtual Machine Management
    MSMQ Writer (MSMQ) MSMQ Message Queuing
    MSSearch Service Writer WSearch Windows Search
    NPS VSS Writer EventSystem COM+ Event System
    NTDS NTDS Active Directory Domain Services
    OSearch VSS Writer OSearch Office SharePoint Server Search
    OSearch14 VSS Writer OSearch14 SharePoint Server Search 14
    OSearch15 VSS Writer OSearch15 SharePoint Server Search 15
    Registry Writer VSS Volume Shadow Copy
    Shadow Copy Optimization Writer VSS Volume Shadow Copy
    SharePoint Services Writer SPWriter Windows SharePoint Services VSS Writer
    SMS Writer SMS_SITE_VSS_WRITER SMS_SITE_VSS_WRITER
    SPSearch VSS Writer SPSearch Windows SharePoint Services Search
    SPSearch4 VSS Writer SPSearch4 SharePoint Foundation Search V4
    SqlServerWriter SQLWriter SQL Server VSS Writer
    System Writer CryptSvc Cryptographic Services
    TermServLicensing TermServLicensing Remote Desktop Licensing
    WDS VSS Writer WDSServer Windows Deployment Services Server
    WIDWriter WIDWriter Windows Internal Database VSS Writer
    WINS Jet Writer WINS Windows Internet Name Service (WINS)
    Windows Server Storage VSS Writer WseStorageSvc Windows Server Essentials Storage Service
    WMI Writer Winmgmt Windows Management Instrumentation


    Thursday, November 14, 2019 1:45 AM
  • Thanks for the reply.

    This has been an ongoing issue and persists after restarts.
    We restart at least once a month to apply updates.

    The "vssadmin list writers" command returns no errors when run.

    Thursday, November 14, 2019 3:59 AM
  • >>The "vssadmin list writers" command returns no errors when run.

    No errors? but from your screenshots, we can clear see that many writers show a error status.  please reproduced the issue and rerun the command and publish your result.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Thursday, November 14, 2019 9:12 AM
    Moderator
  • Hi,

    I am writing here to confirm current situation.

    If the above suggestion are helpful to you, please be kind enough to "mark it as an answer" for helping more people.

    Regards,
    Daniel

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Monday, November 18, 2019 2:33 AM
    Moderator
  • Hi, 

    The issue occurs randomly during the daily backups so I haven't seen the errors since the last, on Nov 8.

    When I run the command, this is the result showing no errors:

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.
    
    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {4ccf4ab6-ad2d-427f-af15-6080b2e573be}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {80024010-15f4-475b-84bb-4861690b7fe8}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'FRS Writer'
       Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
       Writer Instance Id: {fb0bda79-46cc-4c17-ab65-97d049a2291b}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {1f72e597-4b18-4f6a-8126-1b00eca4fe5f}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'MSSearch Service Writer'
       Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
       Writer Instance Id: {bc52a035-3c8e-4e91-adfa-443456fe6415}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {8aa5f933-44d9-464c-af45-e99842942cdc}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {dd5645ac-05d5-4605-b58d-066666bbe4d6}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'Windows Server Storage VSS Writer'
       Writer Id: {e376ebb9-f0fe-4e1a-adaa-bfbdaf3ab488}
       Writer Instance Id: {98014b4f-d685-48be-b212-4abff39f8049}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'NTDS'
       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
       Writer Instance Id: {2aef5fb6-c342-4fde-bae8-d203811a5277}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {1f41b104-8798-4e5d-bafd-d99cd1f158e8}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'Certificate Authority'
       Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
       Writer Instance Id: {83b8d8af-1f37-463d-b31f-e2c68076064f}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'Dhcp Jet Writer'
       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
       Writer Instance Id: {7f3b0139-cfd6-4095-93a6-b136770f44f3}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {f189e68a-98c3-49e4-93cc-d44efe5654fe}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {f2595c5a-ccdf-4122-aa1e-d7fff661237e}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {45a799bf-96c4-4a7b-9d79-5c639fcbc9aa}
       State: [1] Stable
       Last error: No error

    I found another post with a similar issue:
    https://social.technet.microsoft.com/Forums/en-US/9b487087-7578-4969-85f8-2b367382a728/windows-server-2016-essentials-backup-error?forum=ws16essentials
    Do you think the suggestions by Andy would help?


    Monday, November 18, 2019 4:32 AM
  • >>Do you think the suggestions by Andy would help?

    You can try your luck.

    In addition, We need to run the above command when the problem occurs again.

    Due to your issue is not repccurred, so that your command printed no error.

    For now, I don't think we can do too much things but wait for the problem to reoccurred.

    Thanks,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Tuesday, November 19, 2019 8:23 AM
    Moderator
  • I ran "sfc /scannow" and "DISM/Online /Cleanup-image /Scanhealth". 

    SFC results:

    Windows Resource Protection found corrupt files and successfully repaired
    them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.

    DISM results:

    No component store corruption detected.
    The operation completed successfully.

    Tonight's backup still resulted in "Completed with warnings".
    Image during backup:

    

    vssadmin list writers results:

    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.
    
    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {64540831-4e12-44fc-8724-976355b96a53}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {fc0a2759-8811-4853-866e-d5bdeeeb9027}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {5ea41c83-3afd-4bc1-977b-4fdfdfb5971c}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {ac5d462e-eaea-478e-9b74-7dcc46ac2fca}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {e76e8694-ce31-444f-be5f-393b215d9895}
       State: [1] Stable
       Last error: No error
    
    Writer name: 'Windows Server Storage VSS Writer'
       Writer Id: {e376ebb9-f0fe-4e1a-adaa-bfbdaf3ab488}
       Writer Instance Id: {16149615-c564-4243-a83f-e4ba239e649c}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'FRS Writer'
       Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
       Writer Instance Id: {baadf151-1162-404f-ab6e-873ef4e6b9d9}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'MSSearch Service Writer'
       Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
       Writer Instance Id: {ca0e8be4-d85f-4b11-adcb-b92169e88a15}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'Dhcp Jet Writer'
       Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
       Writer Instance Id: {8eca3e90-aed8-4639-99e7-34e4eb5f0402}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {61904315-6ab3-4f43-84f7-1af89ef75263}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {4e41cec8-cdec-449f-9fd8-a81a1ffc5e03}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {3b1eaea2-85a0-4bcf-b4c8-1e3b8d537fa4}
       State: [10] Failed
       Last error: Timed out
    
    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {0fc73e5d-1f10-4517-86ec-9a3345bf7ba4}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'Certificate Authority'
       Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
       Writer Instance Id: {2b004679-0a30-4484-b2dd-6672d9391e28}
       State: [9] Failed
       Last error: Timed out
    
    Writer name: 'NTDS'
       Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
       Writer Instance Id: {9f8ed448-8212-44de-bcd3-6fc64135bb15}
       State: [9] Failed
       Last error: Timed out

    I restarted the services that failed and manually started a backup, which completed without issues.

    How do I figure out the cause of these time out errors?

    Tuesday, November 26, 2019 5:59 AM
  • From forum support, it is diffcult for us to find the cause of these time out errors, maybe you should open a ticket to Microsoft.

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Tuesday, November 26, 2019 6:26 AM
    Moderator