Skip to main content

Migration Service

The Object Storage migration service moves the contents of a bucket in another storage service to a bucket in Arvancloud Object Storage. The source can be any S3-compatible service, such as AWS, Azure, Alibaba, MinIO, or another provider's object storage. For example, you can move the contents of your production bucket from Amazon S3 to Arvancloud.

If you want to move image and video archives, static website files, or backups (backup and dump files) without writing scripts, or you want to gather your data in Arvancloud before connecting the CDN, you can use this service. You can also track the status of each migration process from the panel without needing a CLI.

In the current version, the migration service only supports moving the contents of one source bucket to one destination bucket in Arvancloud Object Storage.

Prerequisites​

Before starting the migration, prepare the following:

  • An active Arvancloud account with access to Object Storage

    The guide to getting started with Object Storage helps you with this.

  • A destination bucket in Arvancloud with enough space, or the ability to create a new bucket

    The Buckets guide helps you with this.

  • An Access Key and Secret Key (or their equivalent in the source service) with read access to the source bucket

  • The correct source endpoint address, for example https://s3.eu-central-1.amazonaws.com

The size of the source bucket and the number of concurrent active processes depend on your Object Storage plan.

Creating a Migration Process​

To start, go to Object Storage in the Arvancloud panel and select Migration Service from the menu. On this page, you can see the list of previous migrations, and click Migration to start a new process.

Step 1: Service Settings​

In this step, you connect to the source storage and check access.

In the first section, select S3-Compatible.

The FTP and Google Drive options will be available soon.

After that, fill in the following fields:

  • Endpoint address

    Enter the source service's endpoint address without https://, for example s3.eu-central-1.amazonaws.com.

  • Access Key

    Enter the source service's Access Key. This field is required.

  • Secret Key

    Enter the source service's Secret Key. This field is required.

  • Region

    If the source service has regions, enter the region's name. This field is optional.

  • Use SSL

    This option specifies whether the connection to the source service uses SSL.

Then click Check Connection.

If the connection isn't established, check the endpoint, Access Key, and Secret Key again, and make sure the entered key has read access to the source bucket.

Step 2: Choose the Source Bucket​

In this step, select one of the buckets for migration. You can also search among the buckets or refresh the list.

If the source bucket has a large number of objects, they're counted precisely in the last step, before the migration starts.

Step 3: Choose the Destination Bucket​

In this step, you select a bucket in Arvancloud that has enough space for the source data.

If a bucket doesn't have enough space for the source data, in terms of size or number of objects, its row is disabled and a red Insufficient Quota label is shown next to it. In this case, select another bucket with more capacity, or create a new bucket and then refresh the list.

Step 4: Transfer Settings​

In this step, you specify how the transfer is done and start the migration.

  • Transfer type

    One-Time Copy copies all source data to the destination once.

    Continuous Sync is intended for continuous synchronization and will be available soon.

  • Conflict policy

    Specifies what happens if a file with the same name exists in the destination. With Skip, the existing file in the destination stays untouched and isn't copied from the source. With Overwrite, the destination version is replaced with the source version.

    Note that with Overwrite, files in the destination bucket with the same name are lost.

Review the settings in the migration details section and click Start Migration.

After it starts, you're taken to the migration list, where you can see the process's status.