You can use Volume Migration and Universal Volume Manager to migrate data between different storage systems.
The following figure shows the system configuration when data is migrated on VSP One Block Administrator.
For details about Volume Migration, see the Volume Migration User Guide. For details about Universal Volume Manager, see the Universal Volume Manager User Guide.
We recommend that you check the notes outlined in the Volume Migration User Guide before migrating data.
- There are restrictions on data migration using VSP One Block Administrator, which are
described below. See the description about UI support for key features in the System Administrator Guide and use the appropriate management tool.
- Data migration can be performed when the volume to be migrated (a volume on the external storage system) is 4 TiB or smaller. If you wish to migrate a volume exceeding 4 TiB, use another management tool.
- I/O to the server is suspended during the data migration process. If you wish to migrate data without suspending I/O to the server, use another management tool.
- If the migration destination pool is full, data migration based on Volume Migration will fail. Verify
that there is sufficient free space in the migration destination pool before migrating
data.
If the pool at the migration destination is full, the server might be prohibited from writing to volumes in the pool that is full.
Use an external path to connect the external storage system (the migration source storage system) and the migration destination storage system, and create external volumes on the migration destination storage system.
time-to-create-external-volumes (seconds) = number-of-external-volumes-to-be-created * {1 second + (number-of-paths-to-be-defined-for-an-external-volume - 1) * {2 seconds + number-of-paths-defined-for-the-storage-system * 0.025 seconds}}
Before migrating data, change the connection destination for the server from the migration source storage system to the migration destination storage system. When you perform data migration, migration pairs consisting of an external volume and a volume created from the migration destination pool will be created and volume copying will start.
When data migration is complete, the IDs of the external volumes and the IDs of the volumes created from the migration destination pool are swapped. The IDs of the volumes created as external volumes become the IDs of the volumes of the migration destination pool.
- During data migration, on the migration pairs inventory page, the Target Volume ID field displays the IDs of the volumes created from the migration destination pool and the Source Volume ID field displays the IDs of the external volumes.
- Once data migration is complete, on the migration pairs inventory page, the Target Volume ID field displays the IDs of the external volumes and the Source Volume ID field displays the IDs of the volumes created from the migration destination pool.
For details about the volume usage capacity after data migration, see the notes on using Dynamic Provisioning virtual volumes (including an explanation about usage rates) in the Volume Migration User Guide.
After deleting migration pairs, attach the volumes of the migration destination pool to the server. Delete the unnecessary external volumes.