Detailed specifications

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 Google Cloud Hyperdisk to be migrated is automatically selected.
Maximum number of Google Cloud Hyperdisks that can be migrated simultaneously		31
Number of Google Cloud Hyperdisks that can be migrated in the external storage		Single-redundancy configuration: Value obtained by the number of storage nodes (excluding the initiator node) × 1,024 Double-redundancy configuration: A value whichever is smaller is applied. Value obtained by the number of storage nodes (excluding the initiator node) × 1,024 16,384
Minimum capacity of one Google Cloud Hyperdisk of the external storage that can be migrated^*		4 GiB
Maximum capacity of one Google Cloud Hyperdisk of the external storage that can be migrated^*		64 TiB
Number of initiator nodes required for migration		1
Connection configuration	Supported Google Cloud Hyperdisk type	hd-balanced
* For details about Google Cloud Hyperdisk volume types, see the following website. https://cloud.google.com/compute/docs/disks

CAUTION:

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.

Tip:

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.