AOS 6.8 Veeam AHV Support/Interoperability/Validation

[ronnmartin61]

@kurtvbmsve76 unfortunately you're 100% correct. I'm just off the phone with my Nutanix counterpart and he confirmed the fix did not make it into 6.8.1.5 after all. Nutanix is continuing to work to get this done as soon as they're able but I don't have any other information to share at this time. We will continue to monitor progress with Nutanix diligently...

[JaySt]

apart from the cause and blame here, i do think it's extraordinary to see this take so long. Veeam is half broken now because of this. 6.8 is the only Nutanix version you can be on right now if you want to be supported (unless you're still on 6.5).
am i missing something in regards to available workaround for restores? i cant do anything untill this is fixed or am i wrong here?
Hard to believe 6.8 customers are stuck in this situation for so long.

[ronnmartin61]

@JaySt admittedly I do not understand either however Nutanix assures us that it's a top priority. To clarify, the specific restore scenario that is broken is "restore-to" new location. Restores to the original VM location will work as expected.

[flow90]

Thank you @JaySt for clarification.

I've got information from Nutanix that the fix is finally in the 6.10 release. For the end of the month.
I hope we'll be out of this soon...

[Kochkin]

According to Nutanix folks, the issue is not yet resolved in 6.8.1.5. Still not sure when the issue will be fixed for 6.8.

[ronnmartin61]

Re-confirmed that 6.10 should drop anytime now. Note that it will require the 6.1 version of our AHV integration which just became available today. According to Nutanix the next 6.8 version due to arrive soon should also include this fix.
In the interim full or instant restore to new location can be made to work by simply creating a VM with the desired restore-to VM name on the target restore cluster. In this way the API call will give us a response we can process correctly and the restore-to will work by creating another VM with that name as the restore target. From a tech support angle we do not yet formally support 6.8 however I know a good many customers have upgraded to this AOS version already.

[Amarokada]

A little confused over the numbers given here. You say Nutanix version 6.10 should release soon, but we're talking about issues in the 6.8 release, so do you actually mean 6.8.6.10 of AOS?

Nvm, it's 6.TEN not 6.1.0. Not sure I like that numbering, easy to mistake for decimal system.

[matthiashoh]

I found that confusing as well. Logically, after 6.8, there should have been a 6.9 release first.

Is anyone up to date on this? Can we expect the update to be released today?

[JaySt]

yes. confused here as well.
Is 6.10 the new LTS release perhaps?
If so, eagerly awaiting ETA numbers on both 6.8 fix-release and 6.10 with the fix.

[ronnmartin61]

Sorry should have been more clear. Nutanix informed us that the API fix to re-establish Veeam compatibility will be in their initial 6.10 release which precedes the 6.8 release that will have a Veeam-compatible API fix. They've said that there is no 6.9 release planned (at least as of our conversation with them last week).

[JaySt]

oh man, can't get a break here last weeks. Now Nutanix pushing a full dot-release faster than the fix i need in the current 6.8 release it seems.

[ronnmartin61]

@JaySt the good news as we understand it is that the 6.8 fixed release should also ship very soon

[matthiashoh]

Yesterday, I attended a small Nutanix presentation where the latest features of version 6.8 were introduced. During the session, I mentioned the bug in conjunction with Veeam, and it was confirmed that there will be a fix for 6.8, and that a new version 6.10 will be released. Interestingly, version 6.9 will be skipped. However, they couldn’t provide a specific release date for the fix. The presenter was not aware of any end-of-September release, but it should be coming soon.

[homerjnick]

Hello, we can confirm that we still get the error on CF/LR headers when on AOS 6.8.1.5 and Veeam version 12.2.0.334.

Can we have an update on when this will be fixed? As we cannot update our cluster version until Veeam works. Is this for Nutanix to remedy?

[ronnmartin61]

@homerjnick yes it's still an issue with 6.8.1.5. As I mentioned a few days ago Nutanix is assuring us it will be in the next 6.8 release and also in the upcoming 6.10. Our AHV v6.1 code is ready for the fixes on either AOS release so yes we're only waiting for Nutanix at this point.

[ryan.odwyer]

Given this is an issue and we need to restore a VM, how can we do that?

Does it need to go all the way back to being converted into a qcow image?

In my case I was restoring from HyperV to Nutanix.

[ronnmartin61]

@ryan.odwyer you can still run a "restore-to-new-location" restore the caveat being that the new restore-to VM name has to already exist on the target Nutanix cluster. In this way we receive an API response code we can deal with and create a new VM instance with the same name to run the restore into.

[flow90]

I guess that AOS 6.10 will be available today. Release note is online.
The Good news is that the issue we're experiencing seems to be fixed !

Prism Gateway
ENG-663089
Resolved an issue where using an aCLI command or an API call to request details of a non-existing VM might resulted in erroneous error messages similar to the following:
The following message was seen with the aCLI command:
acli vm.get <VM UUID> kNotFound: The VmGet request failed: NotFound: 10 :Unknown VMs: <VM UUID>

The following message was seen with the API GET call:
Error occurred while getting VM list:….

https://portal.nutanix.com/page/documen ... ues-r.html

[matthiashoh]

AOS 6.10 is available now in Downloads. Thank you for information

[ronnmartin61]

@flow90, @matthiashoh yes we've deployed in our lab and QA is looking at it now. No ETA quite yet for a formal support announcement but I'll keep this thread updated. Of course and feedback anyone has from their 6.10 / 6.1 AHV plugin testing is welcome here...

[JaySt]

good to know! We'll upgrade to 6.10 in less than 2 weeks as it seems. i think we'll see some others on here updating before that.

[flow90]

Based on my initial tests, the restorations are working well in all cases (whether with VM overwrite or as a clone). The backups also encountered no errors, and the performance is on par with what we had previously.

[ronnmartin61]

Wanted to let everyone know that we've completed validation for AOS 6.10 and our v6.1 AHV plugin and we're working to get helpcenter system requirements updated accordingly. We've found only one issue so far and it's on our end so we will likely create a patch (timing TBD). The issue is noted in the v6.1 release KB - https://www.veeam.com/kb4668. Also spoke with Nutanix this morning and they re-confirmed that the next 6.8 release will contain the API fix for that code branch as well.

[jim.lowry]

Hey all, I think it figured out why Nutanix AOS v6.9 was not used - why they went from 8 to 10. It's likely because version 7 ate 9.

[JaySt]

i see 6.10 is on the helpcenter sys requirements page.
Ok, good to go.

[ItsMeThatsAll]

@ryan.odwyer you can still run a "restore-to-new-location" restore the caveat being that the new restore-to VM name has to already exist on the target Nutanix cluster. In this way we receive an API response code we can deal with and create a new VM instance with the same name to run the restore into.

I tried creating a new machine with the name new_<original>_restored, tried to restore (new machine with prefix and suffix) but failure still there! Did you do it?
I can not upgrade to AOS 6.10 right now but need to check my restorations.

[ronnmartin61]

@ItsMeThatsAll hmmm...if you create an AHV VM such as new_myvmname_restored and then run a restore to new location on VM myvmname to new_myvmname_restored it should work correctly with 6.8.x. Is that what you're attempting?