Dell PowerStore 5200T EMC PowerStore Release Notes for PowerStore OS Version 3 - Page 26

Issue ID MDT-156905 MDT-135505 MDT-433312 MDT-425715 MDT-359565 MDT-285903 MDT-239624 Functional Area Description Install or Upgrade Install or Upgrade Internal Migration Internal Migration Internal Migration Internal Migration Internal Migration After a Non-Disruptive Upgrade (NDU), the NAS servers may not fail back automatically to the original node. Drive firmware updates may not get applied to a single drive or a few drives within the appliance. This may occur because of a timing issue between the two nodes in the appliance. When a virtual volume is migrated to another appliance in PowerStore version 3.0.0.x release, metrics history prior to the migration may be lost. Starting concurrent migrations of a virtual machine (VM) and its member virtual volumes (vVols) at the same time may result in paused migration sessions that cannot be cleaned up. PowerStore Manager does not prevent a user from using the Delete button during a migration cutover, however, deletion during cutover is not supported and the migration session is not deleted. The delete operation will result in a backend error. The migration failed due to a High Availability (HA) event and a system snapshot remains on the migration source object. 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 space-efficient 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, spaceefficient 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. Workaround/Resolution Manually fail back the NAS servers from PowerStore Manager. Download and install the drive firmware again to ensure it gets updated on the drives that were missed in the previous attempt. Check the metrics history for the virtual volume prior to migration from the original appliance. Allow the VM migration to complete before migrating any of its member vVols. Contact your service provider for assistance if issue occurs. None Contact your service provider to clean up the remaining snapshot. 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. 26 Known Issues