Dell PowerStore 1200T EMC PowerStore Release Notes for PowerStore OS Version 3 - Page 9

Issue ID MDT-239624 Functional Area Internal Migration MDT-401600 Install or Upgrade MDT-415463 Install or Upgrade MDT-417339 Install or Upgrade Description Workaround/Resolution When a VM is being deployed from a VM template, vSphere uses the clone operation to provision vVols of the newly created VM. PowerStore internally translates it into spaceefficient clones (the same technique used for vVol snapshots). As soon as a Data Path (DP) family size limit exists, a base vVol cannot have more than a certain number (1000) of derivatives (snapshots, space-efficient clones). This causes the following limitations: - Cloning from a VM template fails if a base vVol of the VM template has too many derivatives (snapshots or clones, or both) already created (1000). - When the maximum number of family members limit is reached, vVol migration cannot occur as it needs to create an internal vVol snapshot which fails. - All vVols are placed to the same appliance in a multi-appliance cluster, so the load is not balanced between appliances. If the healthcheck package was uploaded on the PowerStore cluster before a new appliance was added to the cluster, healthcheck package is unable to run for the newly added appliance. After a failed non-disruptive upgrade (NDU) and rollback, the REST command will not work in 5 minutes due to the management software module failback. If retry the NDU in 5 minutes, the HealthCheck will report some alert incorrectly due to the failed REST command. Pre-upgrade health checks (PUHC) sometimes failed with "failed_to_get_free_size" error on A PUCH on a PowerStore 500T can fail with the error "failed_to_get_free_size" even when there is no underlying issue with space on the system Use several VM templates created from the same OVF template so that each VM template is used for a reasonable number of VM clones to avoid hitting the DP family limit. This action allows vVols to be distributed between appliances in a multiappliance cluster for load balancing. Install the same healthcheck package again. After previous failed NDU / rollback, please wait for 10 minutes and then retry NDU. Rerun the Pre-upgrade health checks (PUHC). Known Issues 9