Dell PowerStore 3000X EMC PowerStore Virtualization Infrastructure Guide - Page 25

Block access for LUNs, Service and recovery, Support for VSS, vSphere limitations

Get Dell PowerStore 3000X PDF manuals and user guides View all Dell PowerStore 3000X manuals
Add to My Manuals
Save this manual to your list of manuals

Page 25 highlights

● Do not place PowerStore X model controller VMs in a user-created VM group. ● The ESXi hosts may be placed in a user-created host group. ● User-created VMs may be placed in a user-created VM group. Block access for LUNs VMs running on internal PowerStore X model nodes can only use vVol based storage. VMFS-based storage is not supported for VMs running on internal PowerStore X model nodes. However, PowerStore X model appliances can also be used as external block storage using iSCSI or Fibre Channel. The block storage can be formatted as VMFS datastores and be presented to external servers and VMs running outside of the internal PowerStore X model nodes. NOTE: While user VMs can use guest operating system iSCSI initiators to access LUNs, this method is not recommended. The best practice is to use the VASA provider link or run VMs locally using vVols. Service and recovery The PowerStore virtualization configuration affects some of the troubleshooting processes that an experienced virtualization administrator may be familiar with. Some administrator operations on the PowerStore X model VM or ESXi host can harm the system or cause service issues. Support for VSS PowerStore clusters support third-party snapshot integration for Microsoft Volume Shadow Copy Service (VSS) to simplify protection of Microsoft applications such as SQL Server and Outlook. vSphere limitations PowerStore X model appliances inherit some limitations that are inherent to vSphere. Number of supported objects vSphere has a limit to the number of VMs, and other objects it can support. For information, see the VMware vSphere documentation. NOTE: Use individual hosts instead of host groups in large scale vVol based vSphere environments with more than 4096 vVols. CPU and memory usage PowerStore X model controller VMs always report high CPU and memory usage in vSphere. The high CPU and memory usage is normal because PowerStore X model appliances reserve 50% of the CPU and memory resources to run controller VMs. PowerStore X model controller VMs might trigger a memory usage alarm in ESXi 6.x. Best practices and limitations 25

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
●
Do not place PowerStore X model controller VMs in a user-created VM group.
●
The ESXi hosts may be placed in a user-created host group.
●
User-created VMs may be placed in a user-created VM group.
Block access for LUNs
VMs running on internal PowerStore X model nodes can only use vVol based storage. VMFS-based storage is not supported for
VMs running on internal PowerStore X model nodes.
However, PowerStore X model appliances can also be used as external block storage using iSCSI or Fibre Channel. The block
storage can be formatted as VMFS datastores and be presented to external servers and VMs running outside of the internal
PowerStore X model nodes.
NOTE:
While user VMs can use guest operating system iSCSI initiators to access LUNs, this method is not recommended.
The best practice is to use the VASA provider link or run VMs locally using vVols.
Service and recovery
The PowerStore virtualization configuration affects some of the troubleshooting processes that an experienced virtualization
administrator may be familiar with.
Some administrator operations on the PowerStore X model VM or ESXi host can harm the system or cause service issues.
Support for VSS
PowerStore clusters support third-party snapshot integration for Microsoft Volume Shadow Copy Service (VSS) to simplify
protection of Microsoft applications such as SQL Server and Outlook.
vSphere limitations
PowerStore X model appliances inherit some limitations that are inherent to vSphere.
Number of supported objects
vSphere has a limit to the number of VMs, and other objects it can support. For information, see the VMware vSphere
documentation.
NOTE:
Use individual hosts instead of host groups in large scale vVol based vSphere environments with more than 4096
vVols.
CPU and memory usage
PowerStore X model controller VMs always report high CPU and memory usage in vSphere. The high CPU and memory usage is
normal because PowerStore X model appliances reserve 50% of the CPU and memory resources to run controller VMs.
PowerStore X model controller VMs might trigger a memory usage alarm in ESXi 6.x.
Best practices and limitations
25