Based on what you are using the Windows 10 machines should be supported.  Check this page which shows the compatible versions using Agent version 6 - System Requirements - Veeam Agent for Microsoft Windows Guide

Hi @HYF_JE -

Forgive me for my lack of NTX knowledge, but will try and share what could be going on by what’s in the NTX User Guide.

First, are you using VBR or the NTX Web Console to restore?...I assume Veeam? Are you choosing to restore to Orig or New location? Selecting Storage Containers, and thus Disks, is only possible when restoring to New location or With different settings, per the User Guide:

https://helpcenter.veeam.com/docs/vbahv/userguide/restore_to_ahv_container.html?ver=50

VBR console. Original location is impossible (physical machines with bare metal Windows installation > Nutanix virtual machine), so it is always a new location.

For Agent recovery, you cannot use Instant Recovery for those if you’re choosing “File level” backup type on the Agent. Volume and Entire Computer backups should work though.

See: https://helpcenter.veeam.com/docs/vbahv/userguide/instant_recovery_ahv.html?ver=50

Also, your backups must be on a Veeam-based Repo, not a repository/storage location on the Agent backed up system (as shown in the link above, as well).

All that being said, it’s weird you’re able to see the disks with a diff Windows type.

Ah yes...of course 

I did find that in my research too. We are not using File level backup for these jobs, they are all “Entire Computer”.

Yes, the backups in question are going to performance extents within a SOBR. The only consistent variable I have so far identified is whether the system being backed up is a Windows client or server.

It sounds like you’ve done your due diligence. Since you’re not really wanting to go the Support route as of yet, you could potentially post this question on the Forums to see if the Product Managers have come across this behavior. They can have the QA team test it out and see if there is indeed a bug.

This is what I would suggest as well but I think it is going to come down to Support request unfortunately.

Yeah I figured community was better because in my experience the R&D folks want an existing support case (which is reasonable, I suspect so they have a better chance at logs and such) before looking into it too much.

For something like this, thought I’d try out the community route.

The community is good but we can only give so much advice and eventually it will require technical help.  As we say to many we are not technical support just Veeam enthusiasts. 

You’re correct...they do; sometimes they don’t though. But, probably more times than not they may request case ID.

Posted to R&D forums.

Veeam Windows Agent Restore Confusion - R&D Forums

That is good.  Will keep an eye over there as well to see how it goes.  Best of luck. 

If you are taking backups from Windows agents and trying to restore or Instant VM recovery to AHV you need the Nutanix VirtIO installed in the VM (scsi drivers). This will allow you to see the the disks. You can download on Nutanix site at link below.It requires a Nutanix login.

(Nutanix VirtIO is a collection of drivers for para-virtual devices that enhance the stability and performance of virtual machines on AHV.)

https://my.nutanix.com/page/login?client_id=X90v3suh7g4OkrFehHiZQefPPFca&commonAuthCallerPath=%2Foauth2%2Fauthorize&forceAuth=false&passiveAuth=false&redirect_uri=https%3A%2F%2Fportal.nutanix.com%2Fapi%2Fv1%2Foauth2%2Fwso2%2Fcallback&response_type=code&scope=openid&state=successRedirect%3Dhttps%253A%252F%252Fportal.nutanix.com%252Fpage%252Fdownloads%253Fproduct%253Dahv%2526bit%253DVirtIO&tenantDomain=carbon.super&sessionDataKey=75f0f75a-bfce-48cb-99ba-72eacef61d50&relyingParty=X90v3suh7g4OkrFehHiZQefPPFca&type=oidc&sp=support-portal-prod&isSaaSApp=false

That’s not the problem here. We don’t even get far enough into the restore for driver compatibility to be part of the equation. While a restored physical > virtual VM may fail to boot, Veeam should at least be able to restore the VM to a “non-booting” state. Here I am specifically thinking about Entire VM restore. I haven’t worked enough with instant recovery to know just how much it differs. My understanding is instant recovery simply “abuses” NFS or similar technologies to get the VM mounted to the hypervisor ASAP even if the storage performance isn’t comparable to production SAN/HCI/storage.

There seems to be something else going on then have you installed the latest AHV plug-in and meet the minimum requirements? links to doc below. Please share screen shots. It might be good to a trouble ticket started. Have you checked AHV tasks and seen any messages indicating any errors?

https://helpcenter.veeam.com/docs/vbahv/userguide/install_ahv_services.html?ver=50

https://helpcenter.veeam.com/docs/vbahv/userguide/system_requirements.html?ver=50

I’m hesitant to provide screenshots/details of production systems outside of support cases.

I can say with relative certainty we are running the latest plugin, AHV appliance version, and system requirements are more than met.

Definitely would suggest a Support ticket at this point then so you can get this worked out.

I don’t know if it was coincidence, but today I upgraded from VBR 12.1.0.2131 to 12.1.1.56 and this issue appears to be resolved.

Ironically, I was installing 12.1.1.56 in an attempt to resolve a different issue. The upgrade didn’t fix that issue, but it did fix this one.

Forum admins/mods, if you’re able to unmark the old solution and mark this one as the correct solution that’d be great.

Hi @safiya kindly take a look at this request.