Ensure the following conditions exist on the
PowerStore cluster before running a file import:
The global storage IP address for the
PowerStore cluster is configured.
The
PowerStore cluster and its nodes are in a healthy state.
Ensure the following on the source system:
The source storage system has been added to the
PowerStore configuration before creating a file import session.
NOTE:The basic configuration (NAS server name, file systems, production interfaces) of the source file server must not change after the file import session is created.
The source VNX VDM or Unity NAS server has at least one client network interface, and exactly one attached network interface named
nas_migration_<name>, where
<name> is a unique name provided to the interface, such as
nas_migration_vdm2.
NOTE:The
PowerStore import application uses this interface throughout the migration. This interface must be added to the CIFS Server in a separate subdomain to ensure that any hosts querying the DNS will not be directed to the migration interface. The VDM or NAS server must contain only a single CIFS Server and no NFS exports and there can be no host access on the NAS migration interface.
There can be no host access on the NAS migration interface. Either disable SMB2 Multi-channel feature, or add the NAS migration interface into a separate subnet.
For import from a VNX2 system, verify that the physical Data Mover on which the source VDM is located has at least one IP Interface configured that is not attached to the VDM being migrated. This verification ensures that the source Data Mover can provide uninterrupted Name Services for the remaining file servers. The file import session will fail if this additional interface is not present.
For import from either a Unified Unity or VNX2 source system, you must update the parameter
acl.extacl to
28 (default setting is 0) on the applicable source system before importing an SMB NAS server (CIFS server) to a
PowerStore appliance.
NOTE: Do one of the following on the source system:
For more information about modifying an adjustable VNX server parameter, see the
VNX Series Parameters Guide for VNX for File.
If the remote system needs to be added during the configuration, determine whether an iSCSI connection or a FC connection will exist between the
Dell VNX2 or Unity source system and the
PowerStore cluster.
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 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 cutover to the destination after import
For importing FLR enabled file systems, determine the administrative username and password credentials to access the source DHSM.
Determine which file import interface to use for the import.
NOTE:If the file import interface does not exist, you can create it while creating the import session.
Determine which protection policy to assign to the VDM or NAS server to be imported.
About this task
To configure a file-based import, do the following:
Steps
Log in to
PowerStore Manager.
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 (also known as the import connection). Otherwise, go to the next step.
To configure a file-based 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 NAS Server.
The
Import NAS Servers from Source Array wizard appears.
Step through the wizard and specify the relevant information.
NOTE:Only source VDMs or NAS servers that have a status of
Ready can be imported.
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
Ok.
NOTE: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. 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. Sometimes ongoing operations on the source system can cause some queued import sessions that become active to fail. In these cases, wait a few minutes and try the import again.
NOTE:When importing several VDMs or NAS servers at the same time, if anyone of those VDMs or NAS servers is not configured correctly and causes an IP address conflict, the import session for that VDM or NAS server will fail and may cause another of those VDM or NAS server import sessions to fail. You must resolve the VDM or NAS server IP address conflict to complete the import.
The VDM or NAS server should progress to the
Ready For Cutover state.
To view the progress of ongoing file import sessions, under
Migration select
Import External Storage and then select
File Imports.
NOTE: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.
Data is not available for the Topic
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: <>()\