Transferring Data With Wasabi Ball

Transferring Data to the Wasabi Ball Transfer Appliance

Once the Appliance is mounted, the transfer process can begin. All data should be transferred to the mount point:

For transfer using the S3 application, the data should be transferred to:

Any data added to the mount point will be added to the single specified bucket, preserving the folder hierarchy.

Preparing Your S3 Client for Uploads to the Wasabi Ball Appliance

The default bucket on the Wasabi Ball is:

Users can create buckets under that prefix. Wasabi automatically strips the prefix /Volume/wasabi-s3 from the Object ID. For example:

Wasabi Ball Credentials

The Wasabi Ball appliance ships with its own set of S3 credentials. The access/secret key is required in the S3 client configuration to communicate with the Wasabi Ball Appliance.

You can obtain the required Access key and Secret key using the following procedure:

Capture the Access key and Secret key as shown in the result. For example:

Wasabi Ball Connection Parameters

In order to authenticate and connect to the Wasabi Ball to upload your data from your S3 source to the Wasabi Ball, you need to enter the correct destination address for the S3 target.

The default S3 server configuration is:

HTTP
Port 9000

If you need to use HTTPs and/or port 80, note that the correct destination address, by default requires you to specify the UDP Port as shown below.

Configure the provided WB Access key/Secret key credentials and connect.

Additional Wasabi Ball Configuration Parameters

Enabling HTTPS (443) on the Wasabi Ball Appliance

Complete the following procedure to enable HTTPS (443) on the Wasabi Ball Appliance. This will allow port 443 (a common default port required for some S3 applications) to be used.

1. ssh into the device, as described above.
2. Run enable_tls.sh on the Target Wasabi Ball ssh shell:
   /usr/local/bin# enable_tls.sh
3. systemctl stop apache2.
4. Add the following line to the /etc/default/minio file:
   MINIO_OPTS="--address :443"
5. systemctl restart minio.
6. If the Wasabi Ball is rebooted, you need to repeat Steps 2 and 4.
7. Run systemctl restart minio.

Wasabi Ball can now be used with HTTPs on port 9000.

When the HTTPs option is enabled, the S3 client needs to be configured to "disable the SSL certificate check."

Disabling HTTPS (443) on the Wasabi Ball Appliance

Complete the following procedure to disable HTTPS (443) on the Wasabi Ball Appliance:

1. ssh into the WB linux shell.
2. Delete the files /root/.minio/certs/public.crt and /root/.minio/certs/private.key
3. Remove or comment out the following line in the /etc/default/minio file:
   MINIO_OPTS="--address :443"
4. Restart the minio server "systemctl restart minio"

Transferring Data from the Wasabi Ball Transfer Appliance

Once the Appliance arrives at Wasabi’s data center, Wasabi will begin the transfer process to get your files into your account. To achieve this, Wasabi will need to be able to access your account via an Access key.

Using the Wasabi Console, create a sub-user account for Wasabi to access your account with read/write permissions for the specific bucket(s) to which you would like Wasabi to integrate the transferred files.

The Getting Started with Wasabi Cloud Storage Product Guide provides detailed instructions as to how to create a sub-user account and provision access.

Encrypting Data

You can opt to encode data with AES 256-bit volume-based encryption before sending it to Wasabi.

Wasabi will send you an encryption key via email or on a USB drive. If the key is sent via email, copy it to a USB drive.

Insert the USB drive in Wasabi Ball and back up your data.