Migrate from Wasabi S3 storage to Zata.ai S3 storage

Wasabi Storage is a cloud storage service providing high-performance, scalable, and cost-effective storage solutions wasabi is suitable for backup, recovery, and archiving needs.

Prerequisites

Select any Linux operating system to perform these processes.

We have chosen the operating system "Ubuntu 22.04"

Launch the Instance

Setup Wasabi

Click on the Wasabi Console.

To create a bucket in wasabi

After logging in to Wasabi, navigate to Buckets and create a bucket

To create Access & Secret Key

Navigate to the Access Keys section.

Setup Zata.ai

For Zata.ai configuration:

• Click on the Zata login page.
• Zata Bucket - See our Bucket Creation Guide
• Zata Access & Secret Key Pair - See our Access Keys Guide
• For more information about the zata.ai

Guide to Move Data from Wasabi to Zata.ai

We used Ubuntu 22.04 as the mediator to facilitate the data migration from Wasabi to Zata.ai.

The first process for Wasabi

Update && Upgrade the system.

sudo apt-get update -y
sudo apt-get upgrade -y

For migrating data from Wasabi to Zata.ai, use rclone.

Install and configure the rclone.

sudo apt-get install rclone -y

To configure rclone for Wasabi, and then configure it in Zata.ai.

Run the following command to configure ' rclone ':

sudo rclone config

When you run the command above, follow these steps:

Choose 'n' to create a new remote

Name: Wasabi (Give the name of the remote)

Type of storage to configure: '4'; these values vary depending on the rclone version.

Choose your S3 Provider to choose '12' for Wasabi object storage, these numbers are very dependent on the rclone versions.

Get credentials from runtime (environment variables or metadata if no env vars). This only applies if access_key_id and secret_access_key are blank. Enter a boolean value (true or false). Press Enter for the default ("false"). Choose a number from below, or type in your value.

env_auth: true

Access & Secret key - We have created the above in the Wasabi section.

Region to connect to. Leave blank if you are using an S3 clone and you don't have a region. Enter a string value. Press Enter for the default. Choose a number from below, or type in your value

Endpoint for S3 API. Required when using an S3 clone. Enter a string value. Press Enter for the default. Choose a number from below, or type in your value

Note that this ACL is applied when server-side copying objects as S3

Note that this ACL is applied only when creating buckets.

After completing these processes, simply press Enter at each step

This is the remote configuration completed after following these steps:

Make sure to choose a number these values vary depending on the rclone version.

Second process for Zata.ai

The same process is now being applied to Zata.ai.

Choose 'n' to create a new remote.

Name it: zata

Choose '4' for S3 Compliant Storage Provider

Choose'13' for S3 compatible provider

env_auth : true

Access & Secret Key Pair - See our Access Keys Guide

Endpoint: idr01.zata.ai

Ensure you have created buckets in both Wasabi and Zata.ai before running these commands.

Now complete the configuration to run these commands.

To copy and move your data

rclone copy Wasabi:(wasabi_bucket_name) Zata:(zata_bucket_name) --s3-region ap-northeast-1 --progress

Now, return to both Wasabi and zata.ai to check the status of buckets and details of the data.