Migrate disks

Console

To migrate unattached disks by using the Google Cloud console, use the following steps.

1. Open the Migrate to Virtual Machines page in the Google Cloud console:

   Go to the Migrate to Virtual Machines page

2. Select the Sourcestab.

3. From the source drop-down list, select the migration source from which you want to migrate disks.

   Below the drop-down you see the Source statusof the migration source as follows:

   • Active: the source is active and connected to Migrate to Virtual Machines.
   • Offline: the source is unavailable.
   • Pending: the source is in the process of being connected and verified.

   If you don't see any entries in the drop-down list, it indicates that you haven't configured the migration source properly. Review the steps for your migration source settings and try again.

4. If the source is Active, the Source diskstab displays all the source disks in the migration source available for migration. Select one or more source disks.

5. Click Migration. The Create disk migrationspage appears.

6. Provide the details required for the disk migration. The following table describes these fields detail.

   Field name	Description
   Disk name	Enter a name for the migrated disk. For more information on the naming rules, see Naming convention .
   Target project	The target project in which you want to create the migrated disk. If you've not already added a target project, do so using the instructions given in Add a target project .
   Zone	Select the zone in which you want to create the migrated disk. See Regions and Zones .
   Disk type	Select the type of disk. See Persistent Disk types .
   Labels	To organize your project, add labels as key-value pairs to your resources. See Organize resources using labels .

7. You can now do one of the following:

   • Click Createto create the migration. Creating a migration only onboards the disk, however, the disk is not migrated yet. This migration appears in the Disk migrationstab. To run the migration, go to the Disk migrationstab, select the disk migration you want to run, and click Run.

   • Click Create and runto create the migration and start the migration immediately.

8. After the migration completes, the status of the migration is displayed in the Disk migrationstab.

gcloud

To migrate unattached disks by using the Google Cloud CLI, run the following command.

gcloud alpha compute migration disk-migrations create DISK_MIGRATION_JOB_NAME 
\
--source= AWS_SOURCE_NAME 
\
--source-volume-id= AWS_VOLUME_ID 
\
--location= REGION_ID 
\
--target-project= TARGET_PROJECT_RESOURCE_PATH 

Replace the following:

• DISK_MIGRATION_JOB_NAME : the name of the unnattached disk you want to migrate. For more information on the naming rules, see Naming convention .
• AWS_SOURCE_NAME : the AWS source from which you want to import the unnattached disk.
• AWS_VOLUME_ID : the ID of the AWS volume that you want to migrate to Google Cloud.
• REGION_ID : the region to which you want to migrate the unnattached disk to.
• TARGET_PROJECT : the target project to which you want to migrate the unnattached disk. If you've not already added a target project, do so using the instructions given in Add a target project .

For more information, see gcloud alpha compute migration disk-migrations create .

REST API

To migrate unattached by using the REST API, complete the following steps.

1. In the Cloud Shell terminal, define a shell alias for calling Google REST APIs:

   alias gcurl='curl -H "Authorization: Bearer $(gcloud auth print-access-token)" -H "Content-Type: application/json"'

2. Create a disk migration job using the following REST command:

   gcurl https://vmmigration.googleapis.com/v1alpha1/projects/ HOST_PROJECT 
   /locations/ LOCATION 
   /sources/ M2VM_SOURCE 
   /diskMigrationJobs/?disk_migration_job_id= DISK_MIGRATION_JOB 
   -X POST --data '{
   "aws_source_disk_details":{"volume_id":" AWS_VOLUME_ID 
   "},
   "target_details":{
     "target_disk":{
       "disk_id":" TARGET_DISK_ID 
   ",
       "zone":" TARGET_ZONE 
   ",
       "disk_type":" DISK_TYPE 
   "
     },
     "target_project":"projects/ HOST_PROJECT 
   /locations/global/targetProjects/ TARGET_PROJECT 
   ",
     "labels":{ CUSTOM_LABELS 
   },
     "encryption":{"kms_key":" KMS_KEY 
   "}
   }
   }'

   Replace the following:

   • HOST_PROJECT : the name of the host project in which you want to run the disk migration process.
   • LOCATION : the region in which you want the disk migration process to run. For a list of supported zones, see Regions and Zones .
   • M2VM_SOURCE : the cloud source from which you want to migrate the disks. Note that you can only migrate disks from AWS sources.
   • DISK_MIGRATION_JOB : the ID of the disk migration job. For information on naming convention for Compute Engine resources, see Naming conventions .
   • AWS_VOLUME_ID : the names of the disks that you want to migrate.
   • TARGET_DISK_ID : the ID of the target disk. For information on naming convention for Compute Engine resources, see Naming conventions .
   • TARGET_PROJECT : the ID of the target project to which you want to migrate the disks. If you've not already added a target project, do so using the instructions given in Add a target project .
   • TARGET_ZONE : zone of the target project. See Regions and Zones .
   • DISK_TYPE : the type of persistent disk that you want to migrate your disks to. Migrate to Virtual Machines supports the following disk types:
   • COMPUTE_ENGINE_DISK_TYPE_STANDARD : a Standard Persistent Disk.
   • COMPUTE_ENGINE_DISK_TYPE_SSD : a Performance Persistent Disk.
   • COMPUTE_ENGINE_DISK_TYPE_BALANCED : a Balanced Persistent Disk that balance performance and cost.
   • (Optional) CUSTOM_LABELS : any labels you want to give the migrated disk. For example, "key1":"val1", "key2":"val2" .
   • (Optional) KMS_KEY : the KMS key you want to use for the migrated disk. For more information, see Cloud Key Management Service overview .

3. (Optional) Update the target details. The target project is the project that contains the migrated disk. You can configure the target details including project, zone, and disk type based on your preferences. You can modify the target details at any time. You can use the command given in the previous step to update the target details as well.

   gcurl https://vmmigration.googleapis.com/v1alpha1/projects/ HOST_PROJECT 
   /locations/ LOCATION 
   /sources/ M2VM_SOURCE 
   /diskMigrationJobs/ DISK_MIGRATION_JOB 
   \?update_mask\=target_details  -X PATCH --data '{
   "target_details":{
    "target_disk":{
        "disk_id":" TARGET_DISK_ID 
   ",
        "zone":" TARGET_ZONE 
   ",
        "disk_type":" DISK_TYPE 
   "
      },
    "target_project":"projects/ HOST_PROJECT 
   /locations/global/targetProjects/ TARGET_PROJECT 
   ",
    "labels":{ CUSTOM_LABELS 
   },
    "encryption":{"kms_key":" KMS_KEY 
   "}
    }
   }'

4. Run the migration job by using the following REST command:

   gcurl https://vmmigration.googleapis.com/v1alpha1/projects/ HOST_PROJECT 
   /locations/ LOCATION 
   /sources/ M2VM_SOURCE 
   /diskMigrationJobs/ DISK_MIGRATION_JOB 
   :run -X POST

5. Poll the job to check its status by using the following REST command:

   gcurl https://vmmigration.googleapis.com/v1alpha1/projects/ HOST_PROJECT 
   /locations/ LOCATION 
   /sources/ M2VM_SOURCE 
   /diskMigrationJobs/ DISK_MIGRATION_JOB