Skip to main content

Sync Box to Wasabi — Cloud Backup with RcloneView

· 3 min read
Tayson
Senior Engineer

Keep an independent copy of your Box content in Wasabi object storage with a repeatable one-way sync.

Box is a convenient place to collaborate, but a second copy outside the platform protects you from accidental deletions, account lockouts, and retention gaps. Wasabi is S3-compatible object storage, which makes it a natural target for that copy. RcloneView connects both services in one window, and basic sync and Dry Run are available with the FREE license.

RcloneView app preview

Manage & Sync All Clouds in One Place

RcloneView is a cross-platform GUI for rclone. Compare folders, transfer or sync files, and automate multi-cloud workflows with a clean, visual interface.

  • One-click jobs: Copy · Sync · Compare
  • Schedulers & history for reliable automation
  • Works with Google Drive, OneDrive, Dropbox, S3, WebDAV, SFTP and more
WindowsmacOSLinux
Get Started Free →

Free core features. Plus automations available.

Connect Box and Wasabi as Remotes​

Box uses browser-based OAuth. In RcloneView, add a new remote, choose Box, and sign in when the browser opens. If your organization uses Box for Business, the remote needs box_sub_type = enterprise. Wasabi is added as an S3-compatible remote: enter your Access Key, Secret Key, and the endpoint for your Wasabi region.

Once both remotes appear in the Remote Manager, open them in two Explorer panels side by side. You can then browse the Box folder tree on the left and a Wasabi bucket on the right before configuring anything.

Adding Box and Wasabi remotes in RcloneView

Preview with Dry Run Before You Sync​

Imagine a design agency with 800 GB of client project folders in Box. Before the first sync, run a Dry Run. It lists which files would be copied and which would be deleted, without changing anything. This helps you avoid pointing a sync at the wrong bucket path.

For a backup, one-way sync ("Modifying destination only") is the right direction: Box stays the source of truth and Wasabi mirrors it. Remember that a sync also deletes destination files that no longer exist in the source, so use a dedicated bucket or prefix for the mirror.

Cloud-to-cloud transfer between Box and Wasabi

Configure the Sync Job​

The Job wizard walks through four steps: storage, advanced settings, filters, and scheduling. Raise the number of file transfers if you have many small documents, and enable checksum comparison when you want hash-based verification. Predefined filters include a Box Docs option, useful because Box Notes and similar online-only items do not behave like regular files.

Name the job with letters, digits, hyphens, or underscores, save it, and run it. Progress, speed, and file counts appear in the Transferring tab.

Running a saved Box to Wasabi sync job

Schedule and Verify​

Schedule-based sync is a PLUS feature, with crontab-style fields and a simulator that previews upcoming run times. A nightly run keeps the Wasabi copy current. After each run, open Job History to check status, size, and file count, or use Folder Compare to confirm the two sides match.

Scheduling a recurring sync job in RcloneView

Getting Started​

  1. Download RcloneView from rcloneview.com.
  2. Add your Box remote through OAuth and your Wasabi remote with its keys and endpoint.
  3. Create a sync job from Box to a dedicated Wasabi bucket, and run a Dry Run first.
  4. Run the job, then verify with Folder Compare and Job History.

A tested, scheduled mirror turns Box from a single point of failure into one half of a real backup.


Related Guides:

Supported Cloud Providers

Local Files
WebDAV
FTP
SFTP
HTTP
SMB / CIFS
Google Drive
Google Photos
Google Cloud Storage
OneDrive
Dropbox
Box
MS Azure Blob
MS File Storage
S3 Compatible
Amazon S3
pCloud
Wasabi
Mega
Backblaze B2
Cloudflare R2
Alibaba OSS
Ceph
Swift (OpenStack)
IBM Cloud Object Storage
Oracle Cloud Object Storage
IDrive e2
MinIO
Storj
DigitalOcean Spaces