Dell Power Store Scalable All Flash Array Storage

Specifications

• Product: Dell PowerStore
• Guide: Importing External Storage to PowerStore
• Version: 3.x
• Date: July 2023 Rev. A08

Product Information

Introduction

This document provides instructions on how to import data from external storage to PowerStore. It includes details on importing block-based external storage and non-disruptive import of external storage to PowerStore.

Supported Versions

For the most up-to-date information on supported versions of host operating systems, multipath software, host protocols, and source systems for seamless import, refer to the PowerStore Simple Support Matrix document available at https://www.dell.com/powerstoredocs.

If your source system’s operating environment version does not match the requirements for seamless import, you can consider using agentless import. The Simple Support Matrix also provides information on supported versions for agentless import.

Product Usage Instructions

Importing Block-Based External Storage to PowerStore Overview

1. Refer to the PowerStore Simple Support Matrix document for the supported versions.
2. If your source system matches the requirements, proceed with seamless import. If not, consider agentless import.

Non-Disruptive Import of External Storage to PowerStore Overview

1. Ensure your source system meets the criteria outlined in the Simple Support Matrix document.
2. Follow the steps for seamless or agentless import based on compatibility.

FAQs

• Q: Where can I find the most up-to-date information on supported versions for importing external storage to PowerStore?
  • A: Refer to the PowerStore Simple Support Matrix document available at https://www.dell.com/powerstoredocs for the latest information on supported versions.
• Q: What should I do if my source system’s operating environment version does not match the requirements for seamless import?
  • A: In such cases, you can consider using agentless import as an alternative method. Check the Simple Support Matrix for details on supported versions for agentless import.

Dell PowerStore
Importing External Storage to PowerStore Guide
Version 3.x
July 2023 Rev. A08

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 – 2023 Dell Inc. or its subsidiaries. All rights reserved. Dell Technologies, Dell, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.

Preface

As part of an improvement effort, revisions of the software and hardware are periodically released. Some functions that are described in this document are not supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information about product features. Contact your service provider if a product does not function properly or does not function as described in this document.
Where to get help
Support, 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 https:// www.dell.com/powerstoredocs. Troubleshooting For information about products, software updates, licensing, and service, go to https://www.dell.com/support and locate the appropriate product support page. Technical support For technical support and service requests, go to https://www.dell.com/support and locate the Service Requests page. To open a service request, you must have a valid support agreement. Contact your Sales Representative for details about obtaining a valid support agreement or to answer any questions about your account.
Third-party content containing non-inclusive language
This manual may contain language from third-party content that is not under Dell Technologies’ control and is not consistent with current guidelines for Dell Technologies’ own content. When such third-party content is updated by the relevant third parties, this manual will be revised accordingly.

6

Additional Resources

Introduction

This document describes how to import data from external storage to PowerStore. This chapter contains the following information:
Topics:
· Importing block-based external storage to PowerStore overview · Importing file-based external storage to PowerStore overview · PowerStore cluster fibre channel connectivity to source systems · Import security
Importing block-based external storage to PowerStore overview
PowerStore provides the abilities of a traditional storage appliance and onboard compute to run embedded workloads. PowerStore enables users to respond quickly to changing business requirements and to scale quickly to meet changing needs without excessive business planning and complexity. Importing block-based external storage to PowerStore is a migration solution that imports block data from any of the following Dell storage platforms to a PowerStore cluster: Dell Peer Storage (PS) Series Dell Storage Center (SC) Series Dell Unity Series Dell VNX2 Series Dell XtremIO X1 and XtremIO X2 (agentless import only) Dell PowerMax and VMAX3 (agentless import only) This import solution can also be used to import block-based data from NetApp AFF A-Series platforms that use ONTAP version 9.6 or later. Import of the following block storage resources is supported: LUNs and Volumes Consistency groups, Volume groups, and Storage groups Thick and thin clones The following options are available to import block-based external storage to a PowerStore cluster: Non-disruptive import Agentless import
Non-disruptive import of external storage to PowerStore overview
The software that runs on the PowerStore cluster and manages the entire import process is known as the Orchestrator. In addition to the Orchestrator, host multipath I/O (MPIO) software and a host plug-in are required to support the import process. The host plug-in is installed on each host that accesses the storage to be imported. The host plug-in enables the Orchestrator to communicate with the host multipath software to perform import operations. The Orchestrator supports Linux, Windows, and VMware host operating systems. The Orchestrator supports the following host MPIO configurations: Linux Native MPIO and Dell PowerStore Import Plugin for Linux Windows Native MPIO and Dell PowerStore Import Plugin for Windows Dell PS Series

Introduction

7

Dell MPIO in Linux – Provided through Dell Host Integration Tools (HIT Kit) for Linux Dell MPIO in Windows – Provided through Dell HIT Kit for Microsoft Dell MPIO in VMware – Provided through Dell MEM Kit NOTE: If you are using native MPIO and the Dell HIT Kit is not installed on the hosts, the PowerStore ImportKit must be installed on the hosts to support import to a PowerStore cluster. If the Dell HIT Kit is already installed on the hosts, ensure that the Dell HIT Kit version matches the version listed in the PowerStore Simple Support Matrix. If the HIT Kit version is earlier than the version that is listed in the Simple Support Matrix, it must be upgraded to the supported version.
For the most up-to-date supported versions of the supported combinations of host operating system, multipath software, host protocol to the source and to the PowerStore cluster, and the type of source system for non-disruptive (seamless) import, see the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs.
If the version of the operating environment running on your source system does not match what is listed for non-disruptive (seamless) import in the PowerStore Simple Support Matrix document, you may be able to use agentless import. The Simple Support Matrix also lists the most up-to-date information for supported versions of source systems and operating environment that are required for agentless import.
NOTE: For PowerStore with operating system versions 3.0 or later, the connection from some source systems to the PowerStore cluster for import can be over either iSCSI or FC. The Simple Support Matrix document for PowerStore lists what protocol is supported for the connection between the source system and PowerStore. When FC connections are used between the source system and PowerStore, only FC connections between the hosts and the source system and the hosts and PowerStore are supported. For PowerStore with operating system versions 2.1.x or earlier, the connection from the source system to the PowerStore cluster for import is only over iSCSI.
NOTE: For the most up-to-date supported versions of software, see the Simple Support Matrix document for PowerStore.
Overview of the non-disruptive import process
Before importing the external storage from a source system to a PowerStore cluster, the active path for the host I/O is to the source system. During the setup of import, the host or hosts build an inactive I/O path to the volumes that are created on the PowerStore cluster which match the specified volumes on the source system. When you start import, the active host I/O path to the source system becomes inactive and the inactive host I/O path to the PowerStore cluster becomes active. However, the source system is kept updated through the I/O forwarding from the PowerStore cluster. When the import reaches the Ready For Cutover state and you initiate cutover, the host I/O path to the source system is removed and the host I/O is directed only to the PowerStore cluster.
Review the following processes to gain an understanding of the import procedure:
NOTE: You can also see the Importing External Storage to PowerStore video at https://www.dell.com/powerstoredocs.
1. Preconfigure ­ Set up the network connectivity. The connection between an existing Dell PS Series or Dell SC Series source system and the PowerStore cluster must be over iSCSI. For Dell PS Series or Dell SC Series source systems ­ All the connections between the hosts and the Dell PS Series or Dell SC Series source system and between the hosts and the PowerStore cluster must be over iSCSI. The connection between an existing Dell Unity Series or Dell VNX2 Series source system and the PowerStore cluster can be over either iSCSI or Fibre Channel (FC). See the PowerStore Simple Support Matrix document at https:// www.dell.com/powerstoredocs to determine which protocol to use. For Dell Unity Series or Dell VNX2 Series source systems ­ The connections between the hosts and the Dell Unity Series or Dell VNX2 Series source system and between the hosts and the PowerStore cluster must be either all over iSCSI or all over Fibre Channel (FC) and match the connection between the source system and the PowerStore cluster. See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs to determine which protocol can be used. Also, all host initiators that are connected to the source system should also be connected to the PowerStore cluster. NOTE: When FC connectivity between the hosts and the source system, the hosts and the PowerStore cluster, and source system and the PowerStore cluster is used, the administrator must set up FC zoning between the hosts, the source system, and the PowerStore cluster.
2. Setup import ­ Install or upgrade the appropriate host plugin as needed on each host that accesses the storage to be imported. Add the source system to the PowerStore cluster, if it is not already listed. Select one or more volumes or consistency groups, or both to be imported. A volume group cannot be combined with any other volumes or volume group.

8

Introduction

Select to add the hosts that access the storage to be imported, the hosts build inactive I/O paths to the destination volumes. Set the import schedule and assign protection policies. 3. Start import ­ A destination volume is created for each selected source volume. A volume group is automatically created for each consistency group that is selected for import. The active I/O and inactive I/O paths from the host are switched to redirect the I/O to the PowerStore cluster. However, the source is kept updated through the I/O forwarding from the PowerStore cluster. 4. Cutover import ­ Cutover can be performed only when the import processing state is Ready For Cutover. In other words, cutover is a final confirmation. You can select to cut over automatically without user intervention. After the cutover step, I/O cannot go back to the source system volume.
In addition, the following processes are available during the import procedure:
Pause import ­ Pause can be performed when the import processing state is Copy In Progress. When an import session is paused, only the background copy is stopped. The forwarding of host I/O to the source system continues to be active. NOTE: The Pause import action on a CG only pauses the member volumes that are in the Copy In Progress state. The CG remains in the In Progress state. Other member volumes that are in other states, such as Queued or In Progress, are not paused and may proceed to the Ready For Cutover state. The other member volumes can be paused when they reach the Copy In Progress state by using the Pause import action again on the CG. If any of the member volumes are in the Paused state but the overall status of the CG is In Progress, both the Pause and Resume import action options are available for the CG.
Resume import ­ Resume can be performed when the import processing state is Paused. Cancel import ­ Cancel can be performed only when the import processing state is Copy In Progress (for volume), In
Progress (for consistency group), Ready For Cutover, Queued, Paused (for volume), or Scheduled, or Cancel Failed (for consistency group). Cancel allows you to cancel the import process with the click of a button and change the active path back to the source.
For Dell PS Series source systems only ­ The source volume is taken offline after a successful cutover operation.
For the Dell SC Series, Dell Unity Series, and Dell VNX2 Series source systems ­ Host access to the source volume is removed after a successful cutover operation.
Agentless import of external storage to PowerStore overview
Unlike non-disruptive import, agentless import of external storage to a PowerStore cluster is independent of the operating system and the multipathing solution on the host, and the front end connectivity between the host and the source system. Agentless import does not require the installation of host plugin software on the host, however, you do need to reconfigure the host application to work with the new PowerStore volumes. Only a one time host application downtime is required prior to the migration. The downtime only includes renaming or reconfiguring the host application, file systems, and datastores to the new PowerStore volumes.
Use the agentless import option to migrate the external storage to a PowerStore cluster when the operating environment running on the source system does not match the respective one listed in the Simple Support Matrix for PowerStore, or is a Dell PowerMax or VMAX3 system, Dell XtremIO X1 or XtremIO X2 system, or a NetApp AFF A-Series system. See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs.
NOTE: When the operating environment running on your source system matches the respective one listed in the Simple Support Matrix for PowerStore, you can choose to use the agentless import option instead of the non-disruptive option. However, the host plugin software must not be installed on the associated host or hosts.
See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs for the supported types of source systems and the version of operating environment required for the agentless import.
Overview of the agentless import process
Before importing the external storage from a source system to a PowerStore cluster, the active path for the host I/O is to the source system. The host or hosts are not automatically added to the PowerStore cluster and must be added manually before setting up the agentless import. During the setup of an agentless import, volumes are created on the PowerStore cluster that match the specified volumes on the source system. However, unlike non-disruptive import, the host applications that access the source system volume or volumes must be shut down manually and the source volumes brought offline.
NOTE: For host clusters, the source LUNs could have SCSI reservations keys. The SCSI reservations must be removed for imports to be successful.

Introduction

9

To start an agentless import, the destination volume must be manually enabled and the host application must be reconfigured to use the destination volume instead of the source volume. The destination volume is read-only until it is enabled. Once the destination volume has been enabled, the host application has to be reconfigured to access the destination volume. Start the import to copy the source volume data to the destination volume. The source system is kept updated through I/O forwarding from the PowerStore cluster. When the import reaches the Ready For Cutover state, you can initiate the cutover. The I/O forwarding from the PowerStore cluster to the source system ends when cutover is initiated.
Review the following processes to gain an understanding of the import procedure:
NOTE: You can also see the Importing External Storage to PowerStore video at https://www.dell.com/powerstoredocs.
1. Preconfigure ­ Set up the network connectivity. The connection between an existing Dell PS Series or NetApp AFF A-Series source system and the PowerStore cluster must be over iSCSI. For Dell PS Series source systems ­ All the connections between the hosts and source system and between the hosts and the PowerStore cluster must be over iSCSI. For Dell SC Series, Dell Unity Series, Dell VNX2 Series, Dell XtremIO X1 or XtremIO X2, and NetApp AFF A-Series source systems ­ The connections between the hosts and the source system and between the hosts and the PowerStore cluster must be either all over iSCSI or all over Fibre Channel (FC). NOTE: When FC connectivity between the host and source system and between the host and PowerStore cluster is used, the administrator must set up FC zoning between the hosts, source system, and the PowerStore cluster. The connection between an existing Dell SC Series, Dell Unity Series, Dell VNX2 Series, or Dell XtremIO X1 or XtremIO X2 source system and the PowerStore cluster can be over either iSCSI or FC. See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs to determine which protocol to use. For Dell SC Series, Dell Unity Series, Dell VNX2 Series, or Dell XtremIO X1 or XtremIO X2 source systems ­ The connections between the hosts and source system and between the hosts and the PowerStore cluster must be either all over iSCSI or all over FC and match the connection between the source system and the PowerStore cluster. See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs to determine which protocol to use. NOTE: When FC connectivity between the hosts and the source system, the hosts and the PowerStore cluster, and the source system and the PowerStore cluster is used, the administrator must set up FC zoning between the hosts, the source system, and the PowerStore cluster. The connection between an existing Dell PowerMax or VMAX3 source system and the PowerStore cluster must be over FC.
NOTE: The administrator must set up FC zoning between the source system and the PowerStore cluster.
For Dell PowerMax and VMAX3 source systems ­ All the connections between the hosts and the source system and between the hosts and the PowerStore cluster must be over FC.
NOTE: The administrator must set up FC zoning between the hosts, the source system, and the PowerStore cluster.
2. Setup import ­ If they are not already listed, add the source system and the hosts to the PowerStore cluster. Select one or more volumes or consistency groups (CGs), or both, or LUNs, or storage group to be imported. A volume group or storage group cannot be combined with any other volumes or volume group. Select to map the hosts that access the storage to be imported. Set the import schedule and assign a protection policy.
3. Start import ­ A destination volume is created for each selected source volume. A volume group is automatically created for each consistency group (CG) or storage group that is selected for import. When the destination volume is in the Ready To Enable Destination Volume state, shutdown or take off line the host application on the applicable host or hosts that use the source volume. Also, remove the host mapping to the applicable source system volume. Select and enable the destination volume which is in the Ready To Enable Destination Volume state. Reconfigure the host application to use the applicable destination volume. Select and Start Copy for the destination volume which is in the Ready to Start Copy state. NOTE: It is recommended to remove the host mapping of the source volumes during the enable destination volume process. If the host mapping of the source volumes is not selected for removal by the orchestrator, the mapping should be removed manually. Also, only one agentless import can be processed from the PowerStore cluster at any point in time until the import process reaches the Ready to Start Copy state. A second agentless import will start execution only after the previous import reaches the Copy In Progress state.
4. Cutover import ­ Cutover can be performed only when the import processing state is Ready For Cutover. In other words, cutover is a final confirmation. You can select to cut over automatically without user intervention.
In addition, the following actions are available during the import procedure:
Pause import ­ Pause can be performed when the import processing state is Copy In Progress.

10

Introduction

NOTE: The Pause import action on a CG only pauses the member volumes that are in the Copy In Progress state. The CG remains in the In Progress state. Other member volumes that are in other states, such as Queued or In Progress, are not paused and may proceed to the Ready For Cutover state. The other member volumes can be paused when they reach the Copy In Progress state by using the Pause import action again on the CG. If any of the member volumes are in the Paused state but the overall status of the CG is In Progress, both the Pause and Resume import action options are available for the CG. Resume import ­ Resume can be performed when the import processing state is Paused. Cancel import ­ For volumes, Cancel can be performed only when the import processing state is Queued, Scheduled, Ready To Enable Destination Volume, Ready to Start Copy, Copy In Progress, Paused, Ready for Cutover, or Cancel Required and the host application that is accessing the volume has been shut down. For volume groups, Cancel can be performed only when the import processing state is Queued, Scheduled, In Progress, Paused, Ready for Cutover, Cancel Required, Cancel Failed and the host application that is accessing the volume has been shut down. Enable Destination Volume ­ Ensure the host application on the applicable host or hosts that use the source volume or volumes have been shut down or taken off line before enabling each destination volume in an import session. Start Copy ­ Start Copy can be performed for each of the destination volumes that are in the Ready to Start Copy state.
Importing file-based external storage to PowerStore overview
Importing file-based external storage to PowerStore is a migration solution that imports a Virtual Data Mover (VDM) (file data) from a Dell VNX2 Series platform to a PowerStore cluster. The file import feature allows you to migrate a VDM with its configuration and data from an existing source VNX2 storage system to a destination PowerStore appliance. This feature provides a built-in capability for NFS-only VDM imports with minimal or no disruption to clients. It also provides a built-in capability for SMB (CIFS)-only VDM imports. However, cutting over of an SMB-only VDM import session can be a disruptive process.
For a file-based VDM import, after cutover completes, the import process does an incremental copy automatically but you must complete the import manually.
An import is always conducted from the PowerStore appliance. The destination system makes a remote call to the VNX2 storage system and instigates a pull (for file-based import) of the source storage resources to the destination system.
VDM import operations support only:
Import of VDM with only NFSV3 protocol enabled (VDMs with NFSV4 protocol enabled are not supported) Import of VDM with only SMB (CIFS) protocol enabled
NOTE: Import of VDM with multiprotocol file systems, or with both NFS and SMB (CIFS) file systems exported and shared is not supported.
Overview of the file-based import process
Review the following processes to gain an understanding of the file import procedure:
1. Prepare the source VDM for an import ­ Create a source import network interface. NOTE: The interface must be named nasmigration. Clients are connected to the source VDM either through the NFSv3 or SMB1, SMB2, or SMB3 file sharing protocol.
2. Add the remote system (to establish the import connection) ­ Establish a file import interface connection to the source VNX2 (Control Station management interface) from PowerStore over SSH. The system is validated, source VDMs are discovered (the configuration of file systems, network interfaces, and such are retrieved), and pre-checks identify the import capability for each VDM on the source system. NOTE: The procedure can be repeated on demand for an existing connection.
3. Create a file import session ­ Specify all the options for the import. NOTE: The user settings and the source VDM are validated. If an import session is scheduled to start at a later time, the Import State is shown as Scheduled. However, if two active import sessions (which is the maximum for active import sessions) are running, any new import sessions that are set to start are shown with an Import State of Queued.

Introduction

11

A maximum of ten import sessions can be scheduled or queued, however, only a maximum of eight import sessions can be scheduled or queued while two import sessions are active. 4. Start the file import session.
NOTE: The basic configuration of the source VDM must not change since an import session is created.
a. The import session begins ­ Destination NAS server, destination file mobility network and destination file systems are created. In the case of an NFS import, unexported file systems are exported.
b. Initial (baseline) data copy is initiated. Stable data and directory structure is pulled to the destination. c. Import of the configuration from the source VDM to the destination NAS server occurs. The configuration includes:
Production network interfaces Static routes DNS SMB server SMB shares NFS server NFS exports NIS LDAP Local files Effective naming service Quotas
NOTE: The session state is shown as Ready For Cutover when the import of the configuration completes. If the file system on the destination system is low on space (reaches 95% of capacity) during import, import of the source file system will fail. In this case you can either ensure that enough space is available and run Resume or Cancel the import session. 5. Cut over the import session ­ Production interfaces are disabled on the source side and enabled on the destination side. NOTE: For SMB import, the Active Directory configuration is imported and the switch over is disruptive. For NFS import, NLM locks are reclaimed for transparent switch over and clients may experience a 30-90s downtime.
An incremental data copy begins ­ Live import and re-synchronization of data from the source to the destination occurs. NOTE: Clients are connected to the destination and the source is updated with modifications from the destination. The source is authoritative. File Creation/Write is done first on the source. When re-synchronization occurs on a file, it is marked up to date and further reads are done from the destination. For a file or directory that is not synchronized yet, all operations are forwarded to the source. During synchronization, file read can be done on the destination (partial read) for imported data already committed on this file. Some configuration changes on the destination during an import are pushed back to the source in a rollback. During an import, snapshots/backups can be created on the source VDM. Replication from the source is still active and user quota management is still active on the source VDM. When all files are synchronized, the status of the import session is shown as Ready For Commit.
6. Commit the import session ­ Protocol data connections to the source terminate and synchronizing modifications stop. The destination import interface is deleted and cleanup of the source system occurs. The final state is shown as Completed.
In addition, the following actions are available during the import procedure:
Pause import ­ Pause can be performed when the import processing state is Copy In Progress during session create or cutover operations. NOTE: When a user tries to pause an import session when an incremental copy is about to complete, the session can be transitioned automatically from the Paused state to the Ready For Commit state without the user having to resume the import session. The Ready For Commit state is equivalent to the Paused state in terms of the load on the source system.
Resume import ­ Resume can be performed when the import processing state is Paused. Cancel import ­ Cancel is allowed at any state of the file import session except Completed, Failed, Cancelling and
Cancelled. Production interfaces are disabled on the destination side and enabled on the source side. Cancel is disruptive for NFS and SMB clients. Some changes to the configuration will be synchronized from the destination to the source. The source system is cleaned up and the destination NAS server is deleted. Cancelled is a terminal state. Cancel can be forced if the source stops responding.

12

Introduction

PowerStore cluster fibre channel connectivity to source systems
PowerStore operating system version 3.0 or later provides an option to import data from an external source system to a PowerStore cluster using Fibre Channel (FC) connectivity. The WWN of the destination system is automatically discovered for FC data connection. The Connection is automatically established from PowerStore to the source system. Host groups are automatically created on the source system with FC initiators and mapped during import. Intelligent volume placement occurs within the PowerStore cluster during Import. The host groups are created upon addition of the remote system in PowerStore.
Both agentless and non-disruptive import variants support FC connectivity. PowerStore with FC connectivity to a source system supports only FC connectivity with the hosts also.
NOTE: The Simple Support Matrix document for PowerStore lists what protocol is supported for the connection between hosts, source system, and PowerStore.
PowerStore creates connection to the remote destinations based on an internal high availability (HA) policy. The number of connections from a FC initiator to destinations is determined by the system. Each initiator port sequentially connects to a unique destination in each controller, SP, or Director of the respective remote system. Configuration on Node A is applied as is in Node B on a best effort basis. PowerStore automatically determines the internal HA policy compliance during Create/Verify/ Connection health change.
Import capable I/O Module0 Ports
Importing data from an external source system into PowerStore with FC connectivity requires that ports 0 and 1 of PowerStore I/O Module0 are enabled as Dual (as both initiator and target). A maximum of two destinations can be connected from each node, for example:
For Dell Unity or Dell VNX2, make connections from each PowerStore node to two different Dell Unity or Dell VNX2 SPs or controllers. For example, connect port P0 of PowerStore Node A and Node B through a switch to the destination port T0 of SPA of the Dell Unity source system. Connect port P1 of PowerStore Node A and Node B through a switch to the destination port T2 of SPB of the Dell Unity source system.
For Dell PowerMax or VMAX3, make connections from each PowerStore node to two different Dell PowerMax or VMAX3 directors. For example, connect port P0 of PowerStore Node A and Node B through a switch to the destination port T0 of PowerMax source system Director-X. Connect port P1 of PowerStore Node A and Node B through a switch to the destination port T2 of PowerMax source system Director-Y.
For Dell Compellent SC, connection from each PowerStore node is made to two controllers through two fault domains. In case multiple fault domains are configured, make connection to a maximum of two fault domains. In case of legacy mode, make the connection to primary ports through two different fault domains. Make connections from each PowerStore node to two different Dell Compellent SC controllers. For example, connect port P0 of PowerStore Node A and Node B through Fault Domain 1 to the destination port T0 of Dell Compellent SC source system Controller A. Connect port P1 of PowerStore Node A and Node B through Fault Domain 2 to the destination port T2 of Dell Compellent SC source system Controller B.
See FC connections between Controllers of remote system and PowerStore Nodes as an example.

Introduction

13

Figure 1. FC connections between Controllers of remote system and PowerStore Nodes

Table 1. PowerStore to remote system port configuration

PowerStore Node

PowerStore (P) to target remote system (T) port configuration

A

P0 to T0

P1 to T2

B

P0 to T0

P1 to T2

PowerStore ports P0 and P1 on Nodes A and B refer to Fibre Channel I/O Module0 FEPort0 and FEPort1, respectively. The SCSI Mode setting for these ports should be set to Dual (both initiator and target).
NOTE: To view the list of import capable ports on a PowerStore appliance in PowerStore Manager, select an appliance under Hardware, and then select Fibre Channel on the Ports card.
Login to the source system is initiated after the remote system is added. PowerStore connects only to the allowed list of destinations.

Import security

Communication between the source system, hosts, and the PowerStore cluster is provided by using HTTPS certificates. These certificates are used to establish secure communication between the following import components:
PowerStore cluster and the source system PowerStore cluster and the host systems
PowerStore Manager provides an option to view and accept the remote certificates when adding a host to the PowerStore cluster.
NOTE: PowerStore Manager is a web-based software application that enables you to monitor and manage storage resources, virtual machines, and appliances within a PowerStore cluster.
When the source storage volumes are configured with CHAP, data transfer is secured with CHAP support, Discovery CHAP, and Authentication CHAP. The PowerStore cluster supports both single and mutual CHAP. For more information about CHAP support, see CHAP restrictions.

14

Introduction

Import requirements and restrictions

This chapter contains the following information:
Topics:
· General requirements for importing data · Dell EqualLogic PS Series specific requirements · Dell Compellent SC Series specific requirements · Dell Unity specific requirements · Dell VNX2 Series specific requirements · Dell XtremIO XI and X2 specific requirements · Dell PowerMax and VMAX3 specific requirements · NetApp AFF and A Series specific requirements · General block- based import restrictions · General file-based import restrictions
General requirements for importing data
The following requirements apply to PowerStore before running import:
The global storage IP address for PowerStore must be configured. Verify that PowerStore and its nodes are in a healthy state.
The following requirements apply to all source platforms:
(For non-disruptive import) You must have the appropriate privileges on the source and its associated hosts to perform an import to a PowerStore cluster. For Windows-based systems, Administrator privilege is required to perform an import to a PowerStore cluster. For Linux-based and VMware-based systems, root privilege is required to perform an import to a PowerStore cluster.
(For non-disruptive import) A Fibre Channel (FC) or iSCSI connection exists between the source system and each associated host system, and a matching FC or iSCSI connection exists between each associated host system and the PowerStore cluster. These connections to each host system should be of the same type, either all FC or all iSCSI.
(For agentless import) For Dell PS source systems, all the connections between the hosts and the Dell PS source system and between the hosts and the PowerStore cluster must be over iSCSI. For Dell PowerMax or VMAX3, a FC connection exists between the source system and each associated host system, and a matching FC connection exists between each associated host system and the PowerStore cluster. For Dell SC or Unity, or Dell VNX2, XtremIO X1, XtremIO X2 source systems, or NetApp AFF or A Series source systems, the connections between the hosts and the source system and between the hosts and the PowerStore cluster must be either all over iSCSI or all over Fibre Channel (FC). NOTE: When FC connectivity between the host and source system and between the host and PowerStore cluster is used, the administrator needs to set up FC zoning between the host, the source system, and the PowerStore cluster.
Only an iSCSI connection is supported between the following source systems and the PowerStore cluster. Dell EqualLogic PS Dell Compellent SC (non-disruptive import) NetApp AFF and A Series (agentless import)
Only a FC connection is supported between a Dell PowerMax or VMAX3 source system (agentless import) and the PowerStore cluster.
Either an iSCSI connection or a FC connection is supported between a Dell Compellent SC (agentless import) or Unity, or Dell VNX2 source system and the PowerStore cluster. NOTE: The connection between the Dell Compellent SC (agentless import) or Unity, or Dell VNX2 source system and the PowerStore cluster, and the connections between the hosts and the source system and between the hosts and the PowerStore cluster must be either all over iSCSI or all over FC.
(For non-disruptive import) Only one instance of MPIO should be running on the host in order to perform an import.

Import requirements and restrictions

15

The Simple Support Matrix for PowerStore lists the host OS platforms that are supported for non-disruptive import. NOTE: If the operating environment running on the source system does not match what is listed in the Simple Support Matrix for PowerStore or the source system is a Dell XtremIO X1 or XtremIO X2, or PowerMax or VMAX3, or a NetApp AFF or A Series, use the agentless import option to migrate the external storage to the PowerStore cluster. The Simple Support Matrix for PowerStore lists the supported types of source systems and operating environment required for agentless import. Agentless import can also be used to migrate the external storage from a source system running the operating environment listed in the Simple Support Matrix for PowerStore for non-disruptive import. For the most up-to-date supported versions of the supported combinations of host OS, multipath software, host protocol to the source and to the PowerStore cluster, and the type of source system for non-disruptive (seamless) import, see the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs.
When Fibre Channel (FC) connectivity is used between the host and the PowerStore cluster, the administrator needs to set up FC zoning between the dual mode FC ports to the destinations. NOTE: For more information about FC zoning, see PowerStore Host Configuration Guide at https://www.dell.com/ powerstoredocs.
When Fibre Channel (FC) connectivity is used between the source system and the PowerStore cluster, the administrator needs to set up FC zoning between the source system and the PowerStore cluster. NOTE: For FC connections, it is recommended to configure FC zoning in such a way that PowerStore can connect to at least to 2 distinct targets on each remote system controller from a PowerStore node. See PowerStore cluster fibre channel connectivity to source systems.
(For non-disruptive import) Depending on the port number that is selected for the hosts that are added when creating an import session, that port must be open on the firewall. The predefined host ports for Windows and Linux are: 8443 (default) 50443 55443 60443 The predefined host port for VMware is 5989.
Dell EqualLogic PS Series specific requirements
(For non-disruptive import) See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs for the supported combinations of host OS, host multipath software, and host protocol that apply to Dell EqualLogic Peer Storage (PS) Series systems.
NOTE: (For non-disruptive import) If you are not running the Dell EqualLogic Host Integration Tools Kit, you can use the PowerStore cluster ImportKIT which uses native MPIO.
(For agentless import) See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs for the supported types of source systems and the version of operating environment required for the agentless import.
NOTE: All hosts taking part in an import process should have initiator names in the standard IQN format. Although friendly names are supported by PS source systems for the standard IQN format, PowerStore only supports valid standard IQN format. Import will fail when friendly IQN names are used. In this case, the initiator names must be changed to valid full IQN names on all the associated hosts before attempting an import of external storage to PowerStore.
Dell Compellent SC Series specific requirements
NOTE: The size of any volume imported from a Dell Compellent SC Series system to a PowerStore cluster must be a multiple of 8192.
(For non-disruptive import) See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs for the supported combinations of host OS, host multipath software, and host protocol that apply to Dell Compellent Storage Center (SC) Series systems.
NOTE: While importing external storage from a Dell Compellent SC Series source system, do not delete or place the source resource in the Recycle Bin.

16

Import requirements and restrictions

(For agentless import) See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs for the supported types of source systems and the version of operating environment required for the agentless import.
Dell Unity specific requirements
(For non-disruptive import) See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs for the supported combinations of host OS, host multipath software, and host protocol that apply to Dell Unity systems. (For agentless import) See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs for the supported types of source systems and the version of operating environment required for the agentless import.
Dell VNX2 Series specific requirements
(For non-disruptive import) See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs for the supported combinations of host OS, host multipath software, and host protocol that apply to Dell VNX2 Series systems.
NOTE: The supported OE on the Dell VNX2 has to be committed in order to perform an import of its storage resources. (For agentless import) See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs for the supported types of source systems and the version of operating environment required for the agentless import.
Dell XtremIO XI and X2 specific requirements
(For agentless import) See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs for the supported types of source systems and the version of operating environment required for the agentless import.
Dell PowerMax and VMAX3 specific requirements
(For agentless import) See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs for the supported types of source systems and the version of operating environment required for the agentless import.
NOTE: For agentless import, Unisphere version 9.2 or later is required as the application to configure and manage either a PowerMax system or a VMAX3 system.
NetApp AFF and A Series specific requirements
(For agentless import) See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs for the supported types of source systems and the version of operating environment required for the agentless import.
General block-based import restrictions
The following restrictions apply to importing block-based external storage to PowerStore: At any given time a maximum of 6 source systems is supported. (For non-disruptive import) A maximum of 64 hosts is supported. The applicable host plugin for import must be installed on
the host. (For agentless import) See the PowerStore Simple Support Matrix for the maximum number of hosts that are supported. A maximum of 8 parallel import sessions is supported, but they all start sequentially. That is, imports start one by one but,
once they reach Copy-In-Progress, the next one is taken for processing. (For non-disruptive import) A maximum of 16 volumes in a consistency group (CG) is supported.

Import requirements and restrictions

17

NOTE: When a CG has 16 members, a maximum of 8 members is imported in parallel, but they all start sequentially.
That is, imports start one by one but, once they reach Copy-In-Progress, the next one is taken for processing. Once
any one of them reaches Ready-For-Cutover, the next member is imported in parallel. Once all the members reach
Ready-For-Cutover, the CG is Ready-For-Cutover.
(For agentless import) A maximum of 75 volumes in a consistency group (CG) is supported. NOTE: When a CG has 75 members, a maximum of 8 members is imported in parallel, but they all start sequentially.
That is, imports start one by one but, once they reach Copy-In-Progress, the next one is taken for processing. Once
any one of them reaches Ready-For-Cutover, the next member is imported in parallel. Once all the members reach
Ready-For-Cutover, the CG is Ready-For-Cutover.
A CG that has volumes that are mapped to hosts running different types of operating systems cannot be imported. For example, a CG having volumes from a Linux host and Windows host cannot be imported.
NVMe host mapping on PowerStore is not supported for importing a volume or CG. A maximum of 16 import sessions is supported in the Ready-For-Cutover state. Sometimes when several dozen import
operations are run back-to-back, intermittent failures of alternate import sessions may occur. If this occurs, do the following:
1. Remove the remote (source) system and then add it again.
2. Run fewer set of imports (16 or less) at a time. It is recommended to start all these import sessions with automatic cutover turned off.
3. Once all imports have reached the Ready-For-Cutover state, do a manual cutover.
4. After one set of imports is completed, run the next set of imports after a delay of 10 minutes. This delay allows enough time for the system to cleanup any connections to the source system.
You can import only an active volume or LUN. Snapshots are not imported. It is not recommended to change a host cluster configuration once the volume is selected for import. All the target port IP addresses returned by the PowerStore’s iSCSI target portal should be reachable from the host where
import is planned. Replication relationships are not imported. SAN boot disks are not supported. IPv6 is not supported. Veritas Volume Manager (VxVM) is not supported. (For non-disruptive import) Only implicit ALUA mode is supported on source systems. The following configuration changes are not supported on the source system during import:
Firmware or Operating Environment upgrade System re-configuration, including network configuration and restart of node or members When any configuration changes, such as moving a volume between hosts or re-sizing the source system volume capacity, are made to the source or a host system after they have been added to PowerStore, all the affected or involved systems must be refreshed from PowerStore Manager. Only an iSCSI connection is supported between the following source systems and the PowerStore cluster: Dell EqualLogic PS (For agentless import) NetApp AFF and A Series Either an iSCSI connections or Fibre Channel (FC) connection is supported between a Dell Compellent SC or Unity, or Dell VNX2, or XtremIO X1 or XtremIO X2 source system and the PowerStore cluster. However, the connection between the Dell Compellent SC or Unity, or Dell VNX2, or XtremIO X1 or XtremIO X2 source system and the PowerStore cluster, and the connections between the hosts and the Dell Compellent SC or Unity, or Dell VNX2, or XtremIO X1 or XtremIO X2 source system and between the hosts and the PowerStore cluster must be either all over iSCSI or all over FC. (For agentless import) Only a FC connection is supported between a Dell PowerMax or VMAX 3 source system and the PowerStore cluster. (For non- disruptive import) SCSI-2 clusters are not supported. Only SCSI-3 persistent reservation (PR) clusters are supported. Heterogeneous host cluster is not supported. Configuration changes must not be made during import, such as resizing a volume during import or adding or removing a host node in a cluster configuration, on either the source system or PowerStore. The following configuration changes are allowed but not supported on either the source system or PowerStore during import for consistency groups: Removing members from consistency group Restoring Cloning Snapshot Consistency group migration Creating replication Refreshing volume Such operations should be done before starting import.

18

Import requirements and restrictions

Snapshot restore on a volume under import is not supported. Only 512b-sector sized devices are supported from the following systems, 4k-sector devices are not supported from these
systems: Dell EqualLogic PS Dell Compellent SC Dell Unity Dell VNX2 Both 512b- sector and 4k-sector resources are supported from XtremIO systems. iSCSI hardware initiators are not supported. Running in iSCSI Data Center Bridging (DCB) configurations is not supported for Dell EqualLogic PS series and Dell Compellent SC series. Do not delete then add the same VNX2 remote system again in a very short interval (few seconds). The add operation may fail because the software cache on the VNX2 may not have completed being updated. Wait at least five minutes between these operations for the same VNX2 remote system.
CHAP restrictions
The following describes the CHAP support for importing external storage to a PowerStore cluster:
For Dell Unity and VNX2 systems, source volumes with single CHAP can be imported, source volumes with mutual CHAP cannot be imported.
For Dell EqualLogic Peer Storage (PS) series, there are three cases: When Discovery CHAP is disabled, source volumes with both single and mutual CHAP can be imported. If Discovery CHAP is enabled, source volumes with single CHAP can be imported. If Discovery CHAP is enabled, source volumes with mutual CHAP cannot be imported. NOTE: If Dell Unity or VNX2 systems are added in CHAP enabled mode and if a Dell EqualLogic PS system is added, ensure that Discovery CHAP is enabled for the Dell EqualLogic PS system.
For Dell Compellent Storage Center (SC) series, source volumes with both single and mutual CHAP can be imported. Each host must be added with unique CHAP credentials.
Source system restrictions
Each source system has its own restrictions, for example, the maximum number of volumes supported and the maximum number of iSCSI sessions allowed. Importing external storage to PowerStore must work within these limitations of the source systems and the limitations of the PowerStore cluster.
For restrictions specific to a source system, see the source-specific documentation. Go to Online Support (registration required) at: https://www.dell.com/support. After logging in, locate the appropriate Product Support page.
General restrictions for hosts
The following restrictions apply to hosts:
(For non-disruptive import) Applications must be configured to use a given MPIO handle. In other words, the host applications must be actively using either EqualLogic MPIO, or Native MPIO. See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs. Use of dynamic multi- pathing (DMP), Secure-Path, and PowerPath MPIOs are not supported.
(For non-disruptive import) Hosts should have only one MPIO installed that manages both the source and the PowerStore cluster.
Heterogeneous host cluster is not supported. The maximum of a 16 node cluster import is supported. During import, following configuration changes are not supported on the host:
(For non-disruptive import) Change of MPIO policy during import. Changes to the paths (enable or disable) which can impact the import operation. Host cluster configuration changes. Operating system (OS) upgrades.

Import requirements and restrictions

19

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 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. For LVMs, ensure that the option allow_changes_with_duplicate_pvs is enabled in /etc/lvm/lvm.conf. If this
option is set to 0 (disabled), change it to 1 (enabled). Otherwise, imported logical volumes will not become active again after a host reboot if duplicate Port VLAN identifiers (PVIDs) are discovered. 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 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.

20

Import requirements and restrictions

VMware ESXi-based hosts
The following restrictions apply during a non-disruptive import involving VMware ESXi-based hosts:
Import is supported only for those datastores that have a 1:1 mapping with a back-end volume. Linux Raw Device Mapping (RDM) configurations are not supported. If RDM LUNs which are exposed to the VM are imported, the enquiry command on those LUNs will report either the source
UID or the destination UID depending on the ESXi cache enablement. If the ESXi cache is enabled and upon inquiry, the source UID would be reported, otherwise the destination UID would be reported. If xcopy is tried between imported and non-imported volumes, it will fail gracefully and user copy will be initiated instead. ESXi supports only dynamic discovery level CHAP. Non-disruptive import does not support vVols. If the host has vVols or a Protocol Endpoint mapped, it is recommended not to install the host plugin and to use agentless import instead.
The following restriction applies for an agentless import involving VMware ESXi-based hosts:
The minimum host operating system version required is ESX 6.7 Update 1.
General file-based import restrictions
The following restrictions apply to importing file-based external storage to PowerStore:
Only Unified VNX2 is supported as import source storage system. VDM containing both NFS exports and SMB shares cannot be imported. VDM containing multiple SMB servers cannot be imported. VDM with the NFSv4 protocol enabled cannot be imported (no NFS ACL import). VDM with Secure NFS or pNFS configured cannot be migrated. Do not import replication (although replication can be running during the import). Do not import checkpoint/snapshot or checkpoint/snapshot schedule. Compressed files are uncompressed during import. No transparency on cutover for SMB (even in SMB3 with Continuous Availability). Changes to the file mobility network configuration or network issues that occur during an import session may cause an
import operation to fail. Do not change network attributes (such as MTU size or IP address) and source VDM attributes during an import session.
These changes can cause an import operation to fail. File system limitations:
VDM having a Nested Mount File System (NMFS) cannot be imported. A file system mounted directly on DM cannot be imported. A file system that is a replication destination cannot be imported. A file system whose mount path contains more than 2 slashes cannot be imported. The destination file system size may be larger than the source file system size. Rollback limitations: Rollback may be disruptive (NFSv3 clients also have to remount). Rollback of the configuration to the source is very limited. Do not import FTP or SFTP (File Transfer Protocol), HTTP (Hyper Text Transfer Protocol), and Common Event Publishing Agent (CEPA) and Common Anti-Virus Agent (CAVA) settings. Do not import from unhealthy systems.
NOTE: For example, if a Data Mover (DM) is offline and does not respond during the remote system addition and object discovery for all importable objects, many commands that have to run may fail. Disable the problematic DM in the configuration. This action should allow the import to be created. Do not assign the session name of a deleted import session to an import session that is being created. The session name still exists in the file database and is deleted only when the remote system is deleted. When you configure an import and select a date and time for the import session to begin, do not schedule the import to begin within 15 minutes of the current time.
NOTE: A user can change the source configuration, however, that action causes the import to fail.

Import requirements and restrictions

21

Restrictions and limitations for SMB-only VDM file import
The following restrictions and limitations relate to a SMB-only VDM file migration from a VNX2 storage system to a PowerStore appliance:
Only Unified VNX2 storage systems are supported as the source storage system in a VDM file-based import. Only VNX2 storage systems with operating environment (OE) version 8.1.x or later are supported. SMB1 must be enabled on the VNX2 source system. SMB2 and SMB3 are not supported in a VDM file-based import. Upgrading a PowerStore appliance when an import session is in progress is not supported. Creating an import session when an upgrade session is in progress is not supported. PowerStore supports a VDM import session with at most 500 file systems on the source VDM. The destination system must have enough available capacity to host the source resources to be imported.
PowerStore appliances use a different file system layout than Unified VNX2 storage systems. PowerStore appliances use UFS64 file systems while VNX2 storage systems use UFS32 file systems.
Import of deduplicate settings is not supported. During the import session, data is un-deduplicated and un-compressed. A versioning file and fast clone are imported as a normal file. PowerStore appliances with operating system versions
earlier than 3.0 do not support file-based import and File Level Retention (FLR). PowerStore appliances with operating system version 3.0 or later support file-based import and both FLR-E and FLR-C.
Only uxfs-type file systems are imported from the VNX2 source VDM. Import of non-uxfs-type file systems or file systems that are mounted on a Nested Mount File System (NMFS) file system are not supported.
A file system whose mount path contains more than two slashes is not supported. The destination system does not allow file systems with a name containing multiple slashes, for example, /root_vdm_1/a/c.
Import of a file system that is a replication destination is not supported. Import of a checkpoint or checkpoint schedule is not supported. If the source replication file system is also the destination file system of a VDM import session, failing over the replication
session (synchronous or asynchronous) is not allowed until the import is complete.
Restrictions that are related to Quota import: Import of group quota or inode quota settings is not supported. (The destination system does not support either.) Import of a tree quota whose path contains single quotation marks is not supported. (A VNX2 system can create it but it cannot be queried or modified.)
Limitations that are related to Host access: After cutover, read access performance degrades until the related file is migrated. After cutover, write access performance degrades until the VDM file migration is completed. After cutover, a host cannot write data when the source file system is in the read- only mounted state. (Does not apply to PowerStore appliances running operating system 3.0 or later) PowerStore appliances running operating system version 2.1.x or earlier do not support file-based import and FLR.
After cutover, a host cannot access data when the destination file mobility network cannot access the source file system, which includes the following cases: The network between the source VDM file migration interface and the destination file mobility network is disconnected. The source VDM is not in either the loaded or mounted state. The user modifies the source export, which makes the destination system’s file mobility network unable to access the source file system.
Protocol restrictions: Import of NFS settings, multiprotocol settings, and related settings is not supported. For example, LDAP, NIS, local password, group and netgroup files, mount options other than synchronous write, op locks, notify on write, and notify on access.
Import of FTP or SFTP (File Transfer Protocol), HTTP (Hyper Text Transfer Protocol), or CEPP (Common Event Publishing Protocol) is not supported.
Cancel restrictions and limitations: Only some configuration changes, such as the destination VDM’s SMB shares, or local users along with data changes to the source file systems are rolled back to the source VDM.
Configuration restrictions and limitations: Import of NTP configuration is not supported. Only enabled network interfaces on the source VDM are imported. Disabled network interfaces on the source VDM are not imported. (The destination system does not allow you to enable or disable network interfaces.)
File Level Retention (FLR) file systems can be imported on PowerStore appliances running operating system version 3.0 or later. However, PowerStore appliances with operating system versions earlier than 3.0 do not support file-based import and FLR.

22

Import requirements and restrictions

Distributed Hierarchical Storage Management (DHSM)/(Cloud Tiering Appliance (CTA) might be configured on the source VNX2 for archiving inactive files to secondary storage. If DHSM/CTA is configured on the source VNX2 system and a VDM import to a PowerStore cluster is run, all the files on the associated file system are recalled from the secondary storage to the source VNX2.
Only limited configuration changes to the source VDM and the destination NAS server are supported during import: Shares Local groups Local users Privileges Home directory Distributed File System (DFS) (only pre-existing DFS shares are synchronized during a cancel operation) Those are also the only configuration settings that are synchronized with the source if the migration is canceled.
Restrictions and limitations for NFS-only VDM file import
The following restrictions and limitations relate to an NFS-only VDM file migration from a VNX2 storage system to a PowerStore cluster:
Only Unified VNX2 storage systems are supported as the source storage system in a VDM file import. Only VNX2 storage systems with operating environment (OE) version 8.1.x or later are supported. Upgrading a PowerStore appliance when an import session is in progress is not supported. Creating an import session when an upgrade session is in progress is not supported. PowerStore supports a VDM import session with at most 500 file systems on the source VDM. The destination system must have enough available capacity to host the source resources to be imported.
PowerStore appliances use a different file system layout than Unified VNX2 storage systems. PowerStore appliances use UFS64 file systems while VNX2 storage systems use UFS32 file systems.
Import of deduplication settings is not supported. A versioning file and fast clone are imported as a normal file. PowerStore appliances with operating system versions
earlier than 3.0 do not support file-based import and File Level Retention (FLR) PowerStore appliances with operating system version 3.0 and later support file-based import and both FLR-E and FLR-C. Only uxfs-type file systems are imported from the VNX2 source VDM. Import of non-uxfs-type file systems or file systems that are mounted on a Nested Mount File System (NMFS) file system are not supported. A file system whose mount path contains more than two slashes is not supported. The destination system does not allow file systems with a name containing multiple slashes, for example, /root_vdm_1/a/c. Import of a file system that is a replication destination is not supported. Import of a checkpoint or checkpoint schedule is not supported. If the source replication file system is also the destination file system of a VDM import session, failing over the replication session (synchronous or asynchronous) is not allowed until the import is complete. Restrictions that are related to Quota import: Import of group quota or inode quota settings is not supported. (The destination system does not support either.) Import of a tree quota whose path contains single quotation marks is not supported. (A VNX2 system can create it but it cannot be queried or modified.) A VAAI operation is not allowed on either the source or destination systems during and after cutover. A VAAI operation is not allowed on the destination system before cutover. A VAAI operation on the source system must finish before cutover. Limitations that are related to Host access: After cutover, read access performance degrades until the related file is imported. After cutover, write access performance degrades until the VDM file migration is completed. After cutover, a host cannot write data when the source file system is in the read-only mounted state. PowerStore appliances running operating system version 2.1.x or earlier do not support FLR, and the default import setting is to not import such file systems. However, you can override the default, and those file systems are imported as normal destination file systems (UFS64) without FLR protection. This means that after cutover, locked files can be modified, moved, or deleted on the destination PowerStore appliance, but not on the source VNX2 system. This discrepancy can cause the two file systems to be in an inconsistent state. After cutover, a host cannot access data when the destination file mobility network cannot access the source file system, which includes the following cases: The network between the source VDM file migration interface and the destination file mobility network is
disconnected. The source VDM is not in either the loaded or mounted state.

Import requirements and restrictions

23

The user modifies the source export, which makes the destination file mobility network unable to access the source file system.
Protocol restrictions: Import of SMB, multiprotocol settings, and related settings is not supported when performing an NFS-only import. These settings include settings for SMB server, SMB share path and options, Kerberos key, CAVA (Common AntiVirus Agent), usermapper, and ntxmap. Import of a VDM using Secure NFS, NFSv4, or pNFS is not supported. Import of FTP or SFTP (File Transfer Protocol), HTTP, or CEPP (Common Event Publishing Protocol) is not supported. The NFS protocol is transparent, but sometimes client access behaviors can be impacted. Client access issues can arise from policy differences between the source VNX2 system and the destination PowerStore appliance. NOTE: NFSv3 I/O is transparent for SP failover and failback during the incremental copy stage. However, if failover
or failback begins as the node is imported, an error may occur, disrupting client access and resulting in an I/O error.
This error is resolved when the node is re-synchronized.
NFSv3 operations such as CREATE, MKDIR, SYMLINK, MKNOD, REMOVE, RMDIR, RENAME, and LINK may fail with error during import cutover. For example, before cutover, an operation finishes successfully on the source VNX2 side. However, the client does not receive the response; after cutover, the client retries the same operation silently after cutover in an under layer.
For example, if a file has already been removed on the source VNX2 side before cutover, the silent retry of the REMOVE operation fails with a NFS3ERR_NOENT message. You may see the remove failure even though the file has been removed on the file system. This failure notification occurs because after cutover, the XID cache that is used to detect duplicated requests does not exist on the destination PowerStore side. The duplicated request cannot be detected during cutover.
Rollback restrictions and limitations: After rollback, a host may need to remount the NFS file system if the interface configurations are different between the source VDMs and the destination NAS Servers. Only rollback data changes to the source file systems are supported. Rollback of any configuration changes to the NAS server and file systems on the destination PowerStore appliance is not supported. For example, if you add an NFS export to a file system, a rollback does not add the new NFS export to the source VNX2 storage system.
Configuration restrictions and limitations: Import of NTP configuration is not supported. Import of server parameter settings (VNX2 server_param settings except for the IP reflect parameter) is not supported. Import of LDAP configuration with Kerberos authentication (SMB server is not imported) is not supported. Import of client certificates, which the LDAP server requires (persona is not supported on the PowerStore appliance), is not supported. Import of customized cipher list for LDAP connection (customized cipher list is not supported on the PowerStore appliance) is not supported. If multiple LDAP servers are configured with different port numbers that are used by the source VDM, only the server with the port number equal to the first server is imported. If both NIS and LDAP are configured and taken into effect for the naming service on the source VDM, you must select one of them to take effect on the destination NAS server. If local files are configured and taken into effect for the naming service on the source VDM, you can select whether the local files take effect on the destination NAS server. The search order of the local files is always higher than NIS or LDAP on the destination NAS server. Only enabled network interfaces on the source VDM are imported. Disabled network interfaces on the source VDM are not imported. (The destination system does not allow you to enable or disable network interfaces.) FLR file systems can be imported on PowerStore appliances running operating system version 3.0 or later. However, PowerStore appliances with operating system versions earlier than 3.0 do not support file-based import and FLR. Distributed Hierarchical Storage Management (DHSM)/(Cloud Tiering Appliance (CTA) may be configured on the source VNX2 for archiving inactive files to secondary storage. If DHSM/CTA is configured on the source VNX2 system and a VDM import to PowerStore is run, all the files on the associated file system are recalled from the secondary storage to the source VNX2. Those files are then imported to the PowerStore cluster as normal files (that is, no stub files are imported).
Restoring NDMP backups: The NDMP backup path on VNX2 is /root_vdm_xx/FSNAME while the same path on PowerStore is /FSNAME. If any file system of the source VNX2 VDM is protected by NDMP and already backed up, then after VDM file import, those file systems cannot be restored to PowerStore using the original path option. A restore using the original path option fails due to an unavailable destination path. Instead, use the alternative path option.

24

Import requirements and restrictions

Importing VNX2 file systems with File Level Retention (FLR) enabled
PowerStore appliances running operating system version 3.0 or later support both FLR-E and FLR-C. When importing an FLR-enabled file system from a VNX2 system to a PowerStore appliance, ensure the PowerStore appliance is running operating system version 3.0 or later.
NOTE: PowerStore appliances running operating system version 2.1.x or earlier do not support file-based import and FLR.
Limitations related to host access and NFS datastores
When performing a VDM import of FLR-enabled file systems to PowerStore, the source VNX2 Data Mover must be running the DHSM service for the import to succeed. Also, if the source DHSM service authentication is set to None, you do not need to configure the DHSM credentials, username and password, on PowerStore for import. However, if the source DHSM service authentication is set to either Basic or Digest, you must configure those credentials at the PowerStore appliance as part of the import configuration. If DHSM is not already configured on the source file system, refer to the VNX2 system’s Unisphere online help or the VNX Command Line Interface Reference for File for information about setting up the DHSM configuration on the source VNX2 system. PowerStore appliances do not support FLR on NFS datastores. Therefore, VNX2 FLR-enabled file systems cannot be imported to PowerStore as NFS datastores. They can only be imported as file system objects.
NOTE: If the source VNX2 file system is FLR-enabled, you cannot change the destination resource from a file system to an NFS datastore. This action is not allowed.
Port requirements for DHSM when FLR is enabled
The default DHSM service port is 5080 on both VNX2 and PowerStore appliances. However, the VNX2 Data Mover (the physical Data Mover that hosts the VDM that is being imported) that is configured with the DHSM service can be set to a different port than the default. This port must match on both systems in order for the import of FLR-enabled file systems to succeed. To import FLR-enabled file systems when the source VNX2 Data Mover is using another port instead of the default, if possible, change the VNX2 Data Mover that is configured with the DHSM service to use the default port 5080.
VNX2 port requirements for file-based data import
To import file-based data from a VNX2 system to a PowerStore cluster, PowerStore should be able to access the following ports on the VNX2 system: 22, 443, and 5989 to establish import connections 111, 137, 138, 139, 389, 445, 464, 1020, 1021, 1234, 2049, 2400, 4647, 31491, 38914, and 49152-65535 for NFS VDM import 137, 138, 139, 445, and 12345 for SMB (CIFS) VDM import
NOTE: On the VNX2 source system, the physical Data Mover that is configured with the DHSM service can be set to a different port than the default port 5080. This port must match on both VNX2 and PowerStore in order for the import of FLR-enabled file systems to succeed. To import FLR-enabled file systems, if the source VNX2 Data Mover is not using the default port, If possible, change the VNX2 Data Mover that is configured with the DHSM service to use the default port 5080 before creating the file import:
For more information related to ports on the VNX2 system, refer to the EMC VNX Series Security Configuration Guide for VNX.

Import requirements and restrictions

25

3
Host plugin installation (block-based nondisruptive import only)
This chapter contains the following information:
Topics:
· Installing the host plugin for import on a Windows-based host · Installing the host plugin for import on a Linux-based host · Installing the Dell EqualLogic MEM kit on an ESXi-based host · Uninstalling the host plugin for import
Installing the host plugin for import on a Windowsbased host
See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs for a list of the supported source systems and operating environments that are applicable to Windows-based hosts. In addition to single host, cluster configurations are supported. Also, two variants of the host plugin for import are available for Windows: Dell EqualLogic Host Integration Tools Kit ImportKIT
NOTE: The MSI installer, which is a Windows component and is spawned when setup64.exe runs, runs in the context of SYSTEM account (msi server). This process in turn spawns multiple sub processes which are also named msiexec.exe. These sub processes by default are provided a security right that is called Log on as a service. All installer-related services are usually provided this right by default by the operating system. However, there are specific cases where this right is not provided. In such systems you must use the group policy editor, gpedit.msc, and assign this right. See https://docs.microsoft.com/en-us/windows/security/threat-protection/security- policy-settings/log-on-asa-service for more information.
Dell EqualLogic Host Integration Tools Kit
Both upgrade and fresh install are supported for the Dell EqualLogic Host Integration Tools Kit. For a fresh install, run the install file, Setup64.exe, only once. For more information, see Dell EqualLogic Host Integration Tools for Microsoft Installation and User’s Guide at https://www.dell.com/support. Upgrade has two steps: 1. Run the install wizard, which upgrades existing components. 2. Run the install wizard a second time and select the Modify option on the Program Maintenance page that appears after
you accept the Dell EULA. Only a single reboot of the host is required for either an upgrade or fresh install.
ImportKIT
The ImportKIT supports native multipath I/O for Dell EqualLogic, Compellent SC, and Unity, and Dell VNX2 systems and should be installed on all hosts that are part of the host cluster. Upgrade does not apply to this package since it is the first release of the package. Reboot of the host is required after installation.

26

Host plugin installation (block-based non-disruptive import only)

NOTE: It is recommended to use the .EXE version of the installer. The .MSI version of the installer is provided to support administrative installations. To use the .MSI file, see Pre-requisites for an install using the .MSI file.
Install the host plugin for import on a Windows-based host
Prerequisites Verify the following: A supported operating system is running on the host. See the PowerStore Simple Support Matrix document at https://
www.dell.com/powerstoredocs. No other multipath driver is installed on the host. Ensure that MPIO is enabled on the host.
NOTE: Configuring MPIO on the host during import is not supported.
Ensure you know the management IP address and associated port number to use for import. This network configuration information needs to be provided so that the host gets added to the PowerStore cluster for import.
About this task To install the host plugin, do the following:
NOTE: By default, the installation runs interactively. To run the installation in the background, accept all defaults, and accept the Dell EULA, enter one of the following commands after downloading the applicable host plugin package to the host. For ImportKIT, enter:
Setup64.exe /quiet /v/qn
For EQL HIT Kit with import capability, enter:
Setup64.exe /v”MIGSELECTION=1″ /s /v/qn V”/q ADDLOCAL=ALL /L C:setup.log
NOTE: To avoid application disruption when running the installation on a Windows Cluster, Hyper-V clusters for example, move the host out of the cluster (maintenance mode) before installing the host plugin. After installing the host plugin and rebooting, re-join the host to the cluster. The virtual machines running on the host should be moved out and moved back after the installation is complete. To avoid multiple reboots, the ImportKit or Dell EqualLogic HIT kit install can be planned and combined with any other operating system reboot task.
Steps 1. Download the applicable host plugin package to the host.
For Dell EqualLogic PS, download the Dell EqualLogic Host Integration Tools Kit from the Dell EqualLogic support site https://eqlsupport.dell.com. For Dell EqualLogic, Compellent SC, or Unity, or Dell VNX2 systems, download the ImportKIT from the Dell Technologies Support site, https://www.dell.com/support. See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs for the applicable host multipath software versions. 2. As administrator, run Setup64.exe for the host plugin.
NOTE: For Dell EQL HIT Kit, ensure the Host Integration Tools installation (with import capability) option is selected on the Installation Type Selection page. Also, adding or removing additional components to an already installed Dell EQL HIT Kit version is not supported.
3. Reboot the host. A reboot of the host is required to complete the installation.

Host plugin installation (block-based non-disruptive import only)

27

Upgrade the host plugin for import on a Windows-based host
Prerequisites Verify the host is running an applicable version of the Windows operating system. See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs. Also, ensure you know the management IP address and associated port number to use for import. This network configuration information needs to be provided so that the host is added to the PowerStore cluster for import.
About this task To upgrade the EQL HIT Kit host plugin for Windows, do the following:
NOTE: By default, the upgrade runs interactively. To run the upgrade of the EQL HIT Kit in the background, enter the following command after downloading the host plugin update package to the host:
Setup64.exe /v”MIGSELECTION=1″ /s /v/qn /V”/q ADDLOCAL=ALL /L C:setup.log
NOTE: To avoid application disruption when running the installation on a Windows Cluster, Hyper-V clusters for example, move the host out of the cluster (maintenance mode) before installing the host plugin. After installing the host plugin and rebooting, re-join the host to the cluster. The virtual machines running on the host should be moved out and moved back after the installation is complete. To avoid multiple reboots, the ImportKit or Dell EqualLogic HIT kit install can be planned and combined with any other operating system reboot task.
Steps 1. Download the host plugin package update for the Dell EQL HIT Kit to the host from the Dell EqualLogic support site https://
eqlsupport.dell.com. 2. As administrator, run Setup64.exe for the host plugin.
NOTE: This install upgrades the existing HIT/ME components.
3. As administrator, run the install wizard for the host plugin again. Select the Modify option on the Program Maintenance page that appears after you accept the Dell EULA. NOTE: Ensure the Host Integration Tools installation (with import capability) option is selected on the Installation Type Selection page. If the Dell EQL HIT Kit is installed with import capability, adding or removing additional components to an already installed Dell EQL HIT Kit version is not supported.
4. Reboot the host. A reboot of the host is required to complete the installation.
Pre-requisites for an install using the .MSI file
The .MSI file must be run with an elevated command prompt, that is, run as Administrator. The following are the pre-requisites for .MSI installation for ImportKit and Equallogic HIT Kit: Microsoft Visual C++ runtime redistributable 2015 x64 Microsoft Native MPIO is installed. Microsoft .Net 4.0 is installed.
Installing the host plugin for import on a Linux-based host
See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs for a list of the supported source systems and operating environments that are applicable to a Linux-based host.

28

Host plugin installation (block-based non-disruptive import only)

NOTE: Installing the DellEMC-PowerStore-Import-Plugin-for-Linux kit does not require a host reboot and it does not impact ongoing I/O operations.
Install the host plugin for import on a Linux-based host
Prerequisites Verify the following on the host: Open-iscsi (iscsid) is installed and running.
NOTE: This process is optional in a fibre channel environment. sg_utils package is installed. For DellEMC-PowerStore-Import-Plugin-for-Linux kit, multipathd is running.
NOTE: Ensure you know the host server port number, host iSCSI IP address that will be used to reach the PowerStore cluster, and the host management IP address. This information must be provided during the host plugin installation. NOTE: Import to PowerStore 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 for more details.
About this task To install the DellEMC-PowerStore-Import-Plugin-for-Linux kit, do the following:
NOTE: For information about installing the EQL HIT Kit host plugin, see the Dell EqualLogic Host Integration Tools for Linux Installation and User’s Guide.
Steps 1. Download the host plugin package, DellEMC-PowerStore-Import-Plugin- for-Linux-.iso, and the associated
file for the GNU Privacy Guard (GPG) key to a temporary directory, such as /temp, from the Dell download site at: https:// www.dell.com/support 2. Copy the downloaded GPG key file and install it. For example,

rpm –import

NOTE: The GPG key is required to install the host plugin and must be installed on the host before attempting to install the host plugin.
3. Run the mount command for the host plugin. For example, #mount DellEMC- PowerStore-Import-Plugin-for-Linux-.iso /mnt
4. Change to the /mnt directory. For example,

cd /mnt

5. View the items in the /mnt directory for minstall. For example,

ls EULA LICENSES minstall packages README support

6. Install the host plugin.

Host plugin installation (block-based non-disruptive import only)

29

For example, #./minstall
NOTE: By default, the installation runs interactively. To run the installation in the background instead, accept all defaults, and accept the Dell EULA, then enter the following command after downloading the host plugin package to the host and installing the certificate key:

./mnt/minstall –noninteractive –accepted-EULA –fcprotocol (or

-iscsiprotocol) –adapter=
Where ip_address = subnet IP address for MPIO. Failing to provide the –accepted-EULA option aborts a noninteractive installation. Also, the port for the host or hosts is set to 8443 by default. NOTE: If a firewall exists, ensure it is enabled to allow the port for the host or hosts to be open. For example:

sudo firewall-cmd –zone=public –add-port=8443/tcp

Upgrade the host plugin for import on a Linux-based host
Prerequisites Verify the following on the host: Open-iscsi (iscsid) is installed and running.
NOTE: This process is optional in a fibre channel environment. GPG key has been installed. EqualLogic HIT Kit is running.
About this task NOTE: The upgrade of the EQL HIT Kit host plugin for Linux is pertinent only for import of external storage from the Dell EqualLogic PS version that is listed in the PowerStore Simple Support Matrix document at https://www.dell.com/ powerstoredocs.
To upgrade the EQL HIT Kit host plugin, do the following:
Steps 1. Download the host plugin package, equallogic-host-tools-<latest version>.iso, to a temporary directory, such as /temp, from
the Dell EqualLogic support site https://eqlsupport.dell.com. 2. Run the mount command for the host plugin.
For example, #mount equallogic-host-tools-.iso /mnt
3. Change to the /mnt directory. For example, #cd /mnt
4. View the items in the ./mnt directory for install. For example, #ls EULA install LICENSES packages README support welcome-to-HIT.pdf

30

Host plugin installation (block-based non-disruptive import only)

Install the host plugin

./install

NOTE: By default, the installation runs interactively. To run the installation in the background instead, see the latest version of the Dell EqualLogic Host Integration Tools for Linux Installation and User’s Guide.
Installing the Dell EqualLogic MEM kit on an ESXibased host
The following methods exist to install the Dell EqualLogic Multipathing Extension Module (MEM) kit on an ESXi host: Command line installation using esxcli commands Installation using install script on vSphere Management Assistant (VMA) or vSphere Command-Line Interface (VCLI) Installation using VMware Upgrade Manager (VUM) The kit and the associated user guide can be downloaded from the Dell EqualLogic support site https://eqlsupport.dell.com. For the supported versions of Dell EqualLogic Peer Storage (PS) source system and Dell EqualLogic MEM kit, see the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs. The following configurations are supported: Virtual machine file system (VMFS) datastores Raw device mapping (RDM) ­ Windows RDM
Clustering Microsoft Clustering Service (MSCS) virtual machines on a single host Clustering virtual machines across physical hosts NOTE: Linux RDM configurations are not supported.
Install the Dell EqualLogic MEM kit on an ESXi-based host using the vSphere CLI
Prerequisites Verify that the supported VMware ESXi software is installed and running. See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs.
About this task NOTE: To avoid application disruption, move the ESXi host out of the cluster before installing the host plugin. After installing the host plugin and rebooting, re-join the ESXi host with the cluster. Virtual machines should be moved out from the installing host and moved back after the install. Also, to avoid multiple reboots, the Dell EqualLogic MEM kit install can be planned and combined with any other operating system reboot task.
To install the supported Dell EqualLogic MEM kit (see the PowerStore Simple Support Matrix document at https:// www.dell.com/powerstoredocs), do the following:
NOTE: To enable only MEM functionality, execute only steps 1, 2 and 6.
Steps 1. Download the latest version of the Dell EqualLogic MEM kit and associated installation guide from the Dell EqualLogic
support site https://eqlsupport.dell.com. After login, the kit and its associated installation guide can be found under downloads for VMware Integration. 2. Run the install command.

Host plugin installation (block-based non-disruptive import only)

31

For example,

esxcli software vib install -­depot /var/tmp/dell-eql-mem-esx6-<latest

version>.zip
The following message appears:
Operation finished successfully. Reboot Required: true VIBs Installed: DellEMC_bootbank_dellemc-import-hostagent-provider_1.0-14112019.110359, DellEMC_bootbank_dellemc-import-satp_1.0-14112019.110359 VIBs Removed: VIBs Skipped: 3. Stop hostd. For example,

/etc/init.d/hostd stop Terminating watchdog process with PID 67143 hostd

stopped.
4. Start hostd. For example,

/etc/init.d/hostd start

hostd started. 5. Add import command rules.
For example,

esxcli import equalRule add

After adding the SATP rules, they can be listed by running the list command. For example,

esxcli import equalRule list

DellEMC_IMPORT_SATP EQLOGIC 100E-00 user VMW_PSP_RR All EQL Arrays DellEMC_IMPORT_SATP DellEMC PowerStore user VMW_PSP_RR iops=1 All PowerStore Arrays 6. Reboot the system.
NOTE: The system must be rebooted before the Dell EqualLogic Multipathing Extension Module with import becomes active.
Install the Dell EqualLogic MEM kit on an ESXi-based host using setup.pl script on VMA
Prerequisites Verify that the supported VMware ESXi software is installed and running. See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs.
About this task NOTE: To avoid application disruption, move the ESXi host out of the cluster before installing the host plugin. After installing the host plugin and rebooting, re-join the ESXi host with the cluster. Virtual machines should be moved out from the installing host and moved back after the install. Also, to avoid multiple reboots, the Dell EqualLogic MEM kit install can be planned and combined with any other OS reboot task.
To install the supported Dell EqualLogic MEM kit (see the PowerStore Simple Support Matrix document at https:// www.dell.com/powerstoredocs), do the following:
NOTE: To enable only MEM functionality, in step 3 when prompted for import, respond with no.

32

Host plugin installation (block-based non-disruptive import only)

Steps 1. Download the latest version of the Dell EqualLogic MEM kit and associated installation guide from the Dell EqualLogic
support site https://eqlsupport.dell.com. After login, the kit and its associated installation guide can be found under downloads for VMware Integration. 2. Run the setup.pl script command on VMA. The script prompts to install the bundle, then it prompts to enable import. The command uses the following format: ./setup.pl -install –server –username <user name> –password –bundle . For example,
./setup.pl -install –server 10.118.186.64 –username root –password my$1234 -bundle /dell-eql-mem-esx6-.zip
The following message appears:
Clean install of Dell EqualLogic Multipathing Extension Module. Before install_package call Bundle being installed: /home/vi-admin/myName/dell-eql- mem-esx6-.zip Copying /home/dell-eqlmem-esx6-<latest version>.zip Do you wish to install the bundle [yes]:
3. Type yes to continue. The following message appears:
The install operation may take several minutes. Please do not interrupt it. Do you wish to enable import? Enabling import would claim all PS and PowerStore volumes by IMPORT SATP and changes the PSP to VMW_PSP_RR [yes]:
4. Type yes to continue. The following message appears:
Enabling import functionality. In add_claim_rules Clean install was successful.
5. Reboot the system. NOTE: The system must be rebooted before the Dell EqualLogic Multipathing Extension Module with import becomes active.
Install the Dell EqualLogic MEM kit on an ESXi-based host using VUM
Prerequisites Verify that the VMware vSphere Upgrade Manager (VUM) is installed on the host. See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs for the supported MEM kit to install.
About this task To install the supported MEM kit, do the following:
Steps 1. Follow the instructions in the VMware documentation to install the supported MEM kit using the VUM method. 2. After the MEM kit is installed, but before rebooting, do the following on all the hosts where the MEM kit is installed:
a. Stop hostd.

Host plugin installation (block-based non-disruptive import only)

33

For example:

/etc/init.d/hostd stop Terminating watchdog process with PID 67143 hostd

stopped.
b. Start hostd. For example:

/etc/init.d/hostd start hostd started.

c. Add import command rules. For example:

esxcli import equalRule add

3. Reboot the system. NOTE: The system must be rebooted before the Dell EqualLogic Multipathing Extension Module with import becomes active.
Install the Dell EqualLogic MEM kit during an ESXi-based host upgrade
Prerequisites Verify whether a version earlier than the supported VMware ESXi software is running on the host. See the PowerStore Simple Support Matrix document at https://www.dell.com/powerstoredocs.
About this task To install the supported MEM kit (see the PowerStore Simple Support Matrix document at https://www.dell.com/ powerstoredocs) during an upgrade of an earlier version of VMware ESXi software and to avoid multiple reboots, do the following:
Steps 1. Upgrade to the supported VMware ESXi software, but do not reboot the ESXi host. 2. Use one of the following methods to install the supported MEM kit on the prior version of the VMware ESXi software, apply
SATP rules, and skip the reboot step in the following methods: Install MEM Using the vSphere CLI Install the Dell EqualLogic MEM kit on an ESXi-based host using the vSphere CLI Install the Dell EqualLogic MEM kit on an ESXi- based host using setup.pl script on VMA Install the Dell EqualLogic MEM
kit on an ESXi-based host using setup.pl script on VMA Install the Dell EqualLogic MEM kit on an ESXi-based host using VUM Install the Dell EqualLogic MEM kit on an
ESXi-based host using VUM 3. Reboot the host.
NOTE: The system must be rebooted before the Dell EqualLogic Multipathing Extension Module with import becomes active.
Uninstalling the host plugin for import
Uninstalling any of the host plugin software for import is not recommended since it involves host or application down-time and VM/volume re-configuration in some cases. If a host plugin must be uninstalled, contact your service provider.

34

Host plugin installation (block-based non-disruptive import only)

4
Import workflows
This chapter contains the following information:
Topics:
· Non-disruptive import workflow · Cutover workflow for non-disruptive import · Cancel workflow for non-disruptive import · Agentless import workflow · Cutover workflow for agentless import · Cancel workflow for agentless import · File-based import workflow · Cutover workflow for file-based import · Cancel workflow for file-based import
Non-disruptive import workflow
As part of the import process, the source volume or consistency group is pre- validated whether it is ready to be imported. An import session is not allowed when either a non-disruptive upgrade or a network reconfiguration is in progress.
NOTE: Only source volumes and consistency groups that have a status of Ready for Import, System cannot determine cluster type, or All hosts have not been added can be imported.
The following steps show the manual import workflow in PowerStore Manager: 1. If the source system does not appear in PowerStore Manager, add the information needed to discover and access the
source system. NOTE: (For importing storage from a Dell EqualLogic PS series system only) After you attempt to add a PS series system to PowerStore, the initial data connection state will appear as No Targets Discovered. However, you can proceed to create the import session and the state will be updated to OK after the import session moves to the In Progress state. This behavior is only specific to a PS series system and it is expected.
NOTE: If PowerStore discovery of PowerMax as a remote system fails with an internal error (0xE030100B000C), see the Knowledge Base Article 000200002, PowerStore: Discovery of PowerMax as a remote system fails with an Internal Error (0xE030100B000C). 2. Select the volumes or consistency groups, or both to import. 3. (Optional) Assign selected volumes to a PowerStore Volume Group. 4. Select Add hosts (Host Plugin) for non-disruptive import and add the information needed to discover and access the host systems. 5. Set the schedule for the import. 6. (Optional) Assign a protection policy for the import sessions. 7. Review the summary of the import configuration information for accuracy and completeness. 8. Begin the import. NOTE: The active I/O path between the host and the source system becomes passive and the passive I/O path between the host and the PowerStore cluster becomes active. Also, the background copy of the selected source volumes to the associated PowerStore volumes begins as well as the forwarding of host I/O from the PowerStore cluster to the source system.
You can cutover an import after the background copy operation is complete. After cutover, the source volume is no longer accessible to the associated hosts and the PowerStore cluster. The states of a single volume import and the manual operations that are allowed for those states are as follows:

Import workflows

35

Queued state ­ Cancel operation Scheduled state ­ Cancel operation Copy-In- Progress state ­ Cancel and Pause operations Paused state ­ Cancel and Resume operations Ready-For-Cutover state ­ Cancel and Cutover operations Cleanup- Required state ­ Cleanup operation Import-Completed state ­ No manual operations available
The states of a consistency group import and the manual operations that are allowed for those states are as follows:
Queued state ­ Cancel operation Scheduled state ­ Cancel operation In-Progress state ­ Cancel operation
NOTE: Once the first volume of a CG is picked up for import, the CG state changes to In-Progress. The CG remains in that state until it reaches Ready- For-Cutover. Ready-For-Cutover state ­ Cancel and Cutover operations Cleanup- Required state ­ Cleanup operation Cleanup-In-Progress state ­ No manual operations available Cancel-In-Progress state ­ No manual operations available Cancel-failed ­ Cancel operation Cutover-In-Progress state ­ No manual operations available Import-Cutover-Incomplete state ­ Cancel and Cutover operations Import-Completed-With-Errors ­ No manual operations available Import-Completed ­ No manual operations available Failed ­ Cancel operation
When an import session is paused, only the background copy is stopped. The forwarding of host I/O to the source system continues to be active on the PowerStore cluster.
NOTE: Any I/O failures or network outages can cause import to fail during any of the states.
When a paused import session is resumed, the following occurs:
For volumes, the import session state changes to Copy-In-Progress. For consistency groups, the state changes to InProgress.
The background copy restarts from the last copied range. The forwarding of host I/O to the source system continues to be active on the PowerStore cluster.
If an import session fails, the Orchestrator tries to automatically cancel the import operation to restore host I/O back to the source. If a cancel operation fails, the orchestrator will attempt to continue host I/O to the PowerStore cluster. If a catastrophic failure should occur and host I/O cannot continue, the import session state changes to Cleanup-Required. In this state you can run the Cleanup operation, which is specific to the source system. This action sets the source storage resource to Normal and deletes the associated destination storage resource.
Cutover workflow for non-disruptive import
You can cutover an import when the import session reaches the Ready For Cutover state. After cutover, the source volume, LUN, or consistency group is no longer accessible to the associated hosts and the PowerStore cluster.
The following steps show the manual import workflow in PowerStore Manager:
1. Select the import session to cutover. 2. Select the Cutover import action to cutover to the PowerStore cluster. The following cutover processing occurs:
a. Forwarding of host I/O from the PowerStore cluster to the source system stops. b. The volume or volume group status updates to Import Complete upon successful cutover.
NOTE: When all the volumes in a volume group are cutover successfully, the state of the import session is set to Import Complete. However, since the status of the volume group depends on the final status of the member volumes, if one or more of the member volumes are in a state other than Import Complete, the status of the volume group is set to Cutover_Failed. Repeat the cutover operation again until it succeeds and the status for the volume group becomes Import Complete. c. Hosts and PowerStore cluster access to the source volume, LUN, or consistency group is removed.

36

Import workflows

NOTE: Import sessions are not deleted. If you want to delete the import session, use the delete operation that is available only through the REST API. For more information about the REST API, see the PowerStore REST API Reference Guide.
Cancel workflow for non-disruptive import
You can cancel an import session that is in any one of the following states: Queued Scheduled For volume, Copy-in-Progress or, for CG, In-Progress Paused Ready-for-Cutover For CG, Import-Cutover-Incomplete For CG, Cancel-Required For CG, Cancel-Failed For CG, Failed The cancel operation sets the state of the import session to CANCELLED and disables access to the destination volume or volume group. It also deletes the destination volume or volume group associated with the import session.
NOTE: After an import session is successfully cancelled, wait five minutes before retrying to import the same volume or consistency group. If you retry the import immediately after the successful cancel operation, the import may fail.
NOTE: A Force Stop option is provided in the confirmation popup for Cancel in the case of either a source system or a host is down. Selecting this option terminates the import session without rolling back access to the volumes on the source system. Manual intervention may be required on the source system or host, or both.
The following steps show the manual cancel workflow in PowerStore Manager: 1. Select the import session to cancel. 2. Select the Cancel import action to cancel the import session. 3. Click CANCEL THE IMPORT in the pop up screen. The following cancel processing occurs:
a. The destination volume is disabled. b. The source volume is enabled. c. The state of the import session is set to CANCELLED on the successful completion of the operation.
NOTE: When all the volumes in a volume group are cancelled successfully, the state of the import session is set to CANCELLED. However, since the status of the volume group is dependent on the final status of the member volumes, if one or more of the member volumes are in a state other than CANCELLED, the status of the volume group is set to Cancel_Failed. You must repeat the cancel operation again until it succeeds and the status for the volume group becomes CANCELLED. d. The destination volume is deleted. NOTE: Import sessions are not deleted but can be deleted through the REST API.
Agentless import workflow
As part of the import process, the source volume or LUN, or consistency group or storage group is pre-validated whether it is ready to be imported. An import session is not allowed when either a non-disruptive upgrade or a network reconfiguration is in progress.
NOTE: Source volumes and consistency groups can reflect a different status for import that depends on the method of import and the operating environment running on your source system. Storage group, which is a collection of volumes, is the basic unit of storage provisioned in a Dell PowerMax or VMAX3 system. Only storage groups can be imported from Dell PowerMax or VMAX3 systems; individual volumes cannot be imported. Only LUNs can be imported from NetApp AFF or A Series systems, consistency group is not available in ONTAP. The Ready for Agentless Import status is applicable only when the version of the source system is earlier than the
version that is supported for non-disruptive import.

Import workflows

37

If the version of the source system supports non-disruptive import but the host plugin is not installed, volumes or consistency group member volumes will have the status of The host or host(s) have not been added.. In such cases, you can choose to do either a non-disruptive or an agentless import. Depending on the type of import you choose, you need to do one of the following: For a non-disruptive import, install the host plugin. For an agentless import, under Compute > Host Information > Host & Host Groups, select Add Host as needed and specify the relevant information for the hosts.
The following steps show the manual import workflow in PowerStore Manager:
1. If the host or hosts do not appear in PowerStore Manager, add the information needed to discover and access the hosts. 2. If the remote (source) system does not appear in PowerStore Manager, add the information needed to discover and access
the source system. NOTE: (For importing storage from a Dell EqualLogic PS series system only) After you attempt to add a PS series system to PowerStore, the initial data connection state will appear as No Targets Discovered. However, you can proceed to create the import session and the state will be updated to OK after the import session moves to the In Progress state. This behavior is only specific to a PS series system and it is expected. (For importing storage from a NetApp AFF or A Series system only) A data SVM can be added as a remote system in PowerStore. Also, multiple data SVMs from the same NetApp cluster can be added to PowerStore for import. (For importing storage from a Dell PowerMax or VMAX3 system only) Symmetrix is the legacy name of the Dell VMAX family and the Symmetrix ID is the unique identifier of the PowerMax or VMAX system. Multiple PowerMax or VMAX3 systems that are managed by the same Unisphere can be added to PowerStore for import.
NOTE: If PowerStore discovery of PowerMax as a remote system fails with an internal error (0xE030100B000C), see the Knowledge Base Article 000200002, PowerStore: Discovery of PowerMax as a remote system fails with an Internal Error (0xE030100B000C). 3. Select the volumes, or consistency groups, or both, or LUN, or storage group to import. NOTE: An XtremIO source volume is assigned a World Wide Name (WWN) when it is mapped to a host. Only such volumes with a WWN are discovered by PowerStore for import. 4. (Optional) Assign selected volumes to a PowerStore Volume Group. 5. Select Map to hosts on PowerStore for agentless import and map the applicable PowerStore Manager host or hosts to the source volumes or LUNs. NOTE: (Optional) Volumes within a consistency group can be mapped individually to different hosts.
6. Set the schedule for the import. 7. (Optional) Assign a protection policy for the import sessions. 8. Review the summary of the import configuration information for accuracy and completeness. 9. Submit the import job.
NOTE: Volumes are created on PowerStore Manager and access functions are set up for the source system so that data can be copied from the source volume or LUN to the destination volume. 10. After the destination volumes reach the Ready To Enable Destination Volume state, shut down the host application accessing the associated source volume, LUN, consistency group, or storage group. 11. Select and

References

• Log on as a service - Windows 10 | Microsoft Learn

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>