Skip to main content

How to Resume Failed Cloud Transfers Without Starting Over in RcloneView

· 3 min read
Tayson
Senior Engineer

You're migrating 2 TB from Google Drive to S3. At 1.3 TB, your network drops. Do you start over? Absolutely not.

Large cloud transfers inevitably get interrupted. Networks fail, computers sleep, API limits kick in, or providers have temporary outages. The question isn't whether a transfer will fail — it's how you recover. RcloneView uses rclone's intelligent resume logic to pick up exactly where you left off.

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.

How Resume Works

When you run a sync or copy job in RcloneView, rclone tracks what has already been transferred. If the job is interrupted and you run it again, rclone automatically:

  1. Checks what's already at the destination — by comparing file names, sizes, and modification times
  2. Skips completed files — files already transferred are not re-uploaded
  3. Resumes partial files — for providers that support it, partially uploaded files continue from where they left off

This means re-running a failed job doesn't re-transfer everything. It only handles what's missing.

Practical Recovery Steps

Step 1: Check what happened

Open Job History to see which files failed and why:

Review failed transfer details

Step 2: Re-run the same job

Simply run the same sync or copy job again. RcloneView will skip everything that completed successfully and only transfer the remaining files:

Re-run failed job

Step 3: Verify completeness

After the re-run completes, use Folder Comparison to confirm everything transferred:

Verify complete transfer

Tips for Reliable Large Transfers

Use Sync jobs, not one-time Copy

Sync jobs are inherently resumable — they compare source and destination, then transfer only differences. Save your transfer as a named job so you can re-run it anytime.

Schedule retries automatically

For overnight transfers that might fail, schedule the same job to run every few hours. Each run picks up where the last one stopped. When everything has transferred, subsequent runs complete instantly with nothing to do.

Schedule automatic retries

Monitor progress

Track transfer rates and file counts in real-time to spot problems early:

Monitor transfer progress

Getting Started

  1. Download RcloneView from rcloneview.com.
  2. Save transfers as named jobs for easy re-runs.
  3. Re-run failed jobs — they skip completed files automatically.
  4. Verify with Folder Comparison after completion.

Failed transfers are a bump in the road, not a brick wall.


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