Dell PowerStore 3000T EMC PowerStore Virtualization Infrastructure Guide - Page 24

6 Best practices and limitations Topics: • Internal components visible in vCenter Server • Block access for LUNs • Service and recovery • vSphere limitations • Other limitations Internal components visible in vCenter Server Some system components are visible as manageable objects in the vSphere Web Client, but modifying them can cause data loss or unavailability. Critical system components CAUTION: Do not modify any of the following internal components: ● Configuration files ● BIOS settings ● PowerStore X model controller VM resource assignments ● PowerStore X model internal nodes, which appear as ESXi hosts ● M2 device ● Internal datastores PowerStore X model controller VMs The PowerStore X model controller VM is displayed in the vSphere Web Client as an object that can be managed, but some operations should not be performed on it. Do not migrate the PowerStore X model controller VM to a user-created resource pool. The PowerStore X model controller VM must remain in the default resource pool on the cluster. Do not power off the PowerStore X model controller VM. Internal datastores For each node in the cluster, the vSphere Web Client displays and enables modification of the internal datastore that the PowerStore X model controller VM uses. Do not create VMs on internal datastore, or otherwise modify it. The internal datastores are named as follows: ● PRIVATE-.A.INTERNAL ● PRIVATE-.B.INTERNAL Groups and rules vCenter Server supports the creation of VM groups, host groups, and host rules to manage affinity between VMs and hosts in a cluster. 24 Best practices and limitations