Job Completion Status Job ended: 17/11/2019 . On VBR Console, right-click the failed job and click on the Edit. Get the recovery checkpoint exact name with the command, Verify that the recovery checkpoint has been successfully deleted with the command. It doesn't seem like you've done a lot of troubleshooting here, so i will suggest some basics - what does event logs say on either B&R or guest OS. Contact the administrator of the authorization policy for the computer remote_host. Here are some errors that you may encounter when trying to create a Hyper-V checkpoint: The common cause for these error messages is that incorrect file and folder permissions were set. this post, Post For this reason, if both the job (with those settings enabled) and the Production Checkpoint fail, the issue is environmental. Hello all, I've recently downloaded Veeam Comunity Edition to play with Veeam a little bit to get familiar with it, but I'm facing problems when trying to back up one of the server named SA01 info about SA01: -windows 2012 Standard -SQL Server 2016Getting results: ------------------------------------------ Warning: 9/26/2020 9:36:45 PM :: Failed to create VM recovery checkpoint (mode: Veeam application-aware processing) Details: Unable to perform application-aware processing because connection to the guest could not be established Error: 9/26/2020 9:36:47 PM :: Error: Unable to perform application-aware processing because connection to the guest could not be established 9/26/2020 9:36:47 PM :: Processing finished with errors at 9/26/2020 9:36:47 PM ------------------------------------------ -there are two Hyper-V Hosts in my environment - VH01 and VH02 -added both host in Virtual Infrastructure -all VMs were discovered OK. SA01 is there on VH02 and looks OK. -on VH02 directly I was able to create a snapshot of SA01 manually -I can ping SA01 from VeeamServer. 11-17-2019 This article helps fix errors that occur when you try to back up Virtual Machines (VMs) that belong to a guest cluster by using shared virtual disk (VHDS). Error code: '32768'. Wmi error: '32775' Failed to create VM recovery snapshot, VM ID '4c9d3f65-b731-487f-a2c6-4002e018103c'. We are running Hyper-V on Server 2016 and the VM with the issue is a 2012 R2 running Microsoft SQL. It may not be able to quiescence the VM long enough especially if the VM is running heavy processes. Other VMs work fine. [SOLVED] Production checkpoints fail - Virtualization Once the production checkpoint has been applied, noticed that the virtual machine is in an off state. regardless of the aforementioned checkbox. A dialog box appears with the following options: Right-click the checkpoint, and then select. DISCLAIMER: All feature and release plans are subject to change without notice. If you followed the previous exercise, you can use the existing text file. Changed block tracking (CBT) utilize the reference point to identify changes since the last backup. Failed to create VM recovery checkpoint - Page 2 - R&D Forums