[b]10/07/2017 11:55:34 p.m. :: Failed to create VM recovery checkpoint (mode: Veeam application-aware processing with failover) Details: Job failed ('Checkpoint operation for 'ServerNameRedacted' failed. (Virtual machine ID AC036EA6-E0F8-44C5-9E21-4340898C97FA)'). Error code: '32768'.
Failed to create VM recovery snapshot, VM ID 'ac036ea6-e0f8-44c5-9e21-4340898c97fa'.[/b]
10/07/2017 11:55:47 p.m. :: Retrying snapshot creation attempt (Failed to create production checkpoint.)
10/07/2017 11:55:49 p.m. :: Required backup infrastructure resources have been assigned
[b]10/07/2017 11:56:00 p.m. :: Guest processing skipped (check guest OS VSS state and hypervisor integration components version)[/b]
10/07/2017 11:56:00 p.m. :: Creating VM recovery checkpoint (mode: Crash consistent)
10/07/2017 11:56:18 p.m. :: Using source proxy 192.168.9.25 (onhost)
10/07/2017 11:56:54 p.m. :: Saving config.wmi
10/07/2017 11:57:11 p.m. :: VMRS configuration file (60.1 KB) 60.1 KB read at 60 KB/s
10/07/2017 11:57:16 p.m. :: VMCX configuration file (166.3 KB) 166.3 KB read at 166 KB/s
10/07/2017 11:57:47 p.m. :: Hard disk 1 (571.0 GB) 37.1 GB read at 65 MB/s [CBT]
10/07/2017 11:57:51 p.m. :: Hard disk 2 (281.0 GB) 8.1 GB read at 45 MB/s [CBT]
11/07/2017 12:02:30 a.m. :: Hard disk 3 (150.0 GB) 2.9 GB read at 38 MB/s [CBT]
11/07/2017 12:04:58 a.m. :: Hard disk 4 (300.0 GB) 2.2 GB read at 100 MB/s [CBT]
11/07/2017 12:08:05 a.m. :: Finalizing
11/07/2017 12:08:07 a.m. :: Swap file blocks skipped: 15.6 GB
11/07/2017 12:08:07 a.m. :: Deleted file blocks skipped: 3.2 GB
11/07/2017 12:08:07 a.m. :: Busy: Source 42% > Proxy 11% > Network 9% > Target 55%
11/07/2017 12:08:07 a.m. :: Primary bottleneck: Target
11/07/2017 12:08:07 a.m. :: Network traffic verification detected no corrupted blocks
11/07/2017 12:08:07 a.m. :: Processing finished with warnings at 11/07/2017 12:08:07 a.m.
derek wrote:I ran across this issue today and did some searching.
I found a post https://superuser.com/questions/1070464 ... 0x800423f4 Where IntelXX mentioned that if you set that VM's checkpointing to Standard instead of the new Production type it will work.
I was able to take a checkpoint using the HyperV interface after changing this.
I'm running a Veeam backup job now with the new setting for my 2008R2 DC VM.
jed-hyper wrote:Have Microsoft or Veeam acknowledged this issue yet ?
nmdange wrote:If the issue is fixed when Veeam App-Aware processing is disabled and Hyper-V Native Quiescence is used instead, then I'm inclined to side with Microsoft that this is a Veeam issue.
Users browsing this forum: Google Feedfetcher and 1 guest