And just like we saw with the initial deployment, if your vCenter has internet connectivity, you can pull down the new versions automatically. Should a new release of the File Service Agent become available, you can use this feature to provide a rolling upgrade of the agents whilst maintaining full availability of all the file shares. One other feature to point out here is the ‘Check Upgrade’ option. If any of the File Service Agents were to fail on one of the ESXi hosts in the vSAN cluster, this enables the agent to be restarted on any other host in the vSAN cluster and continue to have access to all of the metadata around its file shares, etc. This Distributed File System component is how we share the configuration state (file share names, file share redirects, etc) across all of the File Service Agents. Now an interesting item to highlight in the Introduction screen is the Distributed File System sitting between the NFS File Shares and vSAN. Alternatively, for sites that do not have internet access, you can download the File Service Agent OVF offline. When File Services is Generally Available, you will be able to download the agent image directly from the internet (My VMware I assume). They behave as NFS servers and provide access to the file shares. How File Services is implemented on vSAN is that we implement a set of File Server Agents, managed by vSphere ESX Agent Manager, These are very lightweight, opinionated virtual appliances running Photon OS and Docker.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |