Failed to create VM recovery checkpoint

Hyper-V specific discussions

Failed to create VM recovery checkpoint

Veeam Logoby AlexLeadingEdge » Sun Jan 15, 2017 8:05 pm

Hi guys!

We have just finished moving Hyper-V VMs from our old Windows Server 2012 R2 Hyper-V host to our new Windows Server 2016 Hyper-V host. All the VMs work exceptionally well but when we go to do a backup of the SBS 2011 server using B&R 9.5 it spits up this error after 11 seconds:

15/01/2017 11:47:48 p.m. :: Failed to create VM recovery checkpoint (mode: Veeam application-aware processing with failover) Details: Job failed ('Checkpoint operation for 'SBS-SERVER' failed. (Virtual machine ID B854900D-2DA6-44D0-9E3A-24D5D4700368)'). Error code: '32768'.
Failed to create VM recovery snapshot, VM ID 'b854900d-2da6-44d0-9e3a-24d5d4700368'.
15/01/2017 11:48:00 p.m. :: Retrying snapshot creation attempt (Failed to create production checkpoint.)


I will open a case when I can and update this ticket.

(For privacy reasons I have changed the name of the SBS server in the error message)
AlexLeadingEdge
Expert
 
Posts: 157
Liked: 18 times
Joined: Mon Dec 14, 2015 9:42 pm

Re: Failed to create VM recovery checkpoint

Veeam Logoby AlexLeadingEdge » Sun Jan 15, 2017 8:15 pm

I see here that there is a known issue with Server 2016 and B&R 9.5 (different error message though!):

microsoft-hyper-v-f25/9-5-hyper-v-known-issues-t38927.html

Application-aware processing of Active Directory domain controllers running on guest OS other than Windows Server 2016 fails with the “Failed to create VM recovery checkpoint” error (32770). This is a Hyper-V 2016 issue that Microsoft is planning to address in the future update.
AlexLeadingEdge
Expert
 
Posts: 157
Liked: 18 times
Joined: Mon Dec 14, 2015 9:42 pm

Re: Failed to create VM recovery checkpoint

Veeam Logoby AlexLeadingEdge » Sun Jan 15, 2017 8:41 pm

Case # 02039027
AlexLeadingEdge
Expert
 
Posts: 157
Liked: 18 times
Joined: Mon Dec 14, 2015 9:42 pm

Re: Failed to create VM recovery checkpoint

Veeam Logoby Mike Resseler » Mon Jan 16, 2017 6:33 am

Alex,

For my understanding, your SBS server is running as a VM on a hyper-v 2016 host? In that SBS server is normally a domain controller so while the message might be different, I do think that you should look in that direction. But since I don't have any logs, please keep working with your support engineer to find the root cause

Thanks
Mike
Mike Resseler
Veeam Software
 
Posts: 3340
Liked: 379 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 » Tue Jan 17, 2017 2:47 am

VEEAM Support wrote:Could you please check if you can manually create a Checkpoint?

Also, verify if the VSS writers on the host are stable. You can run the command
Vssadmin list writers
I can manually create a checkpoint on the Hyper-V Host.

VSS writers are stable on both the backup server and the VM (the SBS Server).

The backup last night again spat up this same error.
AlexLeadingEdge
Expert
 
Posts: 157
Liked: 18 times
Joined: Mon Dec 14, 2015 9:42 pm

Re: Failed to create VM recovery checkpoint

Veeam Logoby AlexLeadingEdge » Tue Jan 17, 2017 2:49 am

Mike Resseler wrote:For my understanding, your SBS server is running as a VM on a hyper-v 2016 host?
Correct.

Mike Resseler wrote:In that SBS server is normally a domain controller so while the message might be different, I do think that you should look in that direction. But since I don't have any logs, please keep working with your support engineer to find the root cause.
Will do. The backup last night again spat up this same error.
AlexLeadingEdge
Expert
 
Posts: 157
Liked: 18 times
Joined: Mon Dec 14, 2015 9:42 pm

[MERGED] Domain controllers fail to backup

Veeam Logoby Perry » Wed Jan 25, 2017 11:07 pm

I have a job that backs up 6 VMs two of which are domain controllers. While the non domain controllers back up fine the domain controllers fail with this error:

Code: Select all
Failed to create VM recovery checkpoint (mode: Veeam application-aware processing) Details: Job failed (''). Error code: '32768'. Failed to create VM recovery snapshot, VM ID '50dfbcce-ca37-426c-a280-a83ac9d2e454'.
Retrying snapshot creation attempt (Failed to create production checkpoint.)
Task has been rescheduled
Queued for processing at 1/25/2017 1:41:29 AM
Unable to allocate processing resources. Error: Job failed (''). Error code: '32768'. Failed to create VM recovery snapshot, VM ID '50dfbcce-ca37-426c-a280-a83ac9d2e454'.

Any ideas?
Perry
Enthusiast
 
Posts: 43
Liked: never
Joined: Mon Jan 02, 2017 10:19 pm
Full Name: Perry

Re: Domain controllers fail to backup

Veeam Logoby Perry » Thu Jan 26, 2017 4:01 am

I want to add that the backups for the DCs work fine if "Application-Aware Processing" is disabled.
Perry
Enthusiast
 
Posts: 43
Liked: never
Joined: Mon Jan 02, 2017 10:19 pm
Full Name: Perry

Re: Failed to create VM recovery checkpoint

Veeam Logoby v.Eremin » Thu Jan 26, 2017 9:28 am

Do you use Hyper-V 2016? Does DC run on OS other than Windows Server 2016? If so, be aware that you've come across known Hyper-V 2016 issue. Thanks.
v.Eremin
Veeam Software
 
Posts: 13543
Liked: 1002 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Failed to create VM recovery checkpoint

Veeam Logoby Perry » Fri Jan 27, 2017 9:56 am

Since application-aware processing has to be disabled for Domain Contoller VMs until the bug is fixed, should we enable guest quiescence? If so, how do we enable this at the individual VM level? Enabling quiescence seems to be global to the entire backup.
Perry
Enthusiast
 
Posts: 43
Liked: never
Joined: Mon Jan 02, 2017 10:19 pm
Full Name: Perry

Re: Failed to create VM recovery checkpoint

Veeam Logoby v.Eremin » Fri Jan 27, 2017 2:48 pm

I don't think enabling Hyper-V quiescence is likely to help here, as it would leverage similar framework as AAIP does. Thanks.
v.Eremin
Veeam Software
 
Posts: 13543
Liked: 1002 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Failed to create VM recovery checkpoint

Veeam Logoby Perry » Sat Jan 28, 2017 8:33 am

So what's the recommended setting for backing up DC servers until the bug is fixed? Completely disable Application-Aware processing?
Perry
Enthusiast
 
Posts: 43
Liked: never
Joined: Mon Jan 02, 2017 10:19 pm
Full Name: Perry

Re: Failed to create VM recovery checkpoint

Veeam Logoby v.Eremin » Tue Jan 31, 2017 12:56 pm

Yep, either disable AAIP (till the issue gets fixed by MS) or update DC to Windows Server 2016.
v.Eremin
Veeam Software
 
Posts: 13543
Liked: 1002 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Failed to create VM recovery checkpoint

Veeam Logoby carussell » Wed Feb 01, 2017 3:22 pm

I am having the exact same issue but there is a twist in the information.

HV host updated from HV server 2012r2 to server 2016 datacenter. all the VM's that I manually MOVED to the updated host will complete a backup with a warning that they should be updated to hardware version 8. A newly created VM (windows 7 ent x32) will not backup and fails:

Failed to create VM recovery checkpoint (mode: Hyper-V child partition snapshot) Details: Job failed ('Checkpoint operation for 'Win 7 Ent x32' failed. (Virtual machine ID xxxxxxxx)'). Error code: '32768'. Failed to create VM recovery snapshot, VM ID 'xxxxxxxxx'.
Retrying snapshot creation attempt (Failed to create production checkpoint.)
Task has been rescheduled
Queued for processing at 2/1/2017 8:56:02 AM
Unable to allocate processing resources. Error: Job failed ('Checkpoint operation for 'Win 7 Ent x32' failed. (Virtual machine ID xxxxxxxx)'). Error code: '32768'. Failed to create VM recovery snapshot, VM ID 'xxxxxxxxx'.


Domain controllers are windows 2003.... but they are NOT VM's they are separate physical machines. So while this seems to be related it doesn't seem as though the known bug is this issue as that is about older OS DC's as Guests on Win2016 Hosts.
carussell
Novice
 
Posts: 9
Liked: never
Joined: Tue Jan 17, 2017 3:36 pm
Full Name: Chris Russell

Re: Failed to create VM recovery checkpoint

Veeam Logoby mvalpreda » Tue Jun 06, 2017 2:22 am

Did this ever get sorted on either the Microsoft or Veeam side? I just did a 2012 R2 to 2016 migration and the 2012 R2 DC is not happy.
mvalpreda
Enthusiast
 
Posts: 28
Liked: never
Joined: Wed May 06, 2015 10:57 pm
Full Name: Mark Valpreda

Next

Return to Microsoft Hyper-V



Who is online

Users browsing this forum: No registered users and 25 guests