none
2016 VM backup not working

    Question

  • Hi guys,

    I have an issue that VM backup fails and cannot be backed up through Windows Server Backup. All servers (host and guest) are WS2016 Standard editions. The other VM running on the host (without any SQL) is being backed up fine. 

    Affected VM is running RDS and accounting software which uses SQL 2016 Express. There is also a WSUS db which is also using the same SQLExpress engine.

    Errors:

    Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
    Source:        Microsoft-Windows-Hyper-V-VMMS
    Date:         
    Event ID:      10150
    Task Category: None
    Level:         Error
    Keywords:      
    User:          SYSTEM
    Computer:     
    Description:
    Could not create backup checkpoint for virtual machine <REDACTED>: The shadow-copy set only contains only a subset of the volumes needed to correctly backup the selected components of the writer. (0x800423F0). (Virtual machine ID <REDACTED>)

    Also, on the VM itself:

    vssadmin list writers 

    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: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {d4dbecf8-262d-4115-b598-8e1c5232a4b8}
       State: [8] Failed
       Last error: Inconsistent shadow copy

    Writer name: 'WIDWriter'
       Writer Id: {8d5194e1-e455-434a-b2e5-51296cce67df}
       Writer Instance Id: {2d7c07af-1998-4b9c-8ef5-02f5a2bfb463}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {a1f81fe4-5e2d-4c4a-9c7c-ab024e0302bb}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {632d94bd-d2b9-4ecf-99ca-108818d55d0f}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {81caef2e-101c-44c0-9f19-a5e3f83a1dbf}
       State: [1] Stable
       Last error: No error

    Writer name: 'TermServLicensing'
       Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
       Writer Instance Id: {669a5711-b1e3-4795-88d6-e94ae7199142}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {eb30ba7e-d2da-4b12-94d5-dc1cece4a187}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Config Writer'
       Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
       Writer Instance Id: {b407c973-0037-40b6-9f33-5c0dc4315742}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {dec1fb5d-32d4-4270-9260-653e6b13c630}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'NPS VSS Writer'
       Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
       Writer Instance Id: {f6bec283-0d39-4da8-be33-69d62fbeeb69}
       State: [1] Stable
       Last error: No error

    Writer name: 'IIS Metabase Writer'
       Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
       Writer Instance Id: {5bb3ff47-289d-417b-b9a0-a05522606861}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {ae635df0-9a30-47d4-9182-1b5df38f0e8d}
       State: [5] Waiting for completion
       Last error: No error

    Writer name: 'TS Gateway Writer'
       Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
       Writer Instance Id: {3e35271d-262a-473f-a18c-9d4a57ef6082}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {46750505-fbc1-4b06-a8e2-acc4311b5308}
       State: [1] Stable
       Last error: No error

    

    Thank you for any help.

    Michael



    Friday, June 1, 2018 9:52 PM

All replies

  • Hi Michael,

    Based on the knowledge, vss error 0x800423F0 usually indicates an issue with the VSS snapshot that was created. This could mean the snapshot was corrupt or there is an issue with the VSS service on your system.  

    In your scenario, since it seems point to the sql service when you list vss related writers. The Windows SQL Writer is failing, thus windows server VM Backup is unable to complete an application consistent backup of this VM due to the failure.

    I suggest you could first try to restart below services and check the status of writer.

    Cryptographic Service 
    Volume Shadow Copy Service 

    If it still doesn't work, please restart SQL server service and check for the status.

    In addition, please also check the thread discussed before.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/d68f5b89-49a9-4ae5-9ad0-b2f796ef21b0/issue-with-cryptographic-services-and-backing-up-a-vm?forum=windowsbackup

    Best Regards,

    Mary

         


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

    Monday, June 4, 2018 5:30 AM
    Moderator
  • Hello Mary,

    Many thanks for your answer.

    The VM has been restarted multiple times to no avail. When I manually restart the SQL VSS writer service, it is in 'stable' state. It switches to 'failed' and 'inconsistent shadow copy' after backup attempt.

    I've checked the article you posted, but there's no "Backup (volume checkpoint)" on this 2016 VM properties, only Backup (volume shadow copy). Production checkpoints are enabled but not used (even though the checkpoint structure is created under the specified directory). 

    I have to add that Windows Backup was never successful on this machine (from Jan 29, 2017). 

    Tuesday, June 5, 2018 10:48 AM
  • Hi stereomike80,

    According to your description,  you backup this VM server 2016 through the host backup feature?

    And what do you mean "I have to add that Windows Backup was never successful on this machine "

    Since other vms could be worked. Only this VM has problem. And the vss wirters also has the error in this VM. It's more like to the VSS service problem inside the VM.

    I suggest you could also refer to the thread discussed before.

    https://social.technet.microsoft.com/Forums/lync/en-US/4004b86d-d6c9-4cd7-a3b6-ee16470a72dd/vss-sqlserverwriter-failing?forum=winservergen

    Best Regards,

    Mary


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

    Wednesday, June 6, 2018 2:11 AM
    Moderator