Consider the following when configuring vSAN File Service:

  • vSAN 8.0 supports two-node configurations and stretched clusters.
  • vSAN 8.0 supports 64 file servers in a 64 host setup.
  • vSAN 8.0 supports 100 file shares.
  • vSAN 8.0 Update 2 supports File Service on Express Storage Architecture (ESA).
  • vSAN 8.0 Update 3 ESA cluster supports 250 file shares. Out of those 250 file shares, maximum 100 file shares can be SMB. For example, if you create 100 SMB file shares then the cluster can only support additional 150 NFS file shares.
  • vSAN File Services does not support the following:
    • Read-Only Domain Controllers (RODC) for joining domains because the RODC cannot create machine accounts. As a security best practice, a dedicated org unit should be pre-created in the Active Directory and the user name mentioned here should be controlling this organization.
    • Disjoint namespace.
    • Multi domain and Single Active Directory Forest environments.
  • When a host enters maintenance mode, the file server moves to another FSVM. The FSVM on the host that entered maintenance mode is powered off. After the host exits maintenance mode, the FSVM is powered on.
  • vSAN File Services VM (FSVM) docker internal network may overlap with the customer network without warning or reconfiguration.

    There is known conflict issue if the specified file service network overlaps with the docker internal network ( This causes routing problem for the traffic to the correct endpoint.

    As a workaround, specify a different file service network so that it does not overlap with the docker internal network (