Migrate from Wasabi s3 storage to NeevCloud 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

For Wasabi configuration:

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.

After performing these processes in Wasabi, configure the NeevCloud settings.

Setup Neevcloud

Click on the Neevcloud login page.

Neevcloud Bucket - See our Bucket Creation Guide

Neevcloud Access & Secret Key Pair - See our Access Keys Guide

For more information Neevcloud

Guide to Move Data from Wasabi to NeevCloud.

We used Ubuntu 22.04 as the mediator to facilitate the data migration from Wasabi to NeevCloud S3.

For example, on a Ubuntu 22.04 system.

The first process for Wasabi

Update && Upgrade the systems.

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

For migrating data from Wasabi to Neevcloud, use rclone

Install and configure the rclone.

sudo apt-get install rclone -y

To configure rclone for Wasabi, and then configure it in Neevcloud.

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 to Choose '4' for Aws s3 compliant storage provider.

Choose your S3 provider to Choose '12' for Wasabi object storage.

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:

Second process for Neevcloud

The same process is now being applied to Neevcloud.

Choose 'n' to create a new remote.

Name it 'Neevcloud'

Choose '4' for S3 Compliant Storage Provider

Choose'13' for S3 compatible provider

env_auth : true

Access & Secret Key - See our Access Keys Guide

EndPoint: s3-api.neevcloud.com

Once you have applied the same process, see Configure the details for Neevcloud.

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

Now complete the configuration to run these commands.

sudo rclone move Wasabi:(wasabi_bucket_name) Neevcloud:(neevcloud_bucket_name)  --progress

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