Sync Google Drive to Koofr — Cloud Backup with RcloneView
Keep a European-hosted mirror of your Google Drive on Koofr without writing a single rclone command.
Teams with EU-based clients or data residency preferences often want a second copy of their Google Drive content sitting on European infrastructure. Koofr, based in the EU, is a natural fit for that role, but manually re-uploading files after every change isn't sustainable. RcloneView connects both accounts and runs the sync as a saved job, keeping the Koofr copy current without any manual file shuffling.
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
Free core features. Plus automations available.
Connecting Google Drive and Koofr
Both remotes use the setup methods native to each provider: Google Drive connects through an OAuth browser login, and Koofr is added the same way from Remote tab > New Remote. Once both appear in the Remote Manager, open two Explorer panels side by side — one on Google Drive, one on Koofr — so you can drag and drop a quick test copy before setting up an automated job. Dragging between the two panels always copies rather than moves, since they're separate remotes.
Configuring the Sync Job
Launch the sync wizard from the Home tab and set Google Drive as the source, Koofr as the destination. Choose one-way "Modifying destination only" so the Koofr copy always mirrors Drive without accidentally deleting anything back on the source. In Step 2, enabling checksum comparison ensures files are matched by content rather than just modification time, which matters when files pass through different sync clients before reaching Drive.
RcloneView's 1:N sync can mirror the same Google Drive folder to Koofr and additional destinations at once, on the FREE license — useful if a second backup target gets added later without rebuilding the job.
Running a Dry Run Before the First Sync
Before committing to a full transfer, run Dry Run to preview exactly which files will copy and confirm none will be deleted from Koofr unexpectedly. This is especially useful the first time a job runs against a Koofr account that already has content in the destination folder, since it surfaces conflicts before they become real overwrites.
Getting Started
- Download RcloneView from rcloneview.com.
- Add both Google Drive and Koofr as remotes.
- Create a one-way sync job with checksum comparison enabled.
- Run a dry run, then execute the job to build your first Koofr mirror.
A standing Google Drive to Koofr sync gives you a European-hosted backup you can rerun in a couple of clicks, so your recovery copy never depends on rebuilding the job from scratch.
Related Guides:
- Migrate Koofr to Google Drive — Transfer Files with RcloneView
- Manage Koofr Storage — Sync and Backup Files with RcloneView
- Sync Koofr to Amazon S3 — Cloud Backup with RcloneView
Supported Cloud Providers
