Problems with Windows Server Backup 2019

Luiz Fernando 6 Reputation points
2021-05-25T18:47:42.007+00:00

I have a Windows Server 2019 STD,
With Hyper-V.

I'm having problems with backups of Virtual Machines.

Below is the error log;

Writer failures
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Instance ID: {329AFD4A-C266-4FE2-8BEE-D7E3AC695A34}
Recorder name: Microsoft Hyper-V VSS recorder
Writer status: 5
Failure result: 80042336
Application result: 80004005
Application message: (null)
Component: 05F8C804-9A67-4DEF-8753-A344A49B322F
Logical path: (null)
Component result: 800423F3
Component message:
File specification: E: \ VMs \ Saturn \ Saturn - AD \ Virtual Machines \ 05F8C804-9A67-4DEF-8753-A344A49B322F.vmcx Recursive: 0
File specification: E: \ VMs \ Saturn \ Saturn - AD \ Virtual Machines \ 05F8C804-9A67-4DEF-8753-A344A49B322F.VMRS Recursive: 0
File specification: E: \ VMs \ Saturn \ Saturn - AD \ Virtual Machines \ 05F8C804-9A67-4DEF-8753-A344A49B322F.vmgs Recursive: 0
File specification: E: \ VMs \ Saturno \ Dados.vhdx Recursive: 0
File specification: E: \ VMs \ Saturno \ sistema.vhdx Recursive: 0
File specification: E: \ VMs \ Saturno \ Dados-AutoRecovery.avhdx Recursive: 0
File specification: E: \ VMs \ Saturn \ Saturn - AD \ Snapshots \ 6E729D29-10A5-4BF7-ABA3-EE3E564E6695.VMCX Recursive: 0
File specification: E: \ VMs \ Saturn \ Saturn - AD \ Snapshots \ 6E729D29-10A5-4BF7-ABA3-EE3E564E6695.VMRS Recursive: 0
File specification: E: \ VMs \ Saturn \ Saturn - AD \ Snapshots \ 6E729D29-10A5-4BF7-ABA3-EE3E564E6695.vmgs Recursive: 0
File specification: E: \ VMs \ Saturn \ system-AutoRecovery.avhdx Recursive: 0
Component: E6313090-565B-4D17-B704-2E07380C69B3
Logical path: (null)
Component result: 800423F3
Component message:
File specification: E: \ VMs \ Jupiter \ Jupiter - SAP \ Virtual Machines \ E6313090-565B-4D17-B704-2E07380C69B3.vmcx Recursive: 0
File specification: E: \ VMs \ Jupiter \ Jupiter - SAP \ Virtual Machines \ E6313090-565B-4D17-B704-2E07380C69B3.VMRS Recursive: 0
File specification: E: \ VMs \ Jupiter \ Jupiter - SAP \ Virtual Machines \ E6313090-565B-4D17-B704-2E07380C69B3.vmgs Recursive: 0
File specification: E: \ VMs \ Jupiter \ Dados.vhdx Recursive: 0
File specification: E: \ VMs \ Jupiter \ sistema.vhdx Recursive: 0
File specification: E: \ VMs \ Jupiter \ Dados-AutoRecovery.avhdx Recursive: 0
File specification: E: \ VMs \ Jupiter \ Jupiter - SAP \ Snapshots \ 9309C517-91B8-4914-BB8D-3127BC445ED2.VMCX Recursive: 0
File specification: E: \ VMs \ Jupiter \ Jupiter - SAP \ Snapshots \ 9309C517-91B8-4914-BB8D-3127BC445ED2.VMRS Recursive: 0
File specification: E: \ VMs \ Jupiter \ Jupiter - SAP \ Snapshots \ 9309C517-91B8-4914-BB8D-3127BC445ED2.vmgs Recursive: 0
File specification: E: \ VMs \ Jupiter \ sistema-AutoRecovery.avhdx Recursive: 0
* ----------------------------- *

Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: 05F8C804-9A67-4DEF-8753-A344A49B322F
Caption: Online \ Saturn - AD
Logical Path:
Error: 80780175
Error message: the component has been ignored from the volume's shadow copy.

Detailed error: 800423F3
Detailed error message: The recorder encountered a temporary error. If the backup process is repeated,
the error may not occur again.

Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: E6313090-565B-4D17-B704-2E07380C69B3
Caption: Online \ Jupiter - SAP
Logical Path:
Error: 80780175
Error message: the component has been ignored from the volume's shadow copy.

Detailed error: 800423F3
Detailed error message: The recorder encountered a temporary error. If the backup process is repeated,
the error may not occur again.

  • ----------------------------- *

can anybody help me?

Windows Server Backup
Windows Server Backup
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Backup: A duplicate copy of a program, a disk, or data, made either for archiving purposes or for safeguarding valuable files from loss should the active copy be damaged or destroyed.
439 questions
{count} vote

4 answers

Sort by: Most helpful
  1. JiayaoZhu 3,911 Reputation points
    2021-05-26T02:10:37.937+00:00

    Hi,

    Thanks for posting on our forum!

    Based on your logs, the writer experienced a non-transient error, which usually means the VSS Writer is in a failed state when the backup job starts. Check the VSS writers for failed states, if so, restart the service associated with the writer. Run 'vssadmin list writers' from CMD prompt.

    If you see the vss writer is crashed, restart the associated service. If that doesn't work, you may have to reboot the Hyper-V host.

    Another thing to check would be whether the VM in question has any checkpoints, or is trying to create or delete a checkpoint. If so, try clearing out the checkpoints and letting it finish consolidating/merging them, and see if that helps.

    For more specific information on how to solve this kind of issue, here are some articles that you can refer to:

    General troubleshooting for Volume Shadow Copy Error 0x80042336 - partial writer failure.
    https://www.backupassist.com/support/en/knowledgebase/BA957-Volume-Shadow-Copy-Error-0x80042336-partial-writer-failure.html?cshid=BA957

    (Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.)

    How to repair failed VSS writer.
    https://help.datto.com/s/article/KB205356544

    (Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.)

    Thanks for your support!

    BR,
    Joan

    --------------------------------------------------------------------------------------------------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. Luiz Fernando 6 Reputation points
    2021-06-03T04:19:15.047+00:00

    Hi joan,

    Below is the result of the vssadmin list writers command,

    C:\Windows\system32>vssadmin list writers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.

    Waiting for responses.
    These may be delayed if a shadow copy is being prepared.

    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: 'Microsoft Hyper-V VSS Writer'
    Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
    Writer Instance Id: {01ed0969-e2ee-4031-8512-89b36998199b}
    State: [3] Frozen
    Last error: No error

    Writer name: 'ASR Writer'
    Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
    Writer Instance Id: {3b7203db-2ad9-4e28-b47d-c62e5bf36323}
    State: [3] Frozen
    Last error: No error

    Writer name: 'System Writer'
    Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
    Writer Instance Id: {353b4668-6f10-41c2-ada7-19cc1fb0bf1e}
    State: [3] Frozen
    Last error: No error

    Writer name: 'SqlServerWriter'
    Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
    Writer Instance Id: {c87f3ee2-25ba-4b62-b948-29bfbd102ad3}
    State: [3] Frozen
    Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
    Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
    Writer Instance Id: {234a4211-823f-4b0a-8711-df5139dec071}
    State: [3] Frozen
    Last error: No error

    Writer name: 'Registry Writer'
    Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
    Writer Instance Id: {66dd0d04-ca0e-4bda-88f1-376d7c314d68}
    State: [9] Failed
    Last error: Not responding

    Writer name: 'COM+ REGDB Writer'
    Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
    Writer Instance Id: {9b91b166-f274-4e5a-94ab-afa71a4d5664}
    State: [3] Frozen
    Last error: No error

    Writer name: 'WMI Writer'
    Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
    Writer Instance Id: {7d6e7217-0d58-4d28-9c61-490d22c68aa2}
    State: [3] Frozen
    Last error: No error

    Writer name: 'BITS Writer'
    Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
    Writer Instance Id: {b869ba11-0f6f-4ef9-a461-96fa7098c4c3}
    State: [1] Stable
    Last error: No error

    C:\Windows\system32>

    0 comments No comments

  3. JiayaoZhu 3,911 Reputation points
    2021-06-04T02:14:16.663+00:00

    Hi,

    Thanks for your patience!

    After my research, your issue seems to be related to some third-party backup tools. So I would like to check if you have used some thrid-party tools. If so, please contact the third-party vendor to determine whether it is possible to increase the registry transaction interval. We suggest that you increase the timing of the registry event to at least 120 seconds by using Kernel Transaction Manager (KTM).

    Here is an article which explain your issue in details:

    https://learn.microsoft.com/en-us/troubleshoot/windows-hardware/drivers/making-vss-shadow-copy-fails-error

    Thanks for your support!

    BR,
    Joan

    --------------------------------------------------------------------------------------------------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  4. Luiz Fernando 6 Reputation points
    2021-06-04T02:38:38.883+00:00

    my OS version is Windows Server 2019 with all updates applied, it has only 5 months of use I have 2 vm's in hyper-v and no other backup tool was ever used only Windows Server backup.