Discussions specific to the Microsoft Hyper-V hypervisor
wishr
Veeam Software
Posts: 1948
Liked: 232 times
Joined: Aug 07, 2018 3:11 pm
Full Name: Fedor Maslov
Contact:

Re: Failed to create VM recovery checkpoint

Post by wishr » 1 person likes this post

Hi Fernando,

Correct, with the "Take crash-consistent backup instead of suspending VM" option the application running inside will not be prepared for backup and that might cause issues with restores, so you may want to leave this setting unchecked. However, since it's pfSense, you may want to take a look at this thread mentioning a few possible issues with restores that are related to the initial pfSense deployment method. Additionally, I'd recommend checking if BIS driver package is installed and up to date.

Please, also note that AAIP is not supposed to work with FreeBSD since it's not supported by Microsoft VSS, so Hyper-V Quiescence should be the way to go in this case.

Thanks!

Rabbit
Novice
Posts: 9
Liked: never
Joined: Feb 23, 2020 5:14 am
Full Name: Julia
Contact:

[MERGED] Backup Failed

Post by Rabbit »

Hi experts, I have run the back up for two weeks and everything is fine for the first week after some setting has been updated. But starting from this week, the backup for one of the virtual machines failed. Below is the errror:

Code: Select all

3/2/2020 7:53:02 PM :: Failed to create VM recovery checkpoint (mode: Veeam application-aware processing) Details: Job failed ('Checkpoint operation for 'XXX' failed. (Virtual machine ID xxxxxxxxx)
Production checkpoints cannot be created for 'xxxxxxxxx'. (Virtual machine ID xxxxxxxx)'). Error code: '32770'.
Failed to create VM recovery snapshot, VM ID 'xxxxxxxxxx'. 
3/2/2020 7:53:13 PM :: Transaction logs will not be truncated 
3/2/2020 7:53:18 PM :: Retrying snapshot creation attempt (Failed to create production checkpoint.) 
3/2/2020 7:53:18 PM :: Task has been rescheduled 
3/2/2020 7:53:18 PM :: Queued for processing at 3/2/2020 7:53:18 PM 
3/2/2020 7:53:23 PM :: Unable to allocate processing resources. Error: Job failed ('Checkpoint operation for 'XXX' failed. (Virtual machine ID xxxxxxxx.
What I have done differently this week is to attach two drives on the host. When adding the backup repositories, the attached drives were formatted to REFS 64KB. Please advise how to fix the error! Thank you!

HannesK
Veeam Software
Posts: 6566
Liked: 1002 times
Joined: Sep 01, 2014 11:46 am
Location: Austria
Contact:

Re: Failed to create VM recovery checkpoint

Post by HannesK »

Hello,
I merged your question with the existing thread. Maybe you find something useful.
Please advise how to fix the error!
please contact support and post a case number for reference. Please understand that this is not a support forum

Best regards,
Hannes

wishr
Veeam Software
Posts: 1948
Liked: 232 times
Joined: Aug 07, 2018 3:11 pm
Full Name: Fedor Maslov
Contact:

Re: Failed to create VM recovery checkpoint

Post by wishr »

Hello Julia,

If you are unable to create a production checkpoint manually and keep getting the same error, we would strongly recommend raising a ticket with Microsoft support.

Thanks

fsr
Enthusiast
Posts: 28
Liked: 1 time
Joined: Mar 27, 2019 5:28 pm
Full Name: Fernando Rapetti
Contact:

Re: Failed to create VM recovery checkpoint

Post by fsr »

Hi,

I just had this issue with one of the remaining Windows Server 2008 R2 VMs, and i could circunvent this issue by shutting down the guest, then the snapshots and backups work. And when i turned the guest on again, the production snapshot did also work! No need to restart the Hyper-V Host. (just restarting the guest doesn't fix it, you need to take a snapshot with the guest off).

Regards

Egor Yakovlev
Veeam Software
Posts: 1701
Liked: 383 times
Joined: Jun 14, 2013 9:30 am
Full Name: Egor Yakovlev
Contact:

Re: Failed to create VM recovery checkpoint

Post by Egor Yakovlev » 1 person likes this post

Interesting workaround, thanks for sharing!
/Cheers!

kunniyoor
Service Provider
Posts: 22
Liked: never
Joined: Mar 15, 2015 6:47 am
Full Name: Krishnakuamr
Contact:

[MERGED]Failed to process replication task Error: Failed to create VM snapshot.

Post by kunniyoor »

Hi,

Production having Hyper-V 2012 and 2016 cluster

DR having Hyper-V 2012 and 2019 cluster.

Currently we are successfully running Backup jobs for VMs running on both hyper-v cluster (2012 & 2016) and replication jobs between Hyper-V 2012 at Production & DR hyper-v 2012 servers without Production checkpoints. :lol:

But when we run the replication job for the production hyper-v 2016 cluster VMs (with Production Checkpoint option unchecked) to replicate to DR (Windows 2019 hyper-v cluster) it throws below error

Code: Select all

Failed to process replication task Error: Failed to create VM (ID: cd5c08ac-4023-4598-900e-02dd81a0b091) snapshot. 
Job failed ('Checkpoint operation for 'SVR*****01' failed. (Virtual machine ID CD5C08AC-4023-4598-900E-02DD81A0B091)
Checkpoints have been disabled for 'SVR*****01'. (Virtual machine ID CD5C08AC-4023-4598-900E-02DD81A0B091).'). Error code: '32770'.
What could be the reason? : :shock:

Veeam support is working parallel with this issue and asking us to enable "Production Checkpoint" for 2016 Hyper-v Cluster VMs. We cant enable this option as we faced multiple vm crashes due to snapshot AVHD got utilized all allocated storage space. :roll:

Any suggestions? :D

wishr
Veeam Software
Posts: 1948
Liked: 232 times
Joined: Aug 07, 2018 3:11 pm
Full Name: Fedor Maslov
Contact:

Re: Failed to process replication task Error: Failed to create VM (ID: cd5c08ac-4023-4598-900e-02dd81a0b091) snapshot.

Post by wishr »

Hi Krishnakuamr,

B&R only uses production checkpoints in Hyper-V 2016 and later, so the right way to get it resolved would be to investigate VM crashes you mentioned.

Could you please share your support case ID with us, as it is necessary when posting about any technical issue on the forums?

Thanks

kunniyoor
Service Provider
Posts: 22
Liked: never
Joined: Mar 15, 2015 6:47 am
Full Name: Krishnakuamr
Contact:

Re: Failed to create VM recovery checkpoint

Post by kunniyoor »

Veeam Support - Case # 04285270

But when we did the below work around it went all well.

. Initiated the replication by enabling replica seed as usual.
. Got said Error after a while. but the job created replica VM with out any virtual disk in the target cluster (windows 2019).
. Modified the replica VM setting and enabled "Production Checkpoint" option.
. Restored the virtual disk and attached to the replica VM.
. Rerun the replication and it got created the replica VM successfully.

We didn't enable production check for the source vm in any case. :)

Krish

wishr
Veeam Software
Posts: 1948
Liked: 232 times
Joined: Aug 07, 2018 3:11 pm
Full Name: Fedor Maslov
Contact:

Re: Failed to create VM recovery checkpoint

Post by wishr »

Hi Krishnakuamr,

I have checked the case details and would like to say that regardless of the configured setting in Hyper-V, B&R does not attempt to create standard checkpoints in Hyper-V 2016 and later. So it would be great to try out the suggestions offered by our engineer and see what will be the outcome.

Thanks

drumtek2000
Lurker
Posts: 1
Liked: never
Joined: Sep 15, 2020 9:00 pm
Full Name: Frank Gangone
Contact:

Re: Failed to create VM recovery checkpoint

Post by drumtek2000 »

I rebooted but still failed.. I shut off application aware setting and backup completed.. If that helps with finding resolution..

wishr
Veeam Software
Posts: 1948
Liked: 232 times
Joined: Aug 07, 2018 3:11 pm
Full Name: Fedor Maslov
Contact:

Re: Failed to create VM recovery checkpoint

Post by wishr »

It makes sense since because without AAIP enabled Microsoft VSS is not used, however, it is not a direct solution because the application consistency is not guaranteed in that case. We encourage everyone experiencing similar issues and being unable to create a production checkpoint manually from Hyper-V to raise a ticket with Microsoft support.

Thanks

fsr
Enthusiast
Posts: 28
Liked: 1 time
Joined: Mar 27, 2019 5:28 pm
Full Name: Fernando Rapetti
Contact:

Re: Failed to create VM recovery checkpoint

Post by fsr »

drumtek2000 wrote: Sep 15, 2020 9:03 pm I rebooted but still failed.. I shut off application aware setting and backup completed.. If that helps with finding resolution..
Try this:
  • Shut down the affected VM.
  • Take snapshots/backups while the VM is off. They should work, as nothing is running on the VM, so it's not neccesary (nor possible) to "freeze" running applications. But this also seems to reset any error condition about production snapshots that were preventing them from working.
  • Turn on the affected VM. Now, production snapshots and backups should work again with the VM running. Al least, it worked that way for me on Windows Server 2016 Hyper-V hosts.
This only circunvents the issue, however. If you can contact Microsoft's support, you should do that.

Regards

Post Reply

Who is online

Users browsing this forum: No registered users and 12 guests