Failed to create VM recovery checkpoint

Discussions specific to Microsoft Hyper-V hypervisor

Re: Failed to create VM recovery checkpoint

Veeam Logoby Mike Resseler » Tue Jun 06, 2017 8:13 am

Hi Mark,

No this issue still exists. As written above, you should disable AAIP for the DC. The bug is unfortunately still there and we haven't got any notification that MSFT is solving it
Mike Resseler
Veeam Software
 
Posts: 4225
Liked: 471 times
Joined: Fri Feb 08, 2013 3:08 pm
Location: Belgium, the land of the fries, the beer, the chocolate and the diamonds...
Full Name: Mike Resseler

Re: Failed to create VM recovery checkpoint

Veeam Logoby rsanders » Fri Sep 22, 2017 2:48 am

Still having this issue as I just migrated an SBS server to a 2016 host. It won't be there long as it being decommissioned soon, but it would still be nice to have guest processing.
rsanders
Service Provider
 
Posts: 32
Liked: 7 times
Joined: Wed Apr 20, 2016 7:32 pm
Full Name: Ryan Sanders

Re: Failed to create VM recovery checkpoint

Veeam Logoby AlexLeadingEdge » Tue Sep 26, 2017 3:21 am

Nine months on I'm still having this issue :(
AlexLeadingEdge
Expert
 
Posts: 220
Liked: 26 times
Joined: Mon Dec 14, 2015 9:42 pm

Re: Failed to create VM recovery checkpoint

Veeam Logoby mazzu » Tue Sep 26, 2017 4:17 pm

Same problem here, same scenario, Hyper-V 2016 with a 2012 R2 Domain Controller VM.
Backups for the DC work fine if "Application-Aware Processing" is disabled.
mazzu
Lurker
 
Posts: 2
Liked: 1 time
Joined: Mon Jul 28, 2014 6:37 am
Full Name: Emilio Mazzucconi

Re: Failed to create VM recovery checkpoint

Veeam Logoby sbaltic » Fri Oct 13, 2017 4:22 am

Same problem with 2016 host and 2016 VM (not DC) ....

11.10.2017 20:01:26 :: Failed to create VM recovery checkpoint (mode: Veeam application-aware processing) Details: Job failed (''). Error code: '32772'.
Failed to create VM recovery snapshot, VM ID '6604883e-fc6e-4403-b72d-454d3741377b'.
sbaltic
Enthusiast
 
Posts: 26
Liked: 1 time
Joined: Mon Nov 18, 2013 6:10 pm
Full Name: Sebastijan

Re: Failed to create VM recovery checkpoint

Veeam Logoby IHT_Michael » Tue Nov 21, 2017 10:49 pm

v.Eremin wrote:Yep, either disable AAIP (till the issue gets fixed by MS) or update DC to Windows Server 2016.


How can we disable AAIP with your scheduled PowerShell script and VB&R Free? I'm assuming I'm seeing this same issue. I have Windows Server 2016 for the Hyper-V host with four virtuals running. The two that are not DCs back up fine. The two that are DCs have this Error 32768. But I'm doing this from scheduled PowerShell scripts.

Thanks,
Michael
IHT_Michael
Lurker
 
Posts: 1
Liked: never
Joined: Tue Nov 21, 2017 10:36 pm
Full Name: Michael C Brown

Re: Failed to create VM recovery checkpoint

Veeam Logoby foggy » Wed Nov 22, 2017 1:03 pm

Hi Michael, there's no AAIP in the free version.
foggy
Veeam Software
 
Posts: 16226
Liked: 1296 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Failed to create VM recovery checkpoint

Veeam Logoby cpfleger » Wed Nov 22, 2017 6:35 pm

Got the same problem after I v2ved a Win2k12r2 file server from vSphere 6.5 to Hyper-V 2016 (using a Veeam Agent for Windows 2.0 free backup Instant recovering to Hyper-V host and finalizing the Hyper-V vm), had both app-aware and Hyper-V quiescence enabled in the backup job.

Tried again after deinstalling VAW and VMware tools, but same result.

vssadmin list writers shows a bunch of vss writers failing due to timeouts (System Writer, ASR Writer, FSRM Writer, Shadow Copy Optimization Writer, Registry Writer, COM+ REGDB Writer, Dedup Writer, WMI Writer). Will check if I can start/fix the services behind.

Hints and tips welcome.

Regards!
cpfleger
Veeam ProPartner
 
Posts: 248
Liked: 23 times
Joined: Fri Aug 31, 2012 7:30 am
Full Name: Claus Pfleger

Re: Failed to create VM recovery checkpoint

Veeam Logoby cpfleger » Wed Nov 22, 2017 10:12 pm

System Writer => Service: Cryptographic Services
ASR Writer / Registry Writer / COM+ REGDB Writer / Shadow Copy Optimization Writer => Service: Volume Shadow Copy
FSRM writer => Service: File Server Resource Manager
Dedup Writer => Data Deduplication Volume Shadow Copy Service
WMI Writer => Windows Management Instrumentation

Restarted all those services, restarted vm: all services running
Tried again VBR backup job but failed again, vsslist writers again showed vss writers failed because of timeout. Hmm ...

Disabled application aware processing (without restarting VSS Writer services), now backup has run through.

Ideas still welcome!

Regards!
cpfleger
Veeam ProPartner
 
Posts: 248
Liked: 23 times
Joined: Fri Aug 31, 2012 7:30 am
Full Name: Claus Pfleger

Re: Failed to create VM recovery checkpoint

Veeam Logoby Mike Resseler » Mon Nov 27, 2017 6:56 am

Claus,

Is that server up-to-date on hotfixes and updates?
Mike Resseler
Veeam Software
 
Posts: 4225
Liked: 471 times
Joined: Fri Feb 08, 2013 3:08 pm
Location: Belgium, the land of the fries, the beer, the chocolate and the diamonds...
Full Name: Mike Resseler

Re: Failed to create VM recovery checkpoint

Veeam Logoby AlexLeadingEdge » Thu Dec 14, 2017 12:51 am

cpfleger wrote:Disabled application aware processing (without restarting VSS Writer services), now backup has run through.
Hi cpfleger, my understanding is that you really don't want to do that, as this step quietens (quiesces) an active database system such as SQL or an Exchange Server, so that the backup doesn't end up corrupt! :shock:
AlexLeadingEdge
Expert
 
Posts: 220
Liked: 26 times
Joined: Mon Dec 14, 2015 9:42 pm

Re: Failed to create VM recovery checkpoint

Veeam Logoby ahickingbottom » Wed Jan 17, 2018 2:41 pm

Just checking to see the status on this issue with everyone else. I am still having the same issues. We are running Hyper-V on Server 2016 and the VM with the issue is a 2012 R2 running Microsoft SQL. We do not want to disable Application-Aware Processing just to get the job to complete because it runs SQL. Any information on a proper fix would be appreciated.
ahickingbottom
Lurker
 
Posts: 1
Liked: never
Joined: Wed Jan 17, 2018 2:35 pm
Full Name: Andrew Hickingbottom

Re: Failed to create VM recovery checkpoint

Veeam Logoby AlexLeadingEdge » Thu Jan 18, 2018 7:43 pm

One year now and still no resolution :(
AlexLeadingEdge
Expert
 
Posts: 220
Liked: 26 times
Joined: Mon Dec 14, 2015 9:42 pm

Re: Failed to create VM recovery checkpoint

Veeam Logoby Mike Resseler » Mon Jan 22, 2018 6:49 am

Andrew,

First: Welcome to the forums!

I think your issue might be a bit different. The problem is with DC's. There are MSFT fixes that solves it for other type of workloads. If your 2012 R2 VM is fully up-to-date with MSFT updates, please create a support call. Post the support call ID here and let us know the follow-up after investigation with the engineers
Thanks
Mike
Mike Resseler
Veeam Software
 
Posts: 4225
Liked: 471 times
Joined: Fri Feb 08, 2013 3:08 pm
Location: Belgium, the land of the fries, the beer, the chocolate and the diamonds...
Full Name: Mike Resseler

Previous

Return to Microsoft Hyper-V



Who is online

Users browsing this forum: No registered users and 8 guests