Configure an agentless import for a Universal type remote system
Prerequisites
NOTE:The information that is presented here is only applicable to importing external storage to
PowerStore from a Universal type of remote system. For information about importing external storage to the following remote system types, see
Configure an agentless import.
Dell Peer Storage (PS) Series
Dell Storage Center (SC) Series
Dell Unity Series
Dell VNX2 Series
Dell XtremIO X1 or
Dell XtremIO X2
Dell PowerMax and VMAX3
NetApp AFF A-Series
Ensure that the following conditions exist on the
PowerStore cluster before running import:
The global storage IP address for the
PowerStore cluster is configured.
The
PowerStore cluster and its nodes are in a healthy state.
Ensure that the following connections exist:
For a Universal (either a legacy Dell EMC or third-party) source system, a Fibre Channel (FC) or iSCSI connection between the source system and each associated host system, and a matching FC or iSCSI connection between each associated host system and the
PowerStore cluster.
NOTE:These connections to each host system should be of the same type, either all FC or all iSCSI.
Either an iSCSI connection or an FC connection is supported between a Universal source system and the
PowerStore cluster.
NOTE:For an iSCSI connection, the purpose of the storage network that will be used for import must be set for both
Storage (iSCSI) and
Replication. You can set the purpose on the
Network Details step of the
Create Storage Network wizard (Settings > Network IPs
> Storage > Create ). To view the mapped storage networks of a port and their purposes, select
Hardware > Appliances > [appliance]
> Ports. See the
PowerStore Manager online help and the
PowerStore Protecting Your Data Guide for more information about creating a storage network and setting the purpose of a remote system.
NOTE:When the connections between the Universal source system and the
PowerStore cluster are all over iSCSI, the connections between the hosts and the Universal source system and between the hosts and the
PowerStore cluster can be either all over iSCSI or all over FC. However, when the connections between the Universal source system and the
PowerStore cluster are all over FC, the connections between the hosts and the Universal source system and between the hosts and the
PowerStore cluster must also be all over FC.
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).
For FC connections, it is recommended to configure FC zoning in such a way that
PowerStore can connect to at least two distinct targets on each remote system controller from a
PowerStore node.
It is recommended that the same NTP server is used on the source system, which hosts the source storage resource, and the destination
PowerStore cluster. This configuration should provide the proper time synchronization between the source system and the destination
PowerStore cluster.
Determine the following for the source system:
The type of source system that is selected for the import is
Universal.
The name of the source system
The management cluster IP address or FQDN. For type
Universal, see the documentation for the applicable remote system.
NOTE:PowerStore opens a new tab in the browser and uses this address to connect with the Universal remote system.
The data connection type, either iSCSI IP or fibre channel.
NOTE:For the IP address of the source system, see the documentation for the applicable remote system. Multiple IP addresses can be entered separated with a comma.
(For iSCSI IP only) The Discovery CHAP mode.
(For iSCSI IP only) The Session CHAP mode.
(For fibre channel only) The FC targets must be selected from those that are discovered.
The names of the volumes.
Which protection policy to use for the volume or volume group.
Determine which hosts should be mapped to the
PowerStore volumes.
Determine the schedule of the import:
Immediately or set a time and date.
NOTE: 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.
Whether to automatically cut over to the destination after import.
Determine which protection policy to assign to the import volume.
NOTE:The protection policy must already exist.
About this task
To configure an import, do the following:
Steps
Log in to
PowerStore Manager.
If the intended hosts that are associated with the import do not appear under
Compute > Host Information > Hosts & Host Groups, select
Add Host as needed and specify the relevant information for the hosts. Otherwise, go to the next step.
Under
Migration, select
Import External Storage.
The
Import External Storage page appears.
If the intended source system does not appear in the list of Remote Systems, select
Add Remote System and specify the relevant information for the remote system. Otherwise, go to the next step.
Verify that the IP address is correct and reachable.
NOTE:While adding a remote system to
PowerStore, you must provide the iSCSI IP address of the remote system along with other details. As part of the operation,
PowerStore discovers the iSCSI portal of the remote system and tries to log in to all the targets listed in that portal. If anyone of those targets is unreachable, the associated
Data Connection status appears as
Partial Data Connections Loss in
PowerStore Manager.
Create
PowerStore as a host on the remote system and do one of the following:
NOTE: When adding
PowerStore as a host on the remote system, specify the
PowerStore cluster name.
For iSCSI, specify the HBAs that
PowerStore will use to send I/O requests to the remote system.
NOTE:To view a list of the IQNs on the
PowerStore appliance in
PowerStore Manager, select the appliance under
Hardware, and then select
Ethernet on the
Ports card. If the column IQN is not visible, select the IQN column to be visible. Also only the IQNs that are related to the storage network (with
Replication purpose) that is used for import traffic must be added to the created host in the source system.
For FC, specify the WWNs that
PowerStore will use to send I/O requests to the remote system.
NOTE: Only the WWNs of FC ports that have
Import Capable as
Yes must be added to the created host in the source system. To view the list of the FC import capable ports on a
PowerStore appliance in
PowerStore Manager, select the appliance under
Hardware, and then select
Fibre Channel on the
Ports card.
NOTE: IQNs or WWNs from all the appliances of the
PowerStore cluster must be added to the created host in the source system. Ensure that all the
PowerStore initiators have an active connection or initiator path to the source system. The host setting in the source system must ensure that the volume or CG that is mapped to it is visible to all the initiators in the host.
Select the newly created
PowerStore host on the remote system and ensure that it is configured correctly.
NOTE:The host setting in the source system must ensure that the volume or CG that is mapped to it is visible to all the initiators in the host.
On the Universal remote system, map the volume or volumes to be imported to the
PowerStore appliance.
NOTE:Up to 128 volumes can be mapped to import to a
PowerStore cluster at one time. More or remaining volumes can be mapped and imported to
PowerStore after the current set of volumes are imported.
To configure an import session, select a source system from the list of remote systems on your network that you have previously entered manually in to
PowerStore Manager.
Select
Import Volume.
The
Import Volumes from Source Array wizard appears.
Select
Refresh Volumes to discover the volumes that have been mapped on the Universal remote system to the
PowerStore appliance.
Step through the wizard and specify the relevant information.
NOTE:Only source volumes that have a status of
Ready for Agentless Import can be imported.
NOTE:For a Universal source system, the name of the volumes appears as a dash (–) the first time after discovery. You must provide a name for the volumes before they can be selected for import. Select the applicable volumes, then select
Name Volume to update the name of the volumes. Up to 10 volumes at a time can be selected for naming. Click
Apply to update the list of volumes. The name should appear in place of the dash (–). After all the applicable volumes have been named, select those volumes again and click
Next to continue.
NOTE:Only volumes are discovered for a Universal type remote system. Consistency groups are not discovered. If a consistency group exists on the source system and should also exist on the destination,
PowerStore Manager provides options to create it and to add the applicable volumes to it. When a consistency group is created in this manner, a volume group is automatically created in place of the consistency group on
PowerStore during import. If you would like to group discovered individual volumes as a volume group when they are imported,
PowerStore Manager provides options to create the volume group and to add the applicable volumes to it.
Once you have specified the necessary information, the system generates a summary of the import session information.
Verify that the import session information in the summary is accurate and complete.
Click
Begin Import to create and start the import session.
The
Import External Storage page appears and shows the
Block Imports information once the operation is started.
After the destination volume reaches the Ready To Enable Destination Volume state, shut down the host application accessing the source volume.
When the volume in the import session is in the
Ready To Enable Destination Volume state, select the volume and then select
Import Actions > Enable Destination Volume.
The
Enable Destination Volume dialog box appears.
Select the checkbox to confirm that you have shut down or taken offline the host application that is using the source volume.
NOTE:It is recommended to manually remove the host mapping of the source volume during the enable destination volume process to prevent the host from accidentally accessing the source volume. If the host mappings of the source volume are not removed manually, those mappings remain even after cutover of the import session. Also, if import fails or is cancelled, those host mappings must be restored to the source volume manually. They are not restored automatically.
Select
Enable Destination Volume.
The volume should progress to the
Ready to start copy state.
When the import session changes to the Ready to start copy state, rescan the volumes at the host.
NOTE:The rescan at the host may take up to approximately 3 minutes to complete depending on the size of the volumes.
The destination volumes should be visible to the host after the rescan and those volumes can be mounted immediately.
Ensure that the host application has been reconfigured to access the applicable destination
PowerStore volumes, then bring up the host application.
When the volume in the import session is in the
Ready to start copy state, select the volume and then select
Import Actions > Start Copy.
The volume should progress to the
Copy in progress state.
To view the progress of ongoing import sessions, under
Migration, select
Imports.
To view the progress details of a specific ongoing import session, click the state of that import session.
The
Import Session Progress Details slide out for that import session appears.
Do one of the following to continue to manage the agentless import session:
Select an import session and under
Import Actions, click
Cutover to commit the import session.
NOTE:You can cut over an import session that is in the
Ready For Cutover state.