- Notes, cautions, and warnings
- Additional Resources
- Introduction
- Import requirements and restrictions
- 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 A-Series specific requirements
- General block-based import restrictions
- General file-based import restrictions
- Host plugin installation (block-based non-disruptive import only)
- 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
- 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 VUM
- Install the Dell EqualLogic MEM kit during an ESXi-based host upgrade
- Uninstalling the host plugin for import
- Import workflows
- 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
- Configuring and managing import
- Configure a non-disruptive import
- Refresh hosts and volumes in a non-disruptive import
- Manage non-disruptive import sessions
- Configure an agentless import
- Configure an agentless import for a Universal type remote system
- Manage agentless import sessions
- Configure a File Mobility Network for file-based import
- Configure the connection to a remote system for file-based import
- Configure file import interface
- Configure a file-based import
- Manage file-based import sessions
- Import-CLI (Linux)
- Additional tasks related to import for Linux-based hosts
- ImportKit-CLI (Windows)
- How to run the ImportKit CLI commands
- List supported arrays
- Host plugin log information
- Import kit version
- Restart import kit host plugin service
- Import volumes information
- Get web server port information
- Install import kit certificate
- Regenerate the import kit certificate
- Set web server port information
- Set host plugin logging debug log level
- Import-CLI (VMware)
- CLI for EQL MPIO
- Fault handling by PowerStore import
Dell PowerStore Importing External Storage to PowerStore Guide
Import network overview
Import from source volume to PowerStore depends on several components. One of the most important components is network connections. These connections are:
- SAN path1: The front-end from the host to the PowerStore cluster. The PowerStore cluster is the destination and good and steady network connectivity from the host to the destination is mandatory. Both Fibre Channel (FC) and iSCSI are options for this segment and must be the same as what the host has towards the source system.
- SAN path2: The back-end from the PowerStore cluster to the source system. This connection is used for data transfer between the source volume and the PowerStore cluster. Here again, good and steady network connectivity is mandatory. Both Fibre Channel (FC) and iSCSI are options for this segment and must be the same as what the host has towards the source system and PowerStore cluster.
- SAN path3: The front-end connection from the host to the source system. For this segment, both FC and iSCSI are options and the protocol must be the same as what the host has towards the PowerStore cluster. This connection can be removed from the source system once all the volumes for this host have been imported.
- Control path1 (IP): PowerStore must have a management path connection to the source system for the management commands.
- (For non-disruptive import only) Control path2 (IP): The PowerStore cluster must have a management path connection to the host or hosts involved. The PowerStore cluster import orchestrator uses this connection to communicate with the host or hosts.
All these network connections must be established before starting the import and they must be working well for the import and cancel to be successful. Also, it is highly recommended that the connection from the PowerStore cluster to the source array be a high-speed network with redundant connections. Also, both systems should be within a short distance of each other to minimize network latency issues.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\