Discussions specific to the Microsoft Hyper-V hypervisor
Post Reply
MavBoss86
Lurker
Posts: 2
Liked: never
Joined: May 31, 2016 1:31 pm
Full Name: Daniele Moro
Contact:

Snapshot problem

Post by MavBoss86 » Aug 04, 2017 10:48 am

Hi there,

we have a problem with one of our clients. The problem is related to a VM with 3 disks, 1 for the OS with 200GB and the other 2 for the data with 8TB and 13TB. Veeam 9.5 SP2 is installed on the host. The host is Windows Server 2012 R2 and the guest the same. It backups on a QNAP. No iscsi installed.
The problem is that 9/10 the backup failes with these errors:

Code: Select all

03/08/2017 13:21:47 :: 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.  

03/08/2017 13:22:23 :: Retrying snapshot creation attempt (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.)  

03/08/2017 13:22:25 :: 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.  
This errors happen when the snapshot takes more than 10 minutes and 32 seconds. If it takes, for example, 9:42 the backup works correctly.

In the guest there are these VSS errors:

Code: Select all

VSS Error 12293

Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {74600e39-7dc5-4567-a03b-f091d6c7b092}. Routine details PostFinalCommitSnapshots({f8ddc176-c71a-4aa7-8307-6b7efac0c6be}, 4) [hr = 0x80070002, The system cannot find the file specified.
]. 

Operation:
   Executing Asynchronous Operation

Context:
   Current State: DoSnapshotSet


Volsnap Error 16

The shadow copies of volume \\?...67-11e7-80cf-00155d01a201} were aborted because volume \\?...67-11e7-80cf-00155d01a201}, which contains shadow copy storage for this shadow copy, was force dismounted.
and in the host these ones:

Code: Select all

Error Code 8229

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 to reoccur.
. 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:
   PrepareForSnapshot Event

Context:
   Execution Context: Writer
   Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Name: Microsoft Hyper-V VSS Writer
   Writer Instance ID: {39a658c2-1b5d-4a0f-9364-3402e5439f8c}
   Command Line: C:\Windows\system32\vmms.exe
   Process ID: 2840
Someone have ever seen and solved a similar problem?
My support case id is : 02266075

Thanks

foggy
Veeam Software
Posts: 17089
Liked: 1396 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Snapshot problem

Post by foggy » Aug 07, 2017 12:08 pm

Hi Daniele, this looks like the VSS snapshot timeout is exceeded. Support should be able to verify and advise on increasing the timeout value.

MavBoss86
Lurker
Posts: 2
Liked: never
Joined: May 31, 2016 1:31 pm
Full Name: Daniele Moro
Contact:

Re: Snapshot problem

Post by MavBoss86 » Aug 07, 2017 1:06 pm

Support has ask me to open a call with Microsoft, because it seems there is a problem with the VSS. With Windows Backup if I do a Backup inside the VM it works correctly. If I start it from the host backing up only the VM affected with the problem, it fails like Veeam.

foggy
Veeam Software
Posts: 17089
Liked: 1396 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Snapshot problem

Post by foggy » Aug 07, 2017 1:09 pm

I would appreciate if you share your findings upon MS investigation results.

R.Stuivenberg
Service Provider
Posts: 9
Liked: never
Joined: Aug 03, 2017 1:31 pm
Full Name: Richard Stuivenberg
Contact:

Re: Snapshot problem

Post by R.Stuivenberg » Nov 05, 2017 10:03 am

I have the same problem, did you find anything with MS?

foggy
Veeam Software
Posts: 17089
Liked: 1396 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Snapshot problem

Post by foggy » Dec 11, 2017 2:50 pm

Hi Richard, the OP hasn't returned to support with the results, so I recommend opening your own case for investigation, unless you've already done that. Thanks.

Post Reply

Who is online

Users browsing this forum: No registered users and 12 guests