How to use rclone with eazyBackup e3

Use rclone to sync or backup data to e3 Object Storage. Connection settings: Connection details.

1

Install rclone

On Linux (example):

sudo apt update
curl https://rclone.org/install.sh | sudo bash
rclone version

2

Start rclone config

rclone config

When prompted to make a new remote, choose n (new remote).

3

Name the remote

Enter a name, for example e3.

4

Choose storage type

Select Amazon S3 Compliant Storage Provider (not “Amazon S3” alone if your rclone version lists both).

5

Choose provider variant

Select Any other S3 compatible provider.

6

Enter access key and secret key

Provide the Access Key ID and Secret Access Key for the bucket owner (Root or User). Create keys on Access Keys or Users in the client area.

7

Region and endpoint

• Region — ca-central-1 (or accept default if your rclone build maps it correctly).

• Endpoint — s3.ca-central-1.eazybackup.com (from Access Keys → Service URL).

Leave location constraint as default unless your rclone version requires an empty value.

8

ACL and advanced config

For ACL, the default private / owner full control is appropriate for backups.

Skip advanced config unless you need custom settings. Confirm and save the remote.

9

Test the remote

rclone lsd e3:

Lists buckets visible to the credentials you configured.

Create a bucket

From the client area: Buckets → Create Bucket.

Or with rclone:

rclone mkdir e3:my-bucket-name

Sync example

rclone sync /local/path e3:my-bucket-name/backup-folder --progress

Scheduled backup script

#!/bin/bash
# mydailybackup.sh
SOURCE="/data/to/backup"
REMOTE="e3:my-bucket-name/daily"
rclone sync "$SOURCE" "$REMOTE" --log-file=/var/log/rclone-e3.log

Add to cron for automated runs.

Troubleshooting

Issue	Check
Access denied	Keys must match the bucket owner user.
Wrong endpoint	Use s3.ca-central-1.eazybackup.com, not AWS endpoints.
Empty bucket list	Create a bucket in the dashboard or verify the key’s user owns buckets.