The detailed specifications of data migration are as follows:
|
Item |
Specifications |
||
|---|---|---|---|
|
Data migration destination storage node |
A storage node with sufficient free capacity for the user data of the Azure managed disks to be migrated is automatically selected. |
||
|
Maximum number of Azure managed disks that can be migrated simultaneously |
31 |
||
|
Number of Azure managed disks that can be migrated in the external storage |
|
||
|
Minimum capacity of one Azure managed disk of the external storage that can be migrated1 |
Premium SSD v2: 1GiB Premium SSD: 4GiB Standard SSD: 4GiB |
||
|
Maximum capacity of one Azure managed disk of the external storage that can be migrated1 |
Premium SSD v2: 64TiB Premium SSD: 32TiB Standard SSD: 32TiB |
||
|
Number of initiator nodes required for migration |
1 |
||
|
Connection configuration |
Supported Azure managed disk type |
Premium SSD v22, Premium SSD, Standard SSD |
|
|
|||
Only one initiator node can be added to VSP One SDS Block. If more than one initiator node is added to VSP One SDS Block, data copy in step 2 in Performing data copy might not be successful.
When performing data migration, do not add storage nodes. Adding storage nodes increases internode network usage and load on storage nodes which might degrade data copy performance. Capacity balancing also degrades the data copy performance. Disable capacity balancing, as required. For how to disable capacity balancing, see Editing capacity balance settings for storage nodes in the VSP One SDS Block and SDS Cloud System Administration.