How to return a Data Transport II device and verify data-Data Transport(Data Transport)-阿里云帮助中心

Prerequisites

You have successfully migrated data to the Data Transport II device, stopped the migration task, and powered off the device.

Return the device

1. Confirm the task status

Run the following commands to confirm the task status is succeed and that the data passes CRC64 verification against the source files.

Run cdmgwclient to enter the directory.
Run bash console.sh status <job_name> to check the task status. Replace <job_name> with the actual task name.

2. Stop the migration service

Important

You must run the following command only after the migration is complete. Otherwise, the migrated data may be incomplete. Do not forcibly power off the device.

Run the following command to stop the migration service.

beforepoweroff

3. Unmount and lock the storage pool

Run the following command to unmount and lock the storage pool.

crypt close

4. Power off the device

Run the poweroff command to power off the device.

5. Check the accessories

Verify that two optical modules are present on the 10G optical port.
Verify that two optical modules are present on the 25G optical port.
Confirm that the power cords are stowed in the compartment at the top of the chassis.
Hand over the Data Transport II device to an Alibaba Cloud logistics partner.

Cloud migration and verification

Grant RAM role permissions

Alibaba Cloud uses a specific RAM role to upload the data from the Data Transport II device to your specified OSS bucket. You must grant permissions to this RAM role.

Important

To prevent accidental permission loss, ensure the new policy includes all existing permissions.

Log on to the OSS console.
In the left-side navigation pane, click Buckets. On the page that appears, click the name of the destination bucket.
In the left-side navigation pane, choose Permission Control > Bucket Policy.
In the Add by Syntax section, add a custom Bucket Policy and click Edit, then Save.
- Grants the RAM role permissions to list, read, delete, and write all resources in this bucket.

Note

The following policy is an example. Replace the placeholders with actual values. Do not include the angle brackets (<>) when you replace the placeholders. The following table describes the parameters.

<mybucket>: your destination bucket name.
<myuid>: the Alibaba Cloud account UID that owns the destination bucket.

You need to replace only the preceding parameters. The sample policy already includes the required RAM role details (UID: 1737441177608761 and RAM role name: mgw-data-transport-role). For more information about OSS permission policies, see Common examples of RAM policies.

{
  "Version": "1",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "oss:List*",
        "oss:Get*",
        "oss:Put*",
        "oss:AbortMultipartUpload"
      ],
      "Principal": [
         "arn:sts::1737441177608761:assumed-role/mgw-data-transport-role/*"
      ],
      "Resource": [
        "acs:oss:*:<myuid>:<mybucket>",
        "acs:oss:*:<myuid>:<mybucket>/*"
      ]
    }
  ]
}

Cloud migration

Alibaba Cloud personnel use the authorized RAM role to migrate data from the Data Transport II device to the cloud. After the data is migrated, Alibaba Cloud personnel will notify you and provide the data migration report, which you can use for data verification.

Important

After the migration is complete, the generated data migration report is stored in your specified OSS bucket. For more information, see the Data migration report section.

Data migration report

The data migration report is saved to your specified OSS bucket. The report files are located at the following paths:

OSS://<bucket>/<prefix>/aliyun_import_report/<uid>/<jobid>/<runtimeid>/total_list/
OSS://<bucket>/<prefix>/aliyun_import_report/<uid>/<jobid>/<runtimeid>/failed_list/
OSS://<bucket>/<prefix>/aliyun_import_report/<uid>/<jobid>/<runtimeid>/skipped_list/

Parameter	Description
bucket	Your specified OSS bucket.
prefix	The prefix of the destination directory in your OSS bucket.
uid	The UID provided by Alibaba Cloud personnel: 1737441177608761.
jobid	The task ID provided by Alibaba Cloud personnel.
runtimeid	The task execution record ID provided by Alibaba Cloud personnel.

We recommend using the ossbrowser GUI tool or the ossutil command-line tool.

Note

Naming convention for data migration report files

uid@jobid@runtimeid_total_list_n: a list of all migrated files. Multiple files may exist. n is an integer that is greater than or equal to 0.
uid@jobid@runtimeid_failed_list_n: a list of files that failed to be migrated. Multiple files may exist. n is an integer that is greater than or equal to 0.
uid@jobid@runtimeid_skipped_list_n: a list of files that were skipped during migration. Multiple files may exist. n is an integer that is greater than or equal to 0.

The data migration report contains the following fields, which describe file properties from the source device to the destination OSS bucket.

Parameter	Description
srcObjectName	The name of the source file.
destObjectName	The name of the destination file.
srcObjectSize	The size of the source file.
destObjectSize	The size of the destination file.
srcContentMd5	The MD5 hash of the source file, used for consistency verification.
destContentMd5	The MD5 hash of the destination file, used for consistency verification.
srcCrc64	The CRC64 value of the source file, used for consistency checks.
destCrc64	The CRC64 value of the destination file, used for consistency checks.
srcLastModified	The time when the source file was last modified.
destLastModified	The time when the destination file was last modified.
srcVersionId	This field is empty. It applies only to multi-version migrations.
destVersionId	This field is empty. It applies only to multi-version migrations.
startTime	The time when the file migration started.
endTime	The time when the file migration ended.
isAbnormal	A boolean flag indicating if the migration was abnormal: false for normal, true for abnormal.
detailMsg	Provides the reason for the abnormality.

Data verification

The Data Transport II device is responsible only for data migration and does not guarantee data consistency or integrity. After the migration, you must perform a full data verification, ensuring consistency between the source and destination. After the migration is complete, promptly revoke the permissions granted to the specific RAM role for Data Transport II.

Warning

You are solely responsible for any data loss that occurs if you delete the source data before verifying the destination data is correct.