To scale out an existing Files instance, the administrator needs to add one Client IP and one Storage IP for each additional FSVM. Since the Files instance needs to expand from four FSVMs to six FSVMs, the administrator needs to add two Client IPs and two Storage IPs in total. The Client IPs are used for communication between the FSVMs and the clients, while the Storage IPs are used for communication between the FSVMs and the CVMs. Reference: Nutanix Files Administration Guide, page 28; Nutanix Files Solution Guide, page 7

The action that the administrator should take to resolve this issue is to verify Access Keys for the user. Access Keys are credentials that allow users to access Objects buckets using S3-compatible APIs or tools. Access Keys consist of an Access Key ID and a Secret Access Key, which are used to authenticate and authorize requests to Objects. If the user is unable to write data in the bucket using an Active Directory account, it may be because the user does not have valid Access Keys or the Access Keys do not have sufficient permissions. The administrator can verify and manage Access Keys for the user in Prism Central. Reference: Nutanix Objects User Guide, page 13; Nutanix Objects Solution Guide, page 8

Before upgrading Objects Manager, the administrator must upgrade AOS to the latest version. AOS is the core operating system that runs on each node in a Nutanix cluster and provides the foundation for Objects Manager and Objects service. Upgrading AOS will ensure compatibility and stability for Objects components. Reference: Nutanix Objects Administration Guide, Acropolis Operating System Upgrade Guide

The administrator should resolve this issue by using the Files MMC Snap-in and renaming the folders. The Files MMC Snap-in is a tool that allows administrators to manage Files shares and exports from a Windows machine. The administrator can use the Files MMC Snap-in to connect to a distributed share or export and rename the top-level directories that are hosted by different FSVMs. Renaming the directories from Windows Explorer will not work because Windows Explorer does not recognize the distributed nature of the share or export and will try to rename all directories on the same FSVM, which will fail. Reference: Nutanix Files Administration Guide, page 35; Nutanix Files MMC Snap-in User Guide

The prerequisite that must be performed before performing one-click hypervisor upgrades is to disable the anti-affinity rules on all FSVMs. Anti-affinity rules are rules that prevent two or more VMs from running on the same host at the same time. Anti-affinity rules can improve the availability and performance of FSVMs by distributing them across different hosts in a cluster. However, anti-affinity rules can interfere with one-click hypervisor upgrades, which require all VMs on a host to be migrated to another host before upgrading the host. Therefore, the administrator must disable the anti-affinity rules on all FSVMs before performing one-click hypervisor upgrades, and re-enable them after the upgrades are completed. Reference: Nutanix Files Administration Guide, page 22; Nutanix Files Upgrade Guide