Users Guide

○ Changes to the paths (enable or disable) which can impact the import operation.
○ Host cluster configuration changes.
○ Operating system (OS) upgrades.
Windows-based hosts
The following restrictions apply during a non-disruptive import involving Windows-based hosts:
● The following Windows Dynamic Disk volume types are not supported:
○ Simple volume
○ Spanned volume
○ Mirrored volume
○ Striped volume
○ RAID5 volume
● IDE device and SCSI device under Hyper-V configuration are not supported.
● Modifying the OS disk state after initiating or cancelling an import operation are not supported.
● A LUN having more than 32 paths (sum of source and destination paths) is not supported. This restriction is a Windows
MPIO limitation.
NOTE: After a Windows host plugin install, certain LogScsiPassThroughFailure error messages may occur during
import for Dell EMC VNX2 systems. These messages can be ignored. Also, after the I/O path becomes active toward
PowerStore during an import operation, all I/Os are bound to one port of the network adapter.
Linux-based hosts
The following restrictions apply during a non-disruptive import involving Linux-based hosts:
● Change in user-friendly names of volumes being imported is not supported.
NOTE:
Any device policy or user-friendly name on source volume will not be applied to the destination volume after
import.
● The mpathpersist command fails to get PR information for volumes mapped to clusters after the import. Use
sg_persist.
● LUNs cannot be removed from the storage group.
● UUID-based mount points with EQL MPIO are not supported.
● Only Linear volume LVM is supported, other LVM types, like striped LVM, are not supported.
● The maximum length of the hostname must be within 56 characters.
● After or during the import of a volume and after reboot, the mount command displays the destination mapper name instead
of the source mapper name. The same destination mapper name is listed in the df -h output.
● Before importing a volume, the mount point entry in /etc/fstab should have the "nofail" option
to avoid boot failures on host reboots. For example: /dev/mapper/364842a249255967294824591aa6e1dac /mnt/
364842a249255967294824591aa6e1dac ext3 acl,user_xattr,nofail 0 0
● Import to a PowerStore cluster from a Linux host running Oracle ASM on Dell Compellent SC storage is allowed only when
the Oracle configuration uses logical sector size for ASM disk groups. See Setting the Oracle ASM logical block size on page
48 for more details.
● The keyword blacklist and curly brace should appear in the same line for imports to be successful. For example, "blacklist { "
in the /etc/multipath.conf file.
● If the keyword blacklist and curly brace are not in the same line, import will fail. If not present already, modify the
multipath.conf file manually to the "blacklist {" form.
● If the multipath.conf file has blacklist keyword, such as product_blacklist, before the blacklist section, move that
section after the blacklist section for imports to work successfully.
NOTE:
Ensure that the disk space on the host is not filled to maximum capacity. Free disk space on the host is needed for
import operations.
The following is a known behavior during import on Linux-based hosts:
● After host reboot, during import of the volume, the mount point in /etc/fstab points to the source device mapper.
However, output of the mount or df -h command displays the destination device mapper name.
Import requirements and restrictions
17