Dell EMC PowerStore Virtualization Guide · PowerStore virtualization terminology and definitions...

Dell EMC PowerStoreVirtualization Guide

1.x

June 2020Rev. A01

Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the

problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

© 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Othertrademarks may be trademarks of their respective owners.

Additional Resources...................................................................................................................... 5

1 Introduction................................................................................................................................. 6Purpose...................................................................................................................................................................................6Audience................................................................................................................................................................................. 6

2 Overview..................................................................................................................................... 7PowerStore virtualization terminology and definitions......................................................................................................7

Virtual volumes overview................................................................................................................................................8Storage containers overview......................................................................................................................................... 9

Virtualization architecture and configuration.................................................................................................................... 11Working with virtual resources............................................................................................................................................11

3 Getting started...........................................................................................................................14Hypervisor configuration for PowerStore X model appliances...................................................................................... 14

VMware licensing........................................................................................................................................................... 14vCenter and vSphere configuration changes............................................................................................................. 15ESXi passwords.............................................................................................................................................................. 16Configure a vCenter Server connection to a PowerStore T model cluster............................................................17

Using an external ESXi host with a PowerStore cluster................................................................................................. 18Network configuration for PowerStore X model appliances ......................................................................................... 18

4 Virtualization configuration in PowerStore appliances................................................................... 20Managing virtualization components in the PowerStore Manager...............................................................................20

Monitoring and managing VMs....................................................................................................................................20Monitoring and managing vVols................................................................................................................................... 21Monitoring and managing storage containers............................................................................................................ 21

Change a vCenter Server connection.............................................................................................................................. 22Additional VMware software and configuration.............................................................................................................. 22Upgrading PowerStore X model appliances.....................................................................................................................23

Upgrade readiness for PowerStore X model appliances.......................................................................................... 23Upgrading PowerStore X model node firmware........................................................................................................24Updating the internal ESXi hosts.................................................................................................................................25Upgrading the PowerStore OS ...................................................................................................................................26

5 VMware NSX-V.......................................................................................................................... 28VMware NSX-V introduction.............................................................................................................................................28Add internal ESXi hosts to an existing NSX-V deployment........................................................................................... 28

6 Best practices and limitations..................................................................................................... 29Internal components visible in vCenter Server................................................................................................................29Block access for LUNs........................................................................................................................................................29Service and recovery.......................................................................................................................................................... 30

Support for VSS............................................................................................................................................................ 30

Contents

Contents 3

vSphere limitations..............................................................................................................................................................30VMware snapshot limitations.......................................................................................................................................30

Other limitations.................................................................................................................................................................. 30

4 Contents

Additional ResourcesAs part of an improvement effort, revisions of the software and hardware are periodically released. Some functions that are described inthis document are not supported by all versions of the software or hardware currently in use. The product release notes provide the mostup-to-date information about product features. Contact your technical support professional if a product does not function properly ordoes not function as described in this document.

Where to get helpSupport, product, and licensing information can be obtained as follows:

• Product information

For product and feature documentation or release notes, go to the PowerStore Documentation page at www.dell.com/powerstoredocs.

• Troubleshooting

For information about products, software updates, licensing, and service, go to www.dell.com/support and locate the appropriateproduct support page.

• Technical support

For technical support and service requests, go to www.dell.com/support and locate the Service Requests page. To open a servicerequest, you must have a valid support agreement. Contact your Sales Representative for details about obtaining a valid supportagreement or to answer any questions about your account.

Preface

Additional Resources 5

https://www.dell.com/powerstoredocs

https://www.dell.com/powerstoredocs

https://dell.com/support


Introduction

PurposeThis document provides a brief overview of virtualization, how it is implemented in PowerStore clusters, virtualization-specificconfiguration information, and common tasks and workflows.

AudienceThe information in this guide is primarily intended for:

• System administrators who are responsible for a wide range of technologies in their organization including basic storage management• Storage administrators who manage the operations of storage infrastructure within their organization• Virtualization administrators who deliver and maintain the virtual infrastructure for their organization

Users should have current practical experience with the following topics:

• Managing virtual machines and ESXi hypervisors with the embedded VMware vSphere Web Client• Accessing the ESXi Shell in order to use ESXCLI commands• Using other VMware management interfaces such as PowerCLI

1

6 Introduction

Overview

PowerStore virtualization terminology anddefinitionsPowerStore clusters use a specific implementation of virtualization concepts that are based in a VMware vSphere framework.

Virtual machinesVirtual machines (VMs) provide software abstractions of computer hardware and operating system resources that are managed on asingle device. PowerStore clusters support both VMFS and vVol-based VMs.

The VMs that run internally on PowerStore X model appliances must use vVol storage. PowerStore X model appliances also supportserving storage externally using Fibre Channel and iSCSI protocols. The support for Fibre Channel and iSCSI protocols enables VMs onexternal ESXi hosts to use VMFS or vVol storage from PowerStore X model appliances. PowerStore T model clusters can also providestorage to VMs using either VMFS or vVol storage.

PowerStore X model appliances include two native ESXi host instances. One ESXi host is installed on the physical hardware of each node.The ESXi host for each node is also provisioned with an internal controller VM that runs the PowerStore OS. The PowerStore X modelappliance allocates some of its CPU and memory resources for the controller VMs and user VMs.

Virtual VolumesA VMware Virtual Volume (vVol) is an object type that corresponds to VM files, virtual disks, and their derivatives. On the cluster, vVolsreside in storage containers.

For more information, see Virtual volumes overview on page 8.

Protocol endpointsProtocol endpoints are logical I/O proxies that the ESXi host uses to communicate with vVols and are required for working with vVols.

For more information, see Protocol Endpoints on page 8.

VASA providerPowerStore clusters use vSphere APIs for Storage Awareness (VASA) to allow vCenter and ESXi to manage and monitor vVols hosted onthe cluster.

VASA enables the basic information about the storage system and storage resources on PowerStore clusters to be made available to thevCenter Server. This information includes storage policies, properties, and health status.

By using VASA, the vCenter Server and the PowerStore clusters to establish two-way out-of-band communication to perform dataservices and offload certain VM operations to the cluster. For example, operations such as snapshots and clones can be performed usingPowerStore Manager.

A VASA provider is a management server that supports vVol commands using the vSphere APIs. A VASA provider must be registered withthe vCenter Server to use vVols.

• The PowerStore X model appliance configuration includes an automatically registered VASA provider.• To use vVols on a PowerStore T model cluster, you must manually register the VASA provider on the PowerStore T model cluster from

the vCenter Server.

Registering a VASA provider also gives users the ability to view vVols and associated VMs directly from PowerStore Manager.

2

Overview 7

Storage containersA storage container is a pool of raw storage capacity or an aggregation of storage capabilities that a cluster can provide to the VMwareenvironment. On a PowerStore cluster, it acts as a logical grouping of vVols that enables vVols to map directly to an appliance.

When presented to ESXi hosts, the storage container is equivalent to a vVol datastore. The storage container spans across all appliancesand is part of a single PowerStore cluster. Because of the scale-out design of PowerStore, vSphere is not aware on which appliance thevVol is located.

A storage container may represent a tenant or business unit.

For more information, see Storage containers overview on page 9.

Storage Policy Based ManagementvVols uses Storage Policy Based Management (SPBM) to ensure VMs have the appropriate storage capabilities through their entire lifecycle. VM storage policies can be optionally created after the storage provider is registered. These policies are used to determine thestorage capabilities when a VM is being provisioned. For information about creating a VM storage policy, see the VMware vSpheredocumentation.

vCenter ServersvCenter Servers provide a centralized management interface for VMs.

The PowerStore X model appliance is connected to vCenter Server during initial system configuration.

To connect an existing vCenter Server in your environment to a PowerStore T model cluster, you must register the VASA provider of thecluster to the vCenter Server manually. Then, set up the vCenter Server connection with PowerStore Manager.

Virtual volumes overviewA VMware Virtual Volume (vVol) is a VMware ESXi storage abstraction.

vVol provisioningvVols are provisioned in vCenter Server and correspond to VM files, virtual disks, and their derivatives. Different management actionsautomatically generate different vVols that are associated with a VM.

Management action vVols created

Create a VM • Data-vVol (.vmdk)

• Config-vVol

Power on a VM Swap-vVol (.vswp)

Create a snapshot of a VM • Data-vVol (.vmdk)

• Memory-vVol (.vmem)

Clone a VM • Data-vVol (.vmdk)—Shown as type Clone in PowerStore Manager

• Config-vVol

Add a virtual disk • Data-vVol (.vmdk)

• Config-vVol—if a config-vVol of the same VM does not exist on the storage container

On the PowerStore cluster, each vVol provisioned in vCenter Server is visible as a vVol in PowerStore Manager. For more information, seeStorage containers overview on page 9.

Protocol EndpointsA Protocol Endpoint (PE) is an internal object in storage systems and appliances that is required for working with vVols.

8 Overview

Without a PE, the PowerStore cluster can manage vVols, but the ESXi host has no access to them. To gain access, ESXi hostscommunicate with vVols through a PE. The PE serves as a logical I/O proxy that enables the ESXi host to establish data paths to vVolsand their associated VMs.

PowerStore clusters automatically create and provision PEs when adding an ESXi host. To work with vVols, add a host and select theOperating System type ESXi when prompted.

PowerStore X model appliances support only the iSCSI protocol for internal ESXi hosts, but support both iSCSI and Fibre Channelprotocols for external hosts.

PowerStore Manager operationsFor information about using vVols in PowerStore Manager, see Monitoring and managing vVols on page 21.

Storage containers overviewStorage containers on PowerStore appliances act as a logical grouping of vVols that enable vVols to map directly to the cluster.

A storage container spans all appliances in a cluster and uses storage from each. On PowerStore appliances, vVols reside in storagecontainers, which enable vVols to map directly to an appliance within the PowerStore cluster. The specific appliance that a given vVolresides on is not visible to vSphere, and a vVol can migrate between appliances without disrupting vSphere operations. With storagecontainers, VMs or VMDKs can be managed independently.

Figure 1. Storage containers spanning appliances in a PowerStore T model cluster

Overview 9

Figure 2. Storage containers on one appliance in a PowerStore X model cluster

Storage containers for PowerStore ESXi hostsDuring the initial PowerStore X model appliance configuration process, a default storage container that is named (PowerStore<cluster name>) is automatically provisioned on the cluster. The default storage container on PowerStore X model appliance ismounted to the internal ESXi hosts during initial configuration.

To use storage containers with an external ESXi host:

1. Connect an external ESXi host to your PowerStore cluster.2. Create an ESXi host in PowerStore Manager.3. Use PowerStore Manager to create a storage container.

For more information, see Create a storage container on page 214. Use the vSphere Web Client or CLI to mount the storage container on the external ESXi host.

For more information, see VMware vSphere product documentation.5. Create a vVol datastore from this vVol Storage Container and begin using it as a datastore for VMs.

MultitenancyAll PowerStore appliances support multiple storage containers on a cluster. To support multitenancy requirements, multiple storagecontainers can be created allowing the separation of physical VMs and associated vVols from one tenant to another.

ISOs vVolDuring PowerStore X model cluster initialization, a 500 GB config-vVol that is named ISOs is created in the default storage container.This vVol can store any type of file, but is intended to hold ISO images, such as guest operating system installation files, and VMtemplates. Use this vVol to hold large ISO images that do not fit in a vSphere-created datastore folder, which has a default size of 4 GB.

The ISOs vVol is listed in the vSphere datastore browser as a directory and appears on the vVols card of the default storage container inPowerStore Manager. Because a storage container cannot be deleted if it contains a vVol, the default storage container cannot be deletedwhile it contains the ISOs vVol.

10 Overview

PowerStore Manager operationsFor information about using storage containers in PowerStore Manager, see Monitoring and managing storage containers on page 21.

Virtualization architecture and configuration

PowerStore X model configurationThe PowerStore X model configuration provides a hypervisor layer in addition to block storage. VMware ESXi is the base operating systemrunning on the PowerStore hardware, with the PowerStore OS running as a VM. The PowerStore X model appliance reserves 50% of theCPU and memory resources to run the controller VMs. The remaining CPU and memory resources are available for user VMs.

This application-centric configuration enables you to run applications in other VMs on the PowerStore hardware.

The PowerStore Resource Balancer works with vSphere DRS to automatically manage the placement of VMs and vVols to balance theload across the PowerStore X model appliance. Resources are moved and deployed to locations based on rules to facilitate high availability(HA). HA is enabled by default, and VMs fail over as necessary based on resource availability on the remaining nodes.

In general, this behavior does not impact the daily operation or management of a PowerStore X model appliance. However, there are someconsiderations for storage administrators. The PowerStore X model appliance uses federated rather than distributed storage. Thisconfiguration may impact where a storage administrator chooses to locate resources within a data center, and how VM loads are set upfor satisfactory performance.

PowerStore T model configurationIn the PowerStore T model configuration, the PowerStore OS runs directly on the PowerStore hardware.

To add vVol-based VMs in this configuration, you must add ESXi hosts and a vCenter Server connection with a VASA provider. Some ofthe virtualization features available on PowerStore X model appliances are not available in this configuration. To add VMFS-based VMs inthis configuration, you do not have to add a vCenter Server connection with a VASA provider, but it is still recommended.

For PowerStore T model clusters, the PowerStore Resource Balancer manages the placement of vVols and keeps vVols for the same VMon the same appliance in a cluster. You can also manually migrate a vVol from one appliance to another using the Virtual Volumes card ofthe associated VM in PowerStore Manager.

Working with virtual resourcesThe PowerStore Manager provides detailed monitoring capabilities for connected VMs. To manage VMs, you can launch the vSphere WebClient from PowerStore Manager.

PowerStore Manager operationsFrom the Compute > Virtual Machines page in the PowerStore Manager, you can view performance details, alerts, and connections forthe VMs that are using vVol storage from your PowerStore cluster. You can also view and manage data protection policies.

Only VMs that are deployed on vVols can be managed with PowerStore Manager. VMs on legacy non-vVol datastores are not displayed inPowerStore Manager.

For detailed information about the VM operations you can perform from the PowerStore Manager, see Monitoring and managing VMs onpage 20.

vCenter Server operationsAny VM operations that cannot be performed from the PowerStore Manager must be completed from the vCenter Server. From theCompute > vCenter Server Connection page in the PowerStore Manager, you can click LAUNCH VSPHERE to start the vSphereWeb Client and connect to the vCenter Server. For additional guidance, see the product documentation for the version of vCenter Serveryou are using.

Overview 11

Workflow using PowerStore Manager and vCenter Server

Figure 3. Workflow with PowerStore T model clusters

12 Overview

Figure 4. Workflow with PowerStore X model clusters

Overview 13

Getting started

Hypervisor configuration for PowerStore X modelappliances

vSphere Distributed SwitchYou cannot use an existing vSphere Distributed Switch (vDS) configuration with your PowerStore X model appliance. PowerStore createsits own vDS and does not use the existing vDS configuration.

VMware licensing

vSphere license requirementsPowerStore X model appliances require a vSphere Enterprise Plus license or higher, and include an embedded instance of VMwarevSphere 6.7. You can apply a license from an existing VMware ELA or purchase vSphere licenses from VMware, Dell, or a partner.

vCenter Server requirementsPowerStore X model appliances support vCenter Server version 6.7 or later. To include more than four hosts in your vCenter Serverenvironment, use a vCenter Server Standard edition license. If your PowerStore X model deployment is limited to one of the following hostconfigurations, you can use a vCenter Server Foundation edition license:

• Two single-appliance PowerStore X model clusters• One single-appliance PowerStore X model cluster and two external ESXi hosts

Table 1. vCenter Server license options

vCenter Server License Number of hosts vSphere licensed managed

Standard Unlimited • vSphere Standard• vSphere Enterprise Plus• vSphere Platinum• vCloud Suite

Foundation Up to 4

NOTE: You can purchase vCenter Server licenses independently or through your service provider.

Providing your own ESXi licenseThe simplest way to license VMware ESXi for your PowerStore X model appliance is to purchase the license with the cluster. Licensespurchased this way do not require other steps for activation.

If you choose to bring your own license, you must apply your license key before the ESXi evaluation period ends. A 180-day trial license isconfigured when a PowerStore X model appliance is manufactured. Failure to apply the license in time requires a call to support forresolution. Resolution of the issue requires appliance reinitialization and loss of all configuration and user data. To avoid this outcome, applyyour VMware license within 180 days of the manufacture date of your cluster.

3

14 Getting started

vCenter and vSphere configuration changesDuring PowerStore X model appliance initialization, a vSphere cluster is created with specific configuration settings in vCenter. Some ofthese settings are listed below and should not be changed.

NOTE: Before changing any settings in vCenter or vSphere, review the following configuration details.

Enhanced vMotion Compatibility (EVC)

Default vSphere value Disabled

RecommendedPowerStore value

Disabled

Notes All VMs including the PowerStore controller VM must be shut down to change this value.

Distributed Resource Scheduler (DRS) policy

Default vSphere value --


Partially Automated

Notes If a user selects a different setting, PowerStore reverts it to Partially Automated.

vSphere high availability (HA)



Enabled

Notes If a user disables HA, user VMs are not protected from ESXi host failures.

vSphere HA Admission Control



Disabled

Notes vSphere does not differentiate between PowerStore software VMs and user-created VMs. If HAAdmission Control is enabled, vSphere reserves resources for the PowerStore software VMs and userVMs cannot be failed over.

Enabling HA Admission Control might prevent controller VMs from powering on.

vSphere HA option nas.ignoreInsufficientHbDatastore

Default vSphere value False


True

Notes The default value for this setting causes vSphere to display a warning when there are fewer than twodatastores in the cluster. This warning is unnecessary and misleading because the default PowerStore Xmodel configuration has single vVol datastore. If this setting is changed, vSphere displays the warningmessage: The number of heartbeat datastores for host is 1, which is lessthan required: 2

Getting started 15

Protocol Endpoint (PE) path policy

Default vSphere values Path Selection Policy = Most Recently Used

iops = 1000

No of outstanding IOs with competing worlds = 32

RecommendedPowerStore values

Path Selection Policy = Round Robin

iops = 1

No of outstanding IOs with competing worlds = 128

Notes The Round Robin policy allows the optimized use of multiple paths. The other parameter settings arerecommendations for better performance and are based on testing. Changing these values can cause I/Operformance degradation.

LLDP for virtual switches (vSS or vDS)



Disabled

Notes To prevent networking problems, do not change this setting.

Performance best practices for PowerStore X model appliancesWhen a PowerStore X model appliance is deployed, additional configuration changes are recommended to provide optimal performance.These changes include:

• Creating additional internal iSCSI targets• Increasing internal iSCSI queue depths• Enabling Jumbo frames

NOTE: The configuration changes must be made immediately after deploying the PowerStore X model appliance and

before provisioning any resources. For detailed configuration steps, see KB article HOW17288 PowerStore X -Performance Best Practice Tuning or see the PowerStore Virtualization Integration White Paper.

ESXi passwordsThe default root password for ESXi on a PowerStore X model appliance is in the following format: <Service_Tag>_123!, where<Service_Tag> is the seven-character Dell Service Tag for the appliance.

Do not change the default ESXi password until the initial cluster configuration is complete. For more information about changing an ESXipassword, see the VMware ESXi documentation.

CAUTION: It is critical that you do not lose the ESXi password. If ESXi goes down and you do not have the password, the

appliance must be reinitialized. This behavior is normal for ESXi, however reinitializing due to a lost password can result

in data loss.

CAUTION: The default ESXi password is uniquely configured for each PowerStore X model appliance. The password is

used to authenticate with the ESXi host when the nodes in the appliance are added to a vCenter cluster. If you change

the default password before the cluster is fully configured, you will have to reinitialize the appliance.

16 Getting started

Configure a vCenter Server connection to a PowerStore Tmodel clusterPowerStore T model clusters can host traditional (VMFS) datastores without being registered as a VASA provider or connecting to avCenter Server. Registering a VASA provider is required to use vVols. Connecting to a vCenter Server enables additional managementoptions in the PowerStore Manager.

Prerequisites

Acquire the IP address, username, and password for the vCenter Server.

NOTE: A PowerStore T model cluster cannot be connected to more than one vCenter Server.

Steps

1. Perform the following steps to register the PowerStore T model cluster as a VASA provider on the vCenter Server:

a. In PowerStore Manager, create a user that is named vmadmin and select VM Administrator as the user role.

For more information about user accounts and roles, see Manage Users on page 17.

b. Log in to the vCenter Server using the vSphere Web Client.c. Open the dialog to add a storage provider.

• The Name can be any name that you choose.• The URL must be in the format: https://<IP address>:8443/version.xml, where <IP address> is the management

IP address of the PowerStore T model cluster.• The User name is the PowerStore Manager user with the VM Administrator role, in the appropriate format:

○ For local users: local/<user name>○ For LDAP users: <domain>/<user name>

• The Password is the password of the PowerStore Manager user with the VM Administrator role.

d. Do not select Use storage provider certificate.e. Click OK.f. Verify the details that you entered in vCenter Server.

vCenter might report the Activation status as Automatic for manual registrations, but there is no impact to functionality.

2. Perform the following steps to configure a connection to the vCenter Server:

a. In PowerStore Manager, under Computer, select vCenter Server Connection.b. Click Connect.c. Type the vCenter Server IP address, username, and password, then click Connect.

If the connection to the vCenter Server: is successful, the status of the connection updates and new options become available.

Next steps

• To open vSphere Web Client in a new tab, click Launch vSphere.• To update the stored IP address or credentials for the vCenter Server, click Update Connection.

NOTE: You cannot change the vCenter Server that your cluster is connected to by updating the IP address. To

change the vCenter Server that your cluster is connected to, see Change a vCenter Server connection on page 22.

• To disconnect from the vCenter Server, click Disconnect.

NOTE: You can no longer use your PowerStore T model cluster to manage VMs.

After disconnecting the vCenter Server, you can unregister the VASA provider if you no longer want to use vVols for VM storage.

Manage Users

About this task

Steps

1. Click Settings, and then select PowerSore Users under Users.2. Do any of the following:

Getting started 17

• Add a user. When you add a user, you select the user's role.• View or change a user's role.• Delete a user.

NOTE: The built-in Administrator account cannot be deleted.

• Change a user's password.• Lock or unlock a user.

NOTE: Logged-in users with either an Administrator or Security Administrator role cannot lock their own

account.

Using an external ESXi host with a PowerStoreclusterIf you have another ESXi host that is connected to a vCenter Server in your environment, you can grant the host access to yourPowerStore cluster.

Additional ESXi host configuration guidelinesFor information about configuring another ESXi host on a PowerStore cluster, see the PowerStore Host Configuration Guide.

vCenter Server requirementsThe vCenter Server requirements for adding another ESXi host to a PowerStore cluster are the same as the vCenter Server requirementsfor PowerStore X model appliance deployment. For more information, see VMware licensing on page 14.

Recommended vCenter Server settingsUse the appropriate size vCenter Server Appliance to hold the expected number of objects. The options are Tiny, Small, Medium, Large,and X-Large. For information about the resources that are required and number of objects that are supported at each size level, see theVMware vCenter documentation.

Network configuration for PowerStore X modelappliancesPlan your network configuration before setting up your PowerStore X model appliance.

The PowerStore X model appliance has some specific requirements and considerations that do not apply to PowerStore T model clusters.For detailed information about network configuration with PowerStore X model appliances, see the PowerStore Network Planning Guide.The document includes:

• Planning and preparation information• Configuration recommendations and best practices• Network configuration, VLAN, and IP address requirements• Switch configuration and cabling procedures• Network configuration validation instructions

NOTE: If the configuration is modified, there are some consequences and limitations that impact HA.

User VM NetworkingBefore deploying user VMs on the internal ESXi hosts, create a distributed port group in vCenter Server for your external network. Whenyou deploy user VMs, use that port group for external network connectivity.

18 Getting started

NTP server requirementsTo prevent issues with lag time between vCenter Server and ESXi hosts when creating your cluster, ensure that they are using the sameNTP server.

Getting started 19

Virtualization configuration in PowerStoreappliances

Managing virtualization components in thePowerStore ManagerYou can monitor and manage basic properties of VMs, vVols, and storage containers from the PowerStore Manager. Advancedmanagement capabilities are available with the vSphere Web Client.

Monitoring and managing VMsThe Compute > Virtual Machines page in the PowerStore Manager displays essential information about all connected vVol-based VMsin a centralized location.

The main view shows essential details for each VM. The table can be filtered, sorted, refreshed to show changes, and exported to aspreadsheet. VMs that are provisioned on a connected ESXi host are added to the table automatically. You can select one or more VMs toadd or remove them from the dashboard watchlist or assign or remove a protection policy.

To view more details for a VM, click its name. You can monitor and manage the VM properties available on the following cards:

• Capacity

This card displays interactive line charts with storage usage history for the VM. You can view data for the past two years, month, or24 hours and print or download the chart data as an image or CSV file.

• Compute Performance

This card displays interactive line charts with CPU usage, memory usage, and system uptime history for the VM. You can view data forthe past year, week, 24 hours, or hour and download the chart data as an image or CSV file.

• Storage Performance

This card displays interactive line charts with latency, IOPS, bandwidth, and I/O operation size history for the VM. You can view datafor the two years, month, 24 hours, or hour and download the chart data as an image or CSV file.

• Alerts

This card displays alerts for the VM. The table can be filtered, sorted, refreshed to show changes, and exported to a spreadsheet. Toview more details, click the description of the alert you are interested in.

• Protection

This card displays snapshots for the VM. The table can be filtered, sorted, refreshed to show changes, and exported to a spreadsheet.To view more details, click the name of the snapshot you are interested in. You can also assign or remove a protection policy for theVM from this card.

VM snapshots, whether manual or scheduled, create VMware–managed snapshots. You can take snapshots from PowerStoreManager or vSphere. Whether the snapshots are taken from PowerStore Manager or vSphere, snapshots of vVols based VMs areoffloaded to the native snapshot engine on the PowerStore cluster. For more information, see VMware snapshot limitations on page30.

• vVols

This card displays the vVols connected to the VM. The table can be filtered, sorted, refreshed to show changes, and exported to aspreadsheet. To view more details, click the name of the vVol you are interested in.

4

20 Virtualization configuration in PowerStore appliances

Monitoring and managing vVolsYou can use PowerStore Manager to view essential information about vVols through the storage container or VM to which they areconnected.

• From the Storage > Storage Containers page, click the storage container name. On the details page for the storage container, clickVirtual Volumes.

• If the PowerStore cluster is connected to a vCenter server, you can view vVols in the context of their VMs. From the Compute >Virtual Machines page, click the VM name. On the details page for the VM, click Virtual Volumes.

The main view shows the name of each vVol, what type of vVol it is, the VM it is associated with, the amount of logical used space, theamount of space that is provisioned, when it was created, and its I/O priority. The table can be filtered, sorted, refreshed to showchanges, and exported to a spreadsheet. You can select a single vVol for migration to another appliance. You can select multiple vVols tocollect support materials or add or remove them from the dashboard watchlist.

To view more details for a vVol, click its name. You can monitor and manage the vVol properties available on the following cards:

• Capacity

This card displays current and historical usage details for the vVol. You can view data for the past two years, one month, or 24 hours,print the chart, and download the chart data as an image or CSV file.

• Performance

This card displays interactive line charts with latency, IOPS, bandwidth, and I/O operation size history for the vVol. You can view datafor the past two years, one month, 24 hours, or one hour and download the chart data as an image or CSV file.

To view an overview of the properties of the vVol, click the pencil icon next to its name.

Monitoring and managing storage containersThe Storage > Storage Containers page in the PowerStore Manager displays essential information about all storage containers in acentralized location.

The main view shows the name of each storage container, any current alerts, and capacity details. The table can be filtered, sorted,refreshed to show changes, and exported to a spreadsheet. You can perform the following actions on a storage container:

• Create a storage container on page 21.• Change the name of a storage container. If the PowerStore cluster is connected to a vCenter server, the name of the storage

container is updated in the vSphere Web Client to match the name in the PowerStore Manager.• Limit space usage by a storage container on page 22.• Delete a storage container.

NOTE: You cannot delete a storage container when there are VMs on the associated storage containers in vCenter.

• Monitor current and historical space usage.

To view current and historical usage details for a storage container, click its name. You can view data for the past two years, one month,or 24 hours, print the chart, and download the chart data as an image or CSV file. The PowerStore Manager raises an alert when usage ofa storage container reaches or exceeds 85% of its available space.

Create a storage container

About this task

Use PowerStore Manager to create storage container on a PowerStore cluster.

Steps

1. Under Storage, select Storage Containers.2. Click Create.3. Enter a name for the storage container.4. Optionally, select the Customize default polices configuration checkbox to specify a capacity quota for the storage container.5. Click Create.

Results

For PowerStore X model appliances, a datastore is automatically created with the same name as the storage container. For PowerStore Tmodel clusters, the user must create a datastore from the storage container in vCenter.

Virtualization configuration in PowerStore appliances 21

Limit space usage by a storage container

About this task

To limit the amount of space a storage container consumes, set a quota on that storage container. The quota represents the totalmaximum size of the data that can be written to the vVols in the storage container. Space that snapshots and thin clones consume doesnot count towards the quota.

Steps

1. Under Storage, select Storage Containers.2. Select the storage container for which you want to set a quota and click Modify.3. Check the box to enable a quota and specify the limit that you want, then click Apply.

Results

When the space that the storage container is using reaches or exceeds the high watermark for the quota, the system generates anotification. If the space used falls below the high watermark for the quota, the notification clears automatically. By default, the highwatermark for the quota is 85%, but you can change this value.

To remove the quota on a storage container, clear the checkbox on the Properties panel for that storage container.

Change a vCenter Server connectionTo change the vCenter Server that your PowerStore T model cluster is connected to, you must first remove the existing connection.

Prerequisites

Ensure that you have the IP address, username, and password for the vCenter Server.

Steps

1. Under Compute, select vCenter Server Connection.2. Click Disconnect.

NOTE: You can no longer use your PowerStore T model cluster to manage VMs.

3. Use vCenter Server to unregister the VASA provider.

NOTE: Unregistering the VASA provider causes the vVol datastore to appear as disconnected, but any VMs that are

already running are not impacted. New write operations such as powering up VMs are blocked when there is no

active VASA connection.

4. Register the VASA provider for the new vCenter Server connection.5. On the vCenter Server Connection screen of the PowerStore Manager, click Connect.6. Type the new vCenter Server IP address, username, and password, then click Connect.

Additional VMware software and configuration

VMware integrationYou can use many VMware products with PowerStore the same way you would in your existing VMware environment. The followingproducts are supported in this release:

• VMware vRealize Orchestrator (vRO)• Dell EMC Virtual Storage Integrator (VSI) for VMware vSphere Client• VMware Storage Replication Adapters (SRA)• VMware NSX-V

For more information, see VMware documentation about working with Dell and Dell EMC plugins.


Virtual network configurationNetworking on a PowerStore X model appliance is controlled by ESXi, which uses a virtual switch to share network devices with thecontroller VM. As a part of cluster creation, a vSphere Distributed Switch (vDS) is set up to manage network traffic. The vDS enablesfeatures such as advanced QoS priority configuration with Network I/O Control (NIOC).

In general, this configuration does not impact the management of a PowerStore X model appliance. However, there are someconsiderations for HA if the default configuration is modified.

NOTE: Do not upgrade a vDS even if there are upgrade notifications or options available in vCenter Server.

Upgrading PowerStore X model appliancesWhen upgrading a PowerStore X model appliance, apply the available upgrades to the PowerStore node firmware, ESXi image, vSphereInstallation Bundles (VIBs), and PowerStore OS that are qualified together by Dell EMC.

CAUTION: PowerStore X model internal nodes can only use ESXi update images that are validated by Dell EMC and

available on the support website. Do not use ESXi update images that are obtained from VMware or any other source.

The PowerStore X model upgrade may consist of multiple packages, with some packages installed from PowerStore Manager, and othersinstalled from the vSphere Update Manager. A given PowerStore release may not contain all possible components. Use the information inthe PowerStore Release Notes to determine which bundles are required for a given release.

The PowerStore X model upgrade can accommodate both system and user VMs, and externally attached ESXi hosts. However, theupgrade requires placing the PowerStore X model internal ESXi hosts into maintenance mode. During the upgrade, the ESXi host on thepeer node is placed into maintenance mode first and the ESXi host on the primary node is placed into maintenance mode second.

During a PowerStore X model upgrade, you cannot use the vCenter Server to manage vVol-based VMs on the PowerStore appliance.Management operations such as rebooting VMs, migrating VMs to other ESXi hosts, and taking VM snapshots cannot be performedduring the upgrade. When the PowerStore VASA Provider is offline during the upgrade, the datastores and VMs on the PowerStoreappliance become inaccessible in vCenter Server, but the I/O between the VMs and the PowerStore appliance continues.

NOTE: After the upgrade is complete, wait five to ten minutes for the status of the VASA Provider to change to Online

before creating storage containers or performing management operations on vVol-based VMs.

The upgrade process has up to three parts, which must be completed in sequence, as applicable:

1. Upgrading PowerStore X model node firmware on page 242. Updating the internal ESXi hosts on page 253. Upgrading the PowerStore OS on page 26

You can find which components have an upgrade available in the PowerStore Release Notes. If a component does not have an upgradeavailable, you can skip that part of the upgrade.

NOTE: If a PowerStore X model upgrade fails, check for and resolve all critical alerts on the PowerStore system and

retry the upgrade.

Upgrade readiness for PowerStore X model appliancesBefore upgrading, review the following considerations:

• You can learn that an upgrade is available in one of the following ways:

○ If you are using SupportAssist with your PowerStore appliance, PowerStore Manager notifies you when an upgrade is available.○ If you are not using SupportAssist, or do not have SupportAssist connected to your PowerStore appliance, go to www.dell.com/

support and check for an upgrade.• A few days before upgrading, upload the PowerStore OS image file that you want to install and perform a system health check on it.

The health check ensures that there are no underlying problems that may prevent a successful upgrade, such as:

○ A faulted hardware component○ An incompatible vCenter software version

• There can be up to ten upgrade candidates of different types on the system at a time. However, after an upgrade starts, it mustsuccessfully complete across all appliances in the cluster before another upgrade can be performed.

• You cannot make configuration changes to the system while the upgrade is in progress.• Applying an upgrade does not stop I/O. The nondisruptive upgrade process uses redundant paths, ensuring that no more than one

node is taken offline at any given time. Either node in your appliance can satisfy I/O requirements.




ESXi and VM considerationsBefore upgrading, run a health check to determine whether there is a prerequisite PowerStore node firmware or ESXi update. Dependingon which components are upgraded, the duration of the required maintenance window and whether an upgrade requires any downtimevaries. For details and time estimates, see the PowerStore Release Notes.

In general, vSphere automatically migrates VMs that are running on a PowerStore X model appliance as necessary to keep them availableduring the upgrade. However, manual intervention may be required if one of the following conditions exists:

• The VMs running on ESXi hosts or VM disks point to the local ESXi host drives• The total amount of memory or CPU usage across the VMs exceeds the amount available on a single node• The VMs cannot be migrated automatically because of a different reason

If any of these conditions occur, resolve the situation with one of the following options:

• Migrate the VMs to other available hosts• Reduce the CPU or memory reservation requirements for the VMs• Shut down the VMs

NOTE: Any VMs that are migrated as a part of the upgrade process are not automatically migrated back to their original

location after the upgrade is complete.

Minimizing failover occurrencesIf the upgrade includes new versions of the PowerStore node firmware or ESXi, each ESXi host in the appliance must be placed intoMaintenance Mode during the upgrade process.

When the ESXi host that is running PowerStore OS enters Maintenance Mode, the user VMs migrate to the ESXI host on the other nodeof the appliance. The appliance is temporarily unable to display PowerStore Manager or act as a VASA provider until the failover processbetween nodes is complete.

To minimize disruptions caused by failover, start the upgrade on the ESXi host on the peer node of the appliance.

Use PowerStore Manager to identify the peer node of the appliance:

1. From the Hardware page, click the name of the appliance, and then click the Hardware tab.2. Click the Internal View tab.

The node without the text (primary) is the peer node.3. Record the node letter of peer node, which is either A or B.4. In PowerStore Manager, from the Compute > vCenter Server Connection page, start the vSphere Web Client by clicking

LAUNCH VSPHERE.5. Log in to the associated vCenter Server.6. Find the VM named PSTX-<serial_number>-<node_letter>.

Where node_letter is the node letter of the peer node that was recorded in step 3.7. On the Summary tab of the VM, record the Host IP address.

This address is the IP address of the ESXi host on the peer node of the appliance.8. During the upgrade, place this ESXi host into Maintenance Mode first.

Upgrading PowerStore X model node firmwareUse PowerStore Manager to perform node firmware upgrades.

Prerequisites

1. If there is a PowerStore OS upgrade that does not include a new version of the PowerStore X model node firmware, go to Updatingthe internal ESXi hosts on page 25.

2. Download the latest node firmware and PowerStore OS upgrade package from www.dell.com/support to your managementworkstation.

3. Open PowerStore Manager.

Steps

1. Select the Settings icon, and then select Upgrades in the Cluster section.2. Click Upload Package.



The Choose File to Upload dialog box is displayed.

3. Select the PowerStore OS upgrade package, and click Open.When the upgrade package is uploaded, it is displayed in the Software packages table.

4. Select the uploaded PowerStore OS upgrade package in the Software packages table, and click Health Check.

The health check indicates whether a node firmware upgrade is required.

5. If a node firmware upgrade is required, select the PowerStore OS upgrade package in the Software packages table, and clickUpgrade.

If a node firmware upgrade is not required, stop the upgrade and go to Updating the internal ESXi hosts on page 25.

6. Wait for the firmware upgrade to complete on both nodes of the appliance.

To determine if the firmware upgrade is complete, select the uploaded PowerStore OS upgrade package in the Software packagestable and click Health Check.

• If the upgrade is complete, the health check passes.• If the upgrade is not complete, the health check indicates that a node firmware upgrade is required.

Next steps

If an ESXi update is available on the support website, go to Updating the internal ESXi hosts on page 25.

If an ESXi update is not available on the support website, go to Upgrading the PowerStore OS on page 26.

Updating the internal ESXi hostsUse the vSphere Web Client to perform ESXi host updates. This procedure must be completed on each node.

Prerequisites

If the PowerStore Release Notes do not indicate that a new version of ESXi is available, go to Upgrading the PowerStore OS on page 26.

1. If an upgrade to the node firmware is also available, complete Upgrading PowerStore X model node firmware on page 24 first.2. Download the latest qualified version of ESXi from www.dell.com/support to your management workstation.

CAUTION: PowerStore X model internal nodes can only use ESXi update images that are validated by Dell EMC and

available on the Dell EMC support website. Do not use ESXi update images that are obtained from VMware or any

other source.

3. Open PowerStore Manager and identify the peer and primary nodes on your appliance. See Minimizing failover occurrences on page24 for more information.

4. In PowerStore Manager, from the Compute > vCenter Server Connection page, start the vSphere Web Client by clickingLAUNCH VSPHERE.

About this task

Some management operations that involve vVols may be unavailable during the upgrade.

Steps

1. In the vSphere Web Client, log in to the associated vCenter Server and open the Update Manager Web Client plug-in.2. Upload the VMware Installation Bundle (VIB) files (.zip) or import the ESXi images (.iso) for the release.

3. Create a baseline for the update using the Patch content type.

a. On the Select Patches Automatically page, clear the Automatically update this baseline with patches that match thefollowing criteria checkbox to prevent unqualified VIBs from being installed on the ESXi hosts.

b. On the Select Patches Manually page, select the PowerStore VIBs to include in the baseline.4. Attach the new baseline to the ESXi hosts cluster.5. To reduce the amount of time needed in Maintenance Mode, stage the baseline on both ESXi hosts in the cluster.

NOTE: Before placing the ESXi host on one node of the appliance into Maintenance Mode, ensure that system

resources are available on the other ESXI host to run the migrated user VMs. If the CPU and memory utilization on

each ESXi host is greater than 75%, power off some user VMs or migrate them to another ESXi host using vMotion

before placing ESXi host into Maintenance Mode.

6. Place the ESXi host on the peer node into Maintenance Mode.



User VMs automatically migrate to the other node in the cluster. After all user VMs are migrated, the controller VM automaticallyshuts down and the ESXi host enters Maintenance Mode.

NOTE: Some user VMs may not migrate due to local dependency or lack of resources. User intervention may be

required to manually power off these user VMs to allow the ESXi host to enter Maintenance Mode. See ESXi and VM

considerations on page 24 for more information.

CAUTION: Do not manually power off the controller VMs, which are named PSTX-<serial_number>-<node_letter>.

7. Remediate the ESXi host against the baseline. For more information, see VMware vSphere documentation.8. When the ESXi host on the peer node is back online, exit Maintenance Mode.

The ESXi host on the peer node is powered on and running with the ESXi host updates.

NOTE: The controller VM starts automatically when the ESXi host exits Maintenance Mode.

9. In PowerStore Manager, perform a health check to verify that the peer node is working correctly, and that the primary node is readyfor the update.

10. Repeat steps 6–9 in this procedure for the ESXi host on the primary node.11. Migrate the VMs that were on the peer node before the update back to the peer node using vMotion.

Results

The ESXi hosts on both nodes are now powered on and running with the ESXi host updates.

Next steps

Go to Upgrading the PowerStore OS on page 26.

Upgrading the PowerStore OSIf the support website indicates that a new version of the PowerStore OS is available, use PowerStore Manager to install it.

Prerequisites

• Download the latest version of the PowerStore OS from www.dell.com/support to your management workstation.• If an upgrade to the node firmware is also available, complete Upgrading PowerStore X model node firmware on page 24.• If an ESXi update is also available, complete Updating the internal ESXi hosts on page 25.• Open PowerStore Manager.

Steps

1. Perform the following steps if you have completed a PowerStore X model node firmware upgrade without performing internal ESXihosts updates:

a. Identify the peer and primary nodes on your appliance. See Minimizing failover occurrences on page 24 for more information.b. In the vSphere Web Client, reboot the ESXi host for the peer node. For instructions, see the PowerStore Power Down and Reboot

Procedures Guide.c. In PowerStore Manager, select the uploaded PowerStore OS package in the Software packages table and click Health Check.

• If the only error displayed is regarding an incorrect firmware version, go to the next step.• If an error regarding RAID readiness is displayed, wait and try the health check again until the only error displayed is regarding

an incorrect firmware version.

d. If the ESXi host on the peer node does not automatically exit Maintenance Mode after rebooting, manually exit MaintenanceMode.

e. Repeat the previous steps for the ESXi host on the primary node.2. Perform the following steps if the PowerStore OS upgrade package has not been uploaded to the PowerStore X model appliance:

a. In PowerStore Manager, select the Settings icon, and then select Upgrades in the Cluster section.b. Click Upload Package.c. Select the PowerStore OS upgrade package and click Open.

When the upgrade package is uploaded, it is displayed in the Software packages table.d. Select the uploaded PowerStore OS upgrade package in the Software packages table, and click Health Check.



The health check identifies problems that may prevent the PowerStore OS upgrade from finishing successfully. This step isoptional if a health check was performed earlier.

3. Select the uploaded PowerStore OS upgrade package in the Software packages table, and click Upgrade.

Results

As a part of the upgrade process, the node that displays PowerStore Manager fails over to the other node. During failover, you aredisconnected from the user interface. You can log back in to PowerStore Manager after the failover process is complete.

Next steps

In the vSphere Web Client, rebalance the VMs between the two nodes. You can rebalance the VMs manually or allow VMware DistributedResource Scheduler (DRS) to rebalance them automatically.

When a new software version is installed, the column layout settings in PowerStore Manager tables may be reset to their default layout.You can change the configuration to a layout of your preference, and your settings persist until the next software upgrade.


VMware NSX-V

VMware NSX-V introductionPowerStore X model appliances include support for VMware NSX Data Center for vSphere (NSX-V). NSX-V is a network virtualizationand security platform that enables the implementation of virtual networks on a physical network.

NSX-V provides the network architecture with features such as rapid provisioning, deployment, reconfiguration, and destruction of on-demand virtual networks. This design uses the vSphere distributed switch (vDS) and VMware NSX-V to implement virtual networking.

NOTE: PowerStore X model appliances support NSX-V version 6.4.6 or later.

CAUTION: The NSX controller VMs cannot be deployed on PowerStore X model nodes because the NSX Controller

cluster requires three nodes. Per VMware NSX-V requirements for resiliency and performance, the NSX controller VMs

must be deployed on three distinct hosts.

Add internal ESXi hosts to an existing NSX-VdeploymentPerform the following steps to add the internal ESXi hosts of a PowerStore X model appliance to an existing deployment of NSX-V:

Steps

1. Prepare the internal ESXi hosts.

Use the NSX Manager to prepare each host by installing the NSX-V VIBs.CAUTION: If the NSX-V controller cluster is using Guest Introspection services, do not deploy Guest Introspection

services on the vSphere cluster using PowerStore vVol datastores. Deploying the Guest Introspection services using

PowerStore vVol datastores will result is appliance boot issues after a power failure. Instead, deploy the Guest

Introspection services on a vSphere cluster using PowerStore X private datastores, which are named PRIVATE-

<serial-number>.<node_letter>.INTERNAL.

2. Exclude virtual machines from firewall protection.

Add the PowerStore X model controller VMs to the firewall exclusion list during NSX-V configuration to avoid potential issues with theNSX-V DFW firewall rules.

For more information about using NSX-V, see the VMware NSX documentation.

5

28 VMware NSX-V

Best practices and limitations

Internal components visible in vCenter ServerSome system components are visible as manageable objects in the vSphere Web Client, but modifying them can cause data loss orunavailability.

Critical system componentsCAUTION: 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 VMsThe PowerStore X model controller VM is displayed in the vSphere Web Client as an object that can be managed, but some operationsshould 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 mustremain in the default resource pool on the cluster.

Do not power off the PowerStore X model controller VM.

Internal datastoresFor each node in the cluster, the vSphere Web Client displays and enables modification of the internal datastore that the PowerStore Xmodel controller VM uses. Do not create VMs on internal datastore, or otherwise modify it. The internal datastores are named as follows:

• PRIVATE-<serial-number>.A.INTERNAL• PRIVATE-<serial-number>.B.INTERNAL

Groups and rulesvCenter Server supports the creation of VM groups, host groups, and host rules to manage affinity between VMs and hosts in a cluster.

• 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 LUNsVMs running on internal PowerStore X model nodes can only use vVol based storage. VMFS-based storage is not supported for VMsrunning 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 canbe formatted as VMFS datastores and be presented to external servers and VMs running outside of the internal PowerStore X modelnodes.

6

Best practices and limitations 29

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 recoveryThe PowerStore virtualization configuration affects some of the troubleshooting processes that an experienced virtualization administratormay 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 VSSPowerStore clusters support third-party snapshot integration for Microsoft Volume Shadow Copy Service (VSS) to simplify protection ofMicrosoft applications such as SQL Server and Outlook.

vSphere limitationsPowerStore X model appliances inherit some limitations that are inherent to vSphere.

Number of supported objectsvSphere 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 usagePowerStore X model controller VMs always report high CPU and memory usage in vSphere. The high CPU and memory usage is normalbecause 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.

VMware snapshot limitationsvSphere allows a maximum snapshot tree depth of 31 for a VM. Scheduled and manual snapshots interact with this limit in different ways.

Scheduled snapshotsWhen you create a VM snapshot schedule as a part of a protection policy, you can set a retention policy specifying how long to keepsnapshots. Snapshots older than the age that the retention policy specifies are deleted. This policy helps keep the total number ofsnapshots below the limit.

If the maximum number of snapshots is reached, the oldest snapshot is automatically deleted when the protection policy creates the nextsnapshot. Although manual snapshots count towards this limit, they are never deleted automatically unless the expiration date is reached.

Manual snapshotsManual snapshots that are created with PowerStore Manager or vSphere cannot have a retention policy and are never deleted withoutuser action. If the maximum number of snapshots is reached, no more can be created unless you delete snapshots to make room.

Other limitationsThe following limitations apply to this release of PowerStore:

• PowerStore X model supports only single appliance clusters.• PowerStore clusters support up to 245 storage containers.

30 Best practices and limitations

Dell EMC PowerStore Virtualization Guide · PowerStore virtualization terminology and definitions...

Documents

Transcript of Dell EMC PowerStore Virtualization Guide · PowerStore virtualization terminology and definitions...