9.5 Hyper-V 2016 Known Issues

Hyper-V specific discussions

Re: 9.5 Hyper-V 2016 Known Issues

Veeam Logoby frankive » Thu Jul 06, 2017 5:07 pm

+1
frankive
Service Provider
 
Posts: 728
Liked: 86 times
Joined: Tue May 14, 2013 8:35 pm
Location: Norway
Full Name: Frank Iversen

Re: 9.5 Hyper-V 2016 Known Issues

Veeam Logoby derek » Fri Jul 07, 2017 5:45 pm

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.
derek
Lurker
 
Posts: 1
Liked: never
Joined: Fri Oct 28, 2016 5:05 pm

Re: 9.5 Hyper-V 2016 Known Issues

Veeam Logoby frankive » Sat Jul 08, 2017 7:42 pm

Worked like a champ!
Veeam, agree this is an good solution for your backups?
frankive
Service Provider
 
Posts: 728
Liked: 86 times
Joined: Tue May 14, 2013 8:35 pm
Location: Norway
Full Name: Frank Iversen

Re: 9.5 Hyper-V 2016 Known Issues

Veeam Logoby AlexLeadingEdge » Mon Jul 10, 2017 9:57 pm

I tried it on the overnight backups but it didn't work for us :cry:

Still seeing these warning messages each night for the SBS 2011 VM on a Server 2016 Hyper-V Host, being backed up from a non-VM Windows 10 backup server (bold is the error messages).

We need Application Aware Processing as it truncates the Exchange logs each night.

It has been eight months and we still have no solution :cry:

Case # 02039027

Code: Select all
[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.
AlexLeadingEdge
Expert
 
Posts: 157
Liked: 18 times
Joined: Mon Dec 14, 2015 9:42 pm

Re: 9.5 Hyper-V 2016 Known Issues

Veeam Logoby frankive » Tue Jul 11, 2017 5:48 am

I am no engineer expert on Veeam, but doesn't this log says you take a "production checkpoint"? (Line 4).
I think it should say standard checkpoint after you have changed this in the checkpoint settings for the VM, but I may be wrong.
frankive
Service Provider
 
Posts: 728
Liked: 86 times
Joined: Tue May 14, 2013 8:35 pm
Location: Norway
Full Name: Frank Iversen

Re: 9.5 Hyper-V 2016 Known Issues

Veeam Logoby AlexLeadingEdge » Tue Jul 11, 2017 8:54 pm

Good spotting. I have just changed it back to Standard and run it again but it doesn't seem to change that message. I can test it again on the overnight backup but I don't expect that it will change (it finished with a warning the other night).
AlexLeadingEdge
Expert
 
Posts: 157
Liked: 18 times
Joined: Mon Dec 14, 2015 9:42 pm

Re: 9.5 Hyper-V 2016 Known Issues

Veeam Logoby jed-hyper » Wed Jul 12, 2017 1:23 am

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.


I have tried changing the checkpoints setting from 'Production checkpoints' to Standard checkpoints' on the virtual machine but I'm still having the same issue.
I'm Running Windows Server 2016 Hyper-V Host with Windows 2012 R2 virtual machine which is a DC with Veeam application-aware processing enabled.
Veeam error: Failed to create VM recovery checkpoint (mode: Veeam application-aware processing) Details: Job failed (''). Error code: '32768'.
Have Microsoft or Veeam acknowledged this issue yet ?
jed-hyper
Enthusiast
 
Posts: 33
Liked: 4 times
Joined: Wed Feb 26, 2014 4:42 am
Full Name: Jed Parkes

Re: 9.5 Hyper-V 2016 Known Issues

Veeam Logoby Tallwood » Wed Jul 12, 2017 10:03 am

Also having issues with backing up 2016 DC's on 2016 hyper v. I must say Veeam supports response is dreadful, basically just fobbed it off as an MS issue, no evidence that is in fact an MS issue no internal KB that this is a known issue with veeam and no links to bug ID's with MS either basically just left to sort it out ourselves.

Worst of all when veeam has attempted to backup some of these VM's its created checkpoints which then fail to merge when the VM is shutdown and then completely bork the vm itself.
Backup software that doesnt backup supported applications, corrupts VM's and support which isnt particularly proactive, nice one veeam!

Support ID's 02218107 & 02213337
Tallwood
Novice
 
Posts: 6
Liked: 1 time
Joined: Thu Sep 06, 2012 7:23 pm
Full Name: Tom Allwood

Re: 9.5 Hyper-V 2016 Known Issues

Veeam Logoby nmdange » Wed Jul 12, 2017 2:04 pm

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.
nmdange
Expert
 
Posts: 213
Liked: 59 times
Joined: Thu Aug 20, 2015 9:30 pm

Re: 9.5 Hyper-V 2016 Known Issues

Veeam Logoby pedropgracio » Wed Jul 12, 2017 5:26 pm

Case ID# 02198270 and 02211099

Hi Mike, greetings to you all,

same problem here Hyper-V 2016 Cluster with 2012r2 DCs, Veeam support was not very helpful. The support engineer had made remote support session only to prove that the problem is related to Microsoft not appointing any solution. On the other hand I have a similar problem with the replica Job of my SQL server, when it tries to create a checkpoint, on the GuestVM, it hangs on Merging Checkpoint State and crash my Hyper-V Node, problem reported to Microsoft and there is no related bug reported.
pedropgracio
Lurker
 
Posts: 1
Liked: never
Joined: Wed Jul 12, 2017 5:06 pm
Full Name: Pedro Pinheiro

Re: 9.5 Hyper-V 2016 Known Issues

Veeam Logoby TT-DL » Thu Jul 13, 2017 5:08 am

jed-hyper wrote:Have Microsoft or Veeam acknowledged this issue yet ?

No. I have an open support case with them in relation to backing up Exchange 2010 or 2k8r2 and the ADAM VSS writer failing. Microsoft are busy referring me from department to department.
TT-DL
Influencer
 
Posts: 20
Liked: 2 times
Joined: Tue Feb 14, 2017 2:50 am
Full Name: Daniel L

Re: 9.5 Hyper-V 2016 Known Issues

Veeam Logoby TT-DL » Thu Jul 13, 2017 5:10 am 1 person likes this post

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.


I have done alot of work on this issue with both Veeam and Microsoft. Full VSS trace logs have been taken and anaylsed. The summary of that analysis from Veeam is the following:

<Start Snip>
I found more information in the vsstrace. I got some help from a colleague and he was able to find something that will probably be useful.

At the end of the snapshot process, there is an event called onPostSnapshot. At this point the ADAM writer tries to open its own files inside the shadow copy. This is whats failing and ultimately causing the writer to fail. writers sometimes do try to access snapshots like this. But for this the snapshot needs to have an attribute autorecovery. in Hyper-V 2016 this attribute is not set for these snapshots and the snapshot is made read only at the previous event onThaw.

It looks like at least ADAM writer is not working as its suppose to or its not aware of changes related to Hyper-V 2016. this attempt is what we see in the event viewer logs as the file being locked. I'm guessing this is the same issue for the NTDS writer as well.
</End Snip>
TT-DL
Influencer
 
Posts: 20
Liked: 2 times
Joined: Tue Feb 14, 2017 2:50 am
Full Name: Daniel L

Re: 9.5 Hyper-V 2016 Known Issues

Veeam Logoby hintzen_comito » Fri Jul 14, 2017 7:32 am

Hi,

I have this error with a full 2016 system.
Strange thing is, everathing else can be backuped with veeam, but the error still happens on the Backup Server itself (A virtualised server 2016)
All servers in this network are still at version 1607.
hintzen_comito
Lurker
 
Posts: 2
Liked: never
Joined: Fri Jul 14, 2017 7:29 am
Full Name: Philippe Hintzen

Re: 9.5 Hyper-V 2016 Known Issues

Veeam Logoby hintzen_comito » Fri Jul 14, 2017 7:38 am

So I have a error with a Server 2016, that is virtualised with hyper-v
everything else, espect this server, can be backuped without an error, but at this server I get the 32770 error, so I can't make a backup of my backupserver.
All servers, also the Hyper-V, are on server 2016 with build 1607.
Don'T know what the problem is. Does someone know a workaround or fix
hintzen_comito
Lurker
 
Posts: 2
Liked: never
Joined: Fri Jul 14, 2017 7:29 am
Full Name: Philippe Hintzen

Re: 9.5 Hyper-V 2016 Known Issues

Veeam Logoby JTT » Mon Jul 17, 2017 5:26 am

How long has this issue been up?? At this point i as a customer, do not really care who´s fault it is!
Veeam, i have bought Your software, i have paid support for support and it is also Your responsibility to fix it, even if it is Microsofts fault ,then work together, to get this issue resolved.
It seems absurd, that today with Server 2016, i cannot do application aware backup of my most critical servers with DC/Exchange/SQL.
JTT
Novice
 
Posts: 3
Liked: never
Joined: Mon Jan 02, 2017 7:31 am
Full Name: JTT

PreviousNext

Return to Microsoft Hyper-V



Who is online

Users browsing this forum: No registered users and 7 guests