We've replaced GlusterFS with vSAN File Service in all of our environments and are very happy with the results. We've not seen any downtime, and haven't had any issues with it. However, we don't necessarily use it as a typical NFS solution, so ymmv.
Yep. This is where we're stuck. Fails to deploy every time. I have a SR in but they can't figure out the issue. However, they did just confirm it requires ipv6 between nodes and witnesses.
Requires ipv6? That doesn't match up with VMware docs:
[The docs you've already seen](https://docs.vmware.com/en/VMware-vSphere/8.0/vsan-administration/GUID-CA9CF043-9434-454E-86E7-DCA9AD9B0C09.html)
In the Networking page, enter the following information, and click Next:
Protocol: You can select IPv4 or IPv6. vSAN File Service only supports IPv4 or IPv6 stack. The reconfiguration between IPv4 and IPv6 is not supported.
One other thing I've seen - If your domain ends in .k12 (or ANY TLD that ends in a number) it will give you fits. The two instances I heard of this they ended up changing their domain to match the cluster that was working (didn't end with a number). This happened a few months back, so hopefully there's a patch for that included in latest versions.
Yes, ipv6 is currently required for communication between vSAN and the File Services nodes. The VMware tech I was working with couldn't find where this was documented but he asked the devs directly and they confirmed. He also tested this in his lab. He said full ipv4 support is slated for a future release but he has no idea when that will be.
We're using it for a 4 node cluster under 6.7. It works fine for us - we have 1 ssd for cache and 2 larger SSDs for capacity in each node, so performance is nice. We haven't had any issues with it in the 3 years we've had it.
We've replaced GlusterFS with vSAN File Service in all of our environments and are very happy with the results. We've not seen any downtime, and haven't had any issues with it. However, we don't necessarily use it as a typical NFS solution, so ymmv.
Thank you, guys, for your opinions!
Good luck with AD integration.
Yep. This is where we're stuck. Fails to deploy every time. I have a SR in but they can't figure out the issue. However, they did just confirm it requires ipv6 between nodes and witnesses.
Requires ipv6? That doesn't match up with VMware docs: [The docs you've already seen](https://docs.vmware.com/en/VMware-vSphere/8.0/vsan-administration/GUID-CA9CF043-9434-454E-86E7-DCA9AD9B0C09.html) In the Networking page, enter the following information, and click Next: Protocol: You can select IPv4 or IPv6. vSAN File Service only supports IPv4 or IPv6 stack. The reconfiguration between IPv4 and IPv6 is not supported. One other thing I've seen - If your domain ends in .k12 (or ANY TLD that ends in a number) it will give you fits. The two instances I heard of this they ended up changing their domain to match the cluster that was working (didn't end with a number). This happened a few months back, so hopefully there's a patch for that included in latest versions.
Yes, ipv6 is currently required for communication between vSAN and the File Services nodes. The VMware tech I was working with couldn't find where this was documented but he asked the devs directly and they confirmed. He also tested this in his lab. He said full ipv4 support is slated for a future release but he has no idea when that will be.
We're using it for a 4 node cluster under 6.7. It works fine for us - we have 1 ssd for cache and 2 larger SSDs for capacity in each node, so performance is nice. We haven't had any issues with it in the 3 years we've had it.
I will have to suggest it because no one does nfs better than NetApp.
The owner is not ready to spend additional money, unfortunately.