File transfer guide

Rclone with S3: configure storage and copy files safely

Rclone connects local folders and cloud storage. This guide sets up NordenVault as an S3 remote, previews a transfer and checks a restored copy. It also explains the deletion behaviour you need to understand before using sync.

Choose the right workflow

Rclone is useful when you need files stored as ordinary objects that you can also browse in NordenVault. A recurring copy keeps another copy of those files, but it does not automatically create a recoverable history of every change. For encrypted snapshots and a snapshot-based restore workflow, start with the restic guide.

Install rclone from its official installation page. Create a backup source in NordenVault and have its access key, secret key, bucket name and endpoint ready. The examples below use a Unix-like shell. Adjust paths and quoting for your operating system.

Configure an S3-compatible remote

rclone config

Create a new remote named nordenvault. Select Amazon S3 compatible storage, then the provider option for another S3-compatible service. Enter your credentials interactively, and use https://s3.nordenvault.com as the endpoint. Use the region provided with your storage configuration if one is required.

Keep the resulting configuration private. It contains credentials. Rclone’s S3 backend reference covers endpoint and provider settings. Avoid copying a configuration that contains someone else’s keys or an endpoint for a different provider.

Preview the first transfer

rclone copy /path/to/test-folder nordenvault:YOUR_BUCKET/files --dry-run

Read the proposed operations and confirm the destination. The command copies the contents of the local directory into the remote files prefix. Use a small folder for your first test and keep the original files in place.

When the preview is correct, run the transfer:

rclone copy /path/to/test-folder nordenvault:YOUR_BUCKET/files --progress

The copy command transfers new or changed files and leaves extra destination files in place. It can overwrite a destination file when the source changes. Decide whether you need version history before scheduling repeated copies.

Verify the copy and test a download

rclone check /path/to/test-folder nordenvault:YOUR_BUCKET/files --one-way --download
rclone copy nordenvault:YOUR_BUCKET/files /path/to/empty-restore-test --progress

The check compares source and destination without changing them. Here, --one-way allows extra remote files and --download verifies content by reading it. This can take time and use significant bandwidth for a large folder. See the check reference.

Open the downloaded test files. Confirm names and folder structure, then repeat from the machine or account you would use after a failure. Record the remote name, bucket, recovery credentials and result of the test somewhere accessible to the person responsible for recovery.

Understand copy and sync before automating

CommandExtra files at destinationTypical use
copyKeptAdd or update a second copy of files.
syncCan be deletedMake the destination match the source.

The sync documentation explains its destination-deletion behaviour. If a local folder becomes empty or files disappear, a later sync can propagate that state. Preview with --dry-run and check the source and destination direction each time you change a job.

Set a schedule you can monitor

Schedule the verified command through your operating system. Save logs to a protected location and alert on failures. Keep the configuration available to the scheduled-job account, and avoid overlapping transfers. A command that runs without anyone checking the result is a weak recovery plan.

Ordinary rclone S3 transfers are not client-side encrypted backups. If you require client-side encryption, review rclone crypt or use restic. Store encryption recovery information independently, and test the encrypted restore path too.