The name of a Nutanix Objects store is an immutable property defined at the time of its creation. Nutanix Prism does not provide a direct "rename" function for an existing object store. Consequently, if a name change is required, the administrator must perform a destructive operation: delete the existing object store and then create a new one with the correct name. Since the request came immediately after creation, no data would be lost in this specific scenario.

A. Enabling or disabling versioning is a feature that applies to data within buckets and has no impact on the core properties, such as the name, of the object store itself.

B. The management capabilities of Nutanix Objects are consistent across supported hypervisors (AHV and ESXi). The inability to rename an object store is a platform limitation, not a hypervisor-specific one.

1. Nutanix Objects 4.0 User Guide

Section: Creating an Object Store. This section outlines the deployment process where the name is a mandatory

initial configuration parameter. The guide does not list the name as a modifiable attribute post-deployment.

2. Nutanix Objects 4.0 User Guide

Section: Managing an Object Store. This section details the available management tasks for an object store

which include updating capacity

managing alerts

and deletion. A "rename" or "edit name" operation is conspicuously absent from the list of supported actions

confirming its immutability.

3. Nutanix University - Nutanix Unified Storage Administration (NUSA) v6.5

Module: Deploying and Managing Nutanix Objects. The courseware demonstrates the object store creation wizard and subsequent management tasks. The labs and materials show that to change a fundamental deployment parameter like the name

the resource must be redeployed.