External Datastores

  • 2 November 2021
  • 2 replies


We have two Nutanix clusters running ESXi v6.7.0 with a Horizon 7 VDI environment on each.  We needed to be able to sync Horizon AppVolumes between the clusters via some common storage.

The solution we were set up with was a FreeNAS VM on one cluster publishing an NFS share which was then attached to the hosts in both clusters.  We weren’t bothered about high availability as it’s not an issue if the replication of the appvolumes goes down sometimes as it’s only needed if appvolumes are being changed or their assignments to users is changing.

After an NCC upgrade, Prism Element now flags up this external datastore as unsupported.  I’m struggling to find out from Support what the actual magnitude of risk is here to the stability of the clusters (especially when it comes to upgrading firmwares, AOS etc).

Does anyone here have any thoughts on this situation please?

Thanks for reading!


Best answer by Cantoris 5 November 2021, 15:55

View original

This topic has been closed for comments

2 replies

Userlevel 4
Badge +5

HI @Cantoris,

Cant you create a volume group and attach it to the needed machines?

Thanks for the reply!

I did mention this to Support but they said it would also fail the NCC check as it would “still use the vmkernel and CVM for the IO”.

There’s actually a solution article for the exact setup and situation we’re in (bottom section): VMware App Volumes in a Multisite Deployment

Apparently what that article suggests would also be flagged up by NCC under this check!

Nutanix have now advised me that they believe the risk in our case to be minimal and to leave as is.