# Migrate from Wasabi S3 storage to Zata.ai S3 storage

Wasabi Storage is a cloud-based object storage service that provides high performance, scalability, and cost-effective storage solutions. It is commonly used for backup, disaster recovery, and archiving purposes.

**Prerequisites**

* Select any Linux operating system to perform this process.
* In this setup, **Ubuntu 22.04** is used as the operating system.
* Launch the Ubuntu [Instance](https://docs.neevcloud.com/neevcloud-products/computes/getting-started-launch-vms).

**Setup Wasabi**

* Open the Wasabi login page.
* Log in to the **Wasabi Console** to start the configuration [Wasabi Console.](https://console.wasabisys.com/login)

<figure><img src="https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2Fggcbdpf4E4oo24RE2Hlf%2Fimage.png?alt=media&#x26;token=9a8a923c-d0ca-4c27-b343-7e38c6789516" alt=""><figcaption></figcaption></figure>

**Create a Bucket in Wasabi**

* After logging in to the Wasabi Console, navigate to the **Buckets** section.
* Click on **Create Bucket** and complete the bucket creation process by providing the required details.

<figure><img src="https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2F7D8hT15qZuuSNQPmh98l%2Fimage.png?alt=media&#x26;token=34abd01c-6be8-4f2e-9bfb-b7bed03060d1" alt=""><figcaption></figcaption></figure>

**Create Access & Secret Key**

* Navigate to the **Access Keys** section in the Wasabi Console.
* Generate a new **Access Key ID** and **Secret Access Key**, and store them securely for later use.

<figure><img src="https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2FvKgX8nIl2f3d8ErDNLqf%2Fimage.png?alt=media&#x26;token=0f77c1ef-f763-4af4-b95a-8fed50a46329" alt=""><figcaption></figcaption></figure>

**Setup Zata.ai**

For Zata.ai configuration:

* Open the Zata.ai login page and sign in to your account [login page](https://auth.zata.ai/realms/zata/protocol/openid-connect/auth?client_id=zatacloud_client\&redirect_uri=https%3A%2F%2Fmy.zata.ai%2F\&state=dd2b5305-f7f5-4922-8639-4b0c62060c2f\&response_mode=fragment\&response_type=code\&scope=openid\&nonce=646d8811-0870-469c-9045-9e13d0fdd1b3\&code_challenge=wRG6I1qb9wdmY4unvHhPYaYq5WWM-801w72AYyLi8xY\&code_challenge_method=S256).
* Create a bucket by following the *Zata Bucket Creation Guide* [Bucket Creation Guide](https://docs.zata.ai/manage/bucket/create-bucket)
* Generate the Access Key ID and Secret Access Key by following the *Access Keys Guide* [Access Keys Guid](https://docs.zata.ai/manage/access-keys/creating-a-new-access-key)e
* Refer to the Zata.ai documentation for more detailed information and features [zata.ai](https://zata.ai/)

**Guide to Move Data from Wasabi to Zata.ai**

Ubuntu 22.04 is used as an intermediary system to facilitate the data migration from Wasabi S3 to Zata.ai S3.

**First Process (Wasabi Side Setup)**

* Update and upgrade the Ubuntu system to ensure all packages are up to date.

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

{% hint style="info" %}
For migrating data from Wasabi to Zata.ai, use **rclone.**
{% endhint %}

### Install and configure the **rclone.**

```
sudo apt-get install rclone -y
```

**Configure rclone for Wasabi and Zata.ai**

To migrate data, rclone must be configured for both Wasabi and Zata.ai. First configure rclone for Wasabi, and then repeat the same process for Zata.ai.\
\
Run the following command to start the rclone configuration:

```
sudo rclone config
```

When the rclone configuration starts, choose **`n`** to create a new remote.\
Enter **Wasabi** as the name of the remote.

<figure><img src="https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2Fqbo64VMvLSwpyDQU3lxt%2Fimage.png?alt=media&#x26;token=20f9e171-bdac-4a58-ad80-094d74c79edb" alt=""><figcaption></figcaption></figure>

Select **`4`** as the storage type to choose an S3-compatible storage provider.

{% hint style="info" %}
Note: The option number may vary depending on the rclone version
{% endhint %}

<figure><img src="https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2Fsmn03CqR7T5jxp9jY5Ip%2Fimage.png?alt=media&#x26;token=95842f3e-ffa7-4afb-a9cd-6252e194b023" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2FesDfuYHuYB9iOaKn1uPS%2Fimage.png?alt=media&#x26;token=f133ebb8-ac24-48b5-8266-b429ab1f5d65" alt=""><figcaption></figcaption></figure>

* `env_auth: true` is used to fetch credentials from environment variables.
* This option applies only when `access_key_id` and `secret_access_key` are left blank.
* Setting it to **true** means credentials will be taken automatically from the system environment.
* Setting it to **false** means credentials will be entered manually.

<figure><img src="https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2FaU9zKoNzztZUsVGcvTf5%2Fimage.png?alt=media&#x26;token=7dcc839e-fd72-4bfe-a638-b7754e6a03b8" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2F1NuFUU4mRNi3FXJAFSwW%2Fimage.png?alt=media&#x26;token=0e120f46-0011-4212-b506-818a1ed05118" alt=""><figcaption></figcaption></figure>

* Enter the region to connect to your S3 service.
* If you are using an S3-compatible provider (like Wasabi) and no region is required, leave it blank.
* Press **Enter** to use the default value

<figure><img src="https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2FFpiG2QyumpCptTKvD3Pm%2Fimage.png?alt=media&#x26;token=a461925b-b89c-40f6-814b-c883c043a05a" alt=""><figcaption></figcaption></figure>

Enter the S3 API endpoint for Wasabi (required for S3-compatible storage) and press Enter to continue.

<figure><img src="https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2FyoZ1CPv4XvceetnowqT6%2Fimage.png?alt=media&#x26;token=c6c264dd-1966-4f56-850a-74ad9e6bb98f" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2FvKcE3yC6ccqMqQCKw399%2Fimage.png?alt=media&#x26;token=be94174c-e9bc-48b7-bdff-6933431b2824" alt=""><figcaption></figcaption></figure>

Note that this ACL is applied only when creating buckets.

After completing these processes, simply press Enter at each step

<figure><img src="https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2FqILKKKyr83z0Y2YhJGAd%2Fimage.png?alt=media&#x26;token=568bbef9-e735-4728-ae94-47bac41059b0" alt=""><figcaption></figcaption></figure>

This is the remote configuration completed after following these steps:

<figure><img src="https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2FOo20RvgsUJtOAF6xcBuQ%2Fimage.png?alt=media&#x26;token=24a2caae-be5d-4c4a-bf6c-7cc24e292661" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Make sure to choose a number these values vary depending on the rclone version.
{% endhint %}

**Second Process for Zata.ai**

* Repeat the same rclone configuration process for Zata.ai.
* Choose **`n`** to create a new remote.
* Set the remote name as **zata**.
* Choose **`4`** for **S3 Compliant Storage Provider**.
* Choose **`13`** for **S3 Compatible Provider**.
* Set `env_auth` to **true**.
* Enter the **Zata Access Key ID** and **Secret Access Key** (refer to the Access Keys Guide).
* Set the endpoint as:

  ```
  idr01.zata.ai
  ```

<figure><img src="https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2FIN0OJCvB9BR9ERGAvUCl%2Fimage.png?alt=media&#x26;token=d1045887-bc8f-4e32-a223-233b9941d856" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Ensure you have created buckets in both **Wasabi** and **Zata.ai** before running these commands.
{% endhint %}

After completing the rclone configuration for both Wasabi and Zata.ai, you can start the data transfer process. Use the following command to copy data from the Wasabi bucket to the Zata.ai bucket:

```bash
rclone copy Wasabi:<wasabi_bucket_name> Zata:<zata_bucket_name> --s3-region ap-northeast-1 --progress
```

Replace `<wasabi_bucket_name>` with your Wasabi bucket name and `<zata_bucket_name>` with your Zata.ai bucket name. The `--progress` option displays the real-time status of the data transfer.

<figure><img src="https://2683631041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPPVG4W649TwXN8OejRhb%2Fuploads%2FvYIC3plWoNMSBti2DE8S%2Fimage.png?alt=media&#x26;token=38258b2c-e359-402a-abb6-48fdb051fe17" alt=""><figcaption></figcaption></figure>

After the migration is completed, return to both the **Wasabi Console** and the **Zata.ai Dashboard** to verify the bucket status and confirm that all data has been transferred successfully.