Failed to create snapshot (Microsoft Software Shadow Copy provider 1.0) (mode: Veeam application-aware processing)

Kevin Yi 6 Reputation points
2023-02-15T05:13:12.3666667+00:00

These are the two error messages I am receiving on back up failure in Veeam.

14/02/2023 3:34:13 PM :: Unable to allocate processing resources. Error: Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_PREPARE_SNAPSHOT'.

The writer experienced a non-transient error. If the backup process is retried,

the error is likely to reoccur.

--tr:Failed to verify writers state.

--tr:Failed to perform pre-backup tasks.

14/02/2023 3:21:21 PM :: Failed to create snapshot (Microsoft Software Shadow Copy provider 1.0) (mode: Veeam application-aware processing) Details: Writer 'Microsoft Hyper-V VSS Writer' is failed at 'VSS_WS_FAILED_AT_PREPARE_SNAPSHOT'.

The writer experienced a non-transient error. If the backup process is retried,

the error is likely to reoccur.

--tr:Failed to verify writers state.

--tr:Failed to perform pre-backup tasks.

After back up job runs the Microsoft Hyper-V VSS Writer fails on the Host
[

](https://filestore.community.support.microsoft.com/api/images/165bc2d1-ed37-4158-977c-fe9d553e9bc6?upload=true)
Restarting Hyper-V Virtual Machine Management service resolves this Non-retryable error

Veeam support has advised this is unrelated to Veeam.

There are other VMs on this Hyper-V Host that are being backed up without issues.
I've confirmed that the guest has no missing vssadmin providers compared to the other VM's with backups working.
User's image

I've checked the guests volume properties and confirmed that the shadow copies section match the storage area.

I was able to create shadow copies of each volume without issues on the guest.

I've tried rebooting both Guest(rebooted guest multiple times trying different fixes) and Host

Event Log on Host: Event ID 8229
[

](https://filestore.community.support.microsoft.com/api/images/39938651-6516-4d82-babf-035a0fd87a62?upload=true)

Event log on Guest: Event ID 12293
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {74600e39-7dc5-4567-a03b-f091d6c7b092}. Routine details PostFinalCommitSnapshots({cae8ad1f-44b9-4132-a728-8694afa050a9}, 5) [hr = 0x80070002, The system cannot find the file specified.].

Operation:
   Executing Asynchronous Operation

Context:
   Current State: DoSnapshotSet

In the Virtual Machine settings the back up (Volume checkpoint) integration services is turned on.[

](https://filestore.community.support.microsoft.com/api/images/3ceff8a9-387b-44a4-9dfb-7fda2e6f54e9?upload=true)
Please advise of any further information you need.

Hoping to find any assistance on why 1 of the VM's is having an issue backing up

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,103 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,715 questions
{count} vote

1 answer

Sort by: Most helpful
  1. Limitless Technology 44,336 Reputation points
    2023-02-16T11:12:00.39+00:00

    Hi. Thank you for your question and reaching out. I’d be more than happy to help you with your query

    It sounds like you are having issues creating a snapshot using Microsoft Software Shadow Copy provider 1.0. This could be caused by several things, so it's important to try to narrow down the cause of the problem.

    First, make sure you have the latest version of the Microsoft Software Shadow Copy provider installed on your system. Then, check that all other applications that are using the Microsoft Software Shadow Copy provider are up to date as well, and that any necessary updates have been installed.

    Additionally, it is important to check that the application you are using to create the snapshot is properly configured and running in the correct mode. If the application is not set up correctly, it can cause the snapshot to fail. You can also try restarting the application to see if that resolves the problem.

    Finally, if the issue persists, it may be necessary to contact Microsoft Support for further assistance in resolving the issue. I hope this helps you get your snapshot working properly!

    If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.