Title
Enhanced Auto-Sync & Backup Scheduling – Plus Edition
Description
Introduce a real-time or periodic automatic backup system that works silently in the background. The backup process should support:
-
Continuous file monitoring (e.g., every X minutes) -
Non-destructive backups (e.g., backup-dir support) -
Multi-cloud backup targets (e.g., Dropbox + Google Drive) -
Conflict-safe operations with versioned folders
This would extend RcloneView beyond manual copy/sync into a resilient automatic backup scheduler, ideal for everyday users and small teams.
Usage Scenarios
Let’s say a user edits a.doc on their desktop. Without user intervention:
-
RcloneView periodically detects changes in the source folder.
-
Modified files are automatically copied to:
-
Primary cloud (e.g., Dropbox) for immediate backup
-
Secondary cloud (e.g., Google Drive) as a failover archive
-
-
(Optional) Older versions are preserved in a time-stamped --backup-dir, supporting rollback.
This ensures real-time protection and multi-point redundancy.
Reference UI (Inspiration)
Limitations to Overcome
| Issue | Solution Proposal |
|---|---|
| Rclone itself doesn’t support real-time sync natively | Use periodic polling + compare timestamps (RcloneView layer) |
| Rclone sync may delete files on the target | Default to copy mode with --backup-dir to preserve older files |
Roadmap (Vision)
-
rclone copy + --backup-dir as safe default -
Add per-job retention policy manager (e.g., keep last N versions) -
Support multiple backup targets per job -
Add visual time picker & cron options for flexible scheduling -
(Optional) Integrate Change Detection Layer (based on fs event or hashing)
Want this feature?
Upvote this post if you’d like to see Auto-Backup + Versioned Sync in RcloneView!
Have other suggestions for backup policies or scheduling UI? Comment below ![]()