Connect the external storage system to the ETERNUS DX (local storage system) directly or via a switch. After a
connection is established, prepare for the data migration.
Create External Drives in the local storage system. Create External RAID Groups using the External Drives and
then create volumes in the External RAID Groups. The volumes are called External Volumes in the local storage
system and they take over the information of the migration source volume in the external storage system. Set
host affinity to the External Volumes.
Add multipath connections between the local storage system and the business server. After disconnecting the
multipath connection between the external storage system and the business server, use RAID Migration to read
data from the migration target volume in the external storage system and write data to the migration
destination volume in the local storage system.
Data consistency is ensured because the data remains in the migration source volume for consolidated
management during the data migration.
Caution
•
Only FC ports (connected in the FC-Initiator mode) are supported for connections with external storage
systems.
•
The Non-disruptive Storage Migration License must be registered to use this function.
For details on the license, contact your sales representative.
•
Only data migrations from the external storage system to the local storage system is supported.
Data migrations from the local storage system to the external storage system or between external
storage systems is not supported.
•
The local storage system volume returns the same information (UID, vendor ID, and product ID) as the
External Volume even after a migration is completed.
•
Do not set the copy operation suppression, the cache parameters, and the Volume QoS for the External
Volume.
•
The functions that can be used for the External Volumes are delete, rename, and RAID migration. Other
functions cannot be used until the data migration is successfully completed.
•
Migration destination volumes in the local storage cannot be used for Storage Cluster even after the
migration is completed.
•
Make sure to delete the Non-disruptive Storage Migration License after the Non-disruptive Storage
Migration is complete.
3. SAN Functions
Non-disruptive Storage Migration
148
Design Guide
Содержание ETERNUS DX S5 Series
Страница 335: ......