Object Migration troubleshooting

Available in Classic and VPC

You might run into the following problems when using Object Migration. Find out causes and possible solutions.

Transfer Object Storage buckets between NAVER Cloud Platform accounts

I want to transfer an Object Storage bucket to another NAVER Cloud Platform account.

Cause

You can transfer data to another account by using bucket permission settings and the CLI sync command.

Solution

Grant access to the other account in the bucket permission settings, and then execute the sync command.

To transfer bucket a from Account A to bucket b in Account B:

1. Grant Account A access to bucket b in Account B.
   • For details on how to grant bucket access to another account, see the permissions management.
2. Check the API authentication key for Account A.
   • To access another account’s bucket, you need the API key of the main account.
3. To sync bucket a from Account A to bucket b in Account B:

   aws --endpoint-url=https://kr.object.ncloudstorage.com s3 sync s3://a s3://b
   

   Note

   Account B does not have permissions for objects transferred from bucket a of Account A.

4. To grant Account B permissions for the objects transferred from bucket a of Account A, run the following command:

   aws --endpoint-url=https://kr.object.ncloudstorage.com s3 sync s3://a s3://b --grants full=id=CANONICAL_USER_ID1,id=CANONICAL_USER_ID2
   

   Note

   CANONICAL_USER_ID refers to the user ID used to identify a NAVER Cloud Platform account in Object Storage (e.g., ncp-xxxxxxx-0). You can check this value in the bucket permission settings.

Transfer objects to a different region

I want to use Object Migration to store data in a bucket in another region.

Cause

The system does not support transferring objects to a bucket in another region.

Solution

As explained above, transferring objects to a bucket in another region is not supported. Please configure each region separately.

Modify or add objects during migration

AWS (source) did not transfer the objects that were modified or added during or after the migration started.
I modified or added files during the migration, but the system did not reflect those changes.

Cause

The system identifies migration targets when it first executes the policy, so it does not transfer already migrated objects with changes or newly uploaded objects. However, if the migration has started but the object has not yet been transferred, the system can transfer the object with the applied changes. For example, if Object A is modified after the migration starts but before it is transferred, the system can transfer the object in its modified state.

Solution

Because the system may exclude objects modified during the migration process from the transfer, run the migration policy again after the current policy completes.

Migrate objects from Object Storage to AWS S3

I don’t know how to migrate data from NAVER Cloud Platform’s Object Storage to AWS S3.

Cause

Object Migration is a service that allows you to migrate data from another cloud to the NAVER Cloud Platform environment. The service does not support migrating data from the NAVER Cloud Platform to another cloud.

Solution

As described above, the system does not support transferring data to AWS S3.

Learning resources

We offer various materials for you to explore. To learn more about Object Migration check out these helpful links:

• FAQs: Object Migration FAQs
• API guide: Object Migration API guide