How to Migrate Data to Stook Using Rclone

Step-by-step guide to migrate data to Stook using Rclone.

Use Rclone to migrate objects from any S3-compatible storage to Medianova Stook Object Storage. Rclone is a good fit for large transfers and resumable copies.

---

Prerequisites

• Rclone installed on your machine Download: https://rclone.org/downloads/

• Source S3 credentials:

  • Endpoint URL

  • Access Key

  • Secret Key

  • Bucket name (and optional prefix)

• Stook credentials:

  • Server (endpoint, e.g. https://xxxxx.mncdn.com)

  • Access Key

  • Secret Key

  • Bucket name

Credentials are private. Do not share them.

Need keys or endpoint details? Start with Getting Started with Stook and Manage Access Keys.

---

Migration steps

1

Configure your source remote

Run the config wizard:

rclone config

Create a new remote. Use the s3 backend. Enter your source endpoint and credentials.

2

Configure your Stook remote

Run rclone config again. Create a second remote, for example stook.

Use the s3 backend. Set your Stook endpoint (for example https://xxxxx.mncdn.com). Enter your Stook Access Key and Secret Key.

If you see signature or redirect errors, enable path-style addressing for the Stook remote. In Rclone, this is usually force_path_style = true.

3

Validate connectivity

List buckets or prefixes to confirm auth and endpoint settings:

rclone lsd source:
rclone lsd stook:

4

Copy objects

Copy a full bucket:

rclone copy source:source-bucket-name stook:target-bucket-name --progress

Copy a prefix only:

rclone copy source:source-bucket-name/path/to/data stook:target-bucket-name/path/to/data --progress

Use copy to only add/update objects. Use sync to make the destination match the source (including deletions).

5

Tune and monitor large transfers

Increase parallelism when you need speed:

rclone copy source:source-bucket-name stook:target-bucket-name --progress --transfers 8 --checkers 16

Write logs for audits and retries:

rclone copy source:source-bucket-name stook:target-bucket-name --log-file rclone-stook.log --log-level INFO

6

Verify migrated data

Run a post-copy verification:

rclone check source:source-bucket-name stook:target-bucket-name

Rclone compares object listings and, when supported, hashes. Hash checks can vary across S3 implementations.

---

Troubleshooting

• Auth error (403/401): Re-check Access Key, Secret Key, and endpoint URL.

• Redirect/signature mismatch: Enable path-style addressing (force_path_style = true).

• Slow transfer: Increase --transfers and verify network throughput.

• Missing objects: Re-run rclone copy. It is safe and incremental.

---

References

• Rclone Downloads

• Rclone S3 backend documentation