Proton Drive Backup

Version: 1.0.0.r17
Update: 06/09/2026
Developer: Download
Maintainer: thecap
Architecture: ["x86-64"]
Apk X86-64: Download
Minimal Supported ADM Version: ADM 5.1
Release Note:

1.0.0.r17
– Adds near-real-time automatic one-way NAS -> Proton Drive backups.
– In NAS -> Proton mode with Automatic enabled, native filesystem events are grouped with a 30-second debounce and trigger one rclone copy automatically.
– Adds a periodic NAS -> Proton safety pass at the selected automatic interval, including every 5 minutes, to catch changes missed while the application or watcher was stopped.
– Keeps automatic Proton -> NAS polling at the selected interval because Proton Drive does not provide a local filesystem event to the NAS application.
– One-way modes remain protective: rclone copy adds/updates destination files but does not propagate source deletions to the destination.
– Keeps bidirectional NAS Proton automatic synchronization, overlap protection, secure R15/R16 Web session handling and native Docker-independent rclone.
– Preserves existing Proton configuration, Web credentials and transfer settings during upgrade.

Description:

Native ASUSTOR backup and optional bidirectional synchronization for Proton Drive.

Available modes:
– NAS → Proton Drive: safe one-way backup using rclone copy. With Automatic enabled, local filesystem changes are detected natively and grouped with a 30-second debounce, then copied automatically to Proton. A periodic safety pass at the selected interval catches changes missed while the app was stopped. Deleting a NAS file does not delete its existing Proton backup.
– Proton Drive → NAS: safe one-way backup using rclone copy. With Automatic enabled, Proton is checked at the selected interval (5, 15, 30, 60, 180, 360, 720 or 1440 minutes). New and modified remote files are copied to the NAS. Deleting a Proton file does not delete its existing NAS backup.
– NAS ↔ Proton Drive: bidirectional synchronization using rclone bisync. Local NAS changes use the same 30-second event debounce while Proton changes are detected by periodic polling. Changes and deletions can propagate both ways and bisync must be initialized explicitly before first use.

The Web UI and transfer engine run natively and do not require Docker.

Rate this post