To grant access of a Dell Unity XT provisioned NFS datastore to an ESXi host, the permission level required for the host depends on the NFS protocol and authentication method used by the NAS server. For NFSv4 with Kerberos NFS owner authentication, the ESXi host must have the Read/write, enable Root permission level. This allows the ESXi host to read and write data to the datastore, as well as perform administrative tasks such as creating and deleting virtual machines. The Read/write permission level alone is not sufficient, as it does not allow the ESXi host to perform root-level operations on the datastore.The Read-only permission level only allows the ESXi host to read data from the datastore, but not write or modify it.Reference: Dell EMC Unity: Configuring hosts to access NFS1, page 9.

A characteristic of Host Groups is that block storage resources added to a host group are accessible to all the member hosts. A Host Group is a logical grouping of hosts that share the same access permissions and settings for block storage resources. By adding block storage resources to a host group, the user can simplify the management and allocation of storage for multiple hosts. Access to block storage resources does not need to be set before adding hosts to a host group, as the access permissions can be modified later. Hosts added to a host group can have mapped block storage resources, as long as they are not in conflict with the host group resources. Block storage resources attached to one of the member hosts are not accessible to the entire host group, unless they are also added to the host group.

The snapshot option that is set automatically when a pool is configured is the Pool Automatic Deletion Policy. This option determines how the system handles the deletion of snapshots when the pool reaches a certain threshold of capacity utilization. The user can choose between three policies: Never Delete, Delete Oldest, or Delete Lowest Priority. The Total Pool Consumption and the Snapshot Pool Consumption are not snapshot options, but rather metrics that show the amount of pool space consumed by the pool data and the snapshots respectively.

Mixing FC and iSCSI protocols for the same host and array is not supported by Dell EMC Unity. This can cause issues with multipathing, failover, and performance. The best practice is to use one protocol per host and array pair.If the host needs to access both FC and iSCSI LUNs from different arrays, then separate vSwitches and port groups should be used for each protocol.Reference: Dell EMC Unity: Best Practices Guide1, page 19.

Two actions that are recommended according to best practices when connecting iSCSI host to a Dell Unity XT system are to ensure that the interfaces are on separate subnets and to use a private network for iSCSI interfaces. These actions can improve the performance, security, and availability of the iSCSI network. Having interfaces on separate subnets can prevent broadcast storms, reduce network congestion, and enable multipathing. Using a private network for iSCSI interfaces can isolate the iSCSI traffic from other network traffic, reduce the risk of interference or attacks, and simplify the network configuration. Manually registering host on storage array and using standard NIC for iSCSI are not recommended actions, as they can introduce errors, inefficiencies, and limitations.