-
[Plugin] Unraid Rsync — multi-job rsync backup scheduler
@haabijaabi Great, glad to hear it works
-
[Plugin] Unraid Rsync — multi-job rsync backup scheduler
@haabijaabi Thanks for the update. The post-quantum message is an OpenSSH warning; it doesn’t prevent the connection. The line we need to investigate is “Permission denied, please try again.” Could you run Connections → Test connection for that same connection and share the result? Please also include your plugin version and whether you use password or SSH-key authentication—no passwords or private keys. If Test connection fails, we’ll check SSH login and account access. If it succeeds, we’ll check Synology’s rsync service, application privileges, and access to the source folder. That will help distinguish a NAS configuration issue from a plugin problem. The misleading path labels have been fixed, and the update is being released (https://github.com/sasa-fajkovic/unraid-rsync/releases/tag/2026.10.30) This permission-denied error needs a separate diagnosis.
-
[Plugin] Unraid Rsync — multi-job rsync backup scheduler
Hey @haabijaabi The order of paths you put is wrong. Should be like this: Left (Unraid): /mnt/user/Backup/aamarnas/ Right (Synology): /volume1/FTP_FOLDER/ Direction: Pull The labels for the fields are misleading. I will release an update soon fixing it
-
[Plugin] Unraid Rsync — multi-job rsync backup scheduler
@haabijaabi Give me a few hours to check this. Sounds like an easy fix
-
[Plugin] Unraid Rsync — multi-job rsync backup scheduler
Glad to hear. Enjoy
-
[Plugin] Unraid Rsync — multi-job rsync backup scheduler
Hi @newmy - new version released fixing the issue with characters in username https://github.com/sasa-fajkovic/unraid-rsync/releases/tag/2026.10.24
-
[Plugin] Unraid Rsync — multi-job rsync backup scheduler
Hey @newmy , this is limitation on characters in the plugin. Seems I made whitelisting too restrictive. I will release a new version during the day with a fix.
-
[Plugin] Unraid Rsync — multi-job rsync backup scheduler
New: snapshot mode (versioned backups) — 2026.10.22a Hi all, this is the biggest update so far: snapshot mode. Until now a job kept one mirror on the destination. If a file was deleted, corrupted or encrypted on the server, the next run copied that damage straight into the backup. Snapshot mode keeps dated, versioned copies instead. How it works Every run writes a new folder on the receiver, named after its start time in UTC (for example 2026-10-22T030000Z/). Unchanged files are hard links to the previous snapshot (rsync --link-dest). Every snapshot is a complete tree you can browse and restore from, but it only costs the space of what changed. A snapshot only counts if the run finished cleanly. A failed or aborted run stays as .inprogress and is reused by the next run, so nothing is sent twice. Retention: keep N daily / weekly / monthly snapshots (default 7 daily + 4 weekly). Pruning starts as a dry run that only logs its plan, and deletes at most a few snapshots per run. Safety nets (the part I spent the most time on) A target marker file with a UUID on the backup drive is mandatory, and the snapshot folder must already exist with a small sentinel file. A run never writes into an empty mountpoint, and the plugin never creates the snapshot folder itself. If a run looks wrong (far fewer files or bytes than last time, or the disk suddenly growing much faster than usual, which is what ransomware looks like), it still saves the snapshot but puts all deletions on hold, pins the previous snapshot and sends an alert. Nothing is pruned until you have looked at it and removed the hold. Clock checks on both ends, --inplace is refused (it would silently change older snapshots), --delete is forced off, and a mirror job with --delete cannot point at a snapshot folder. You can now back up the flash drive: a snapshot job may use /boot/ as its source, with recommended excludes for the previous OS version and the Tailscale state. Requirements SSH transport, Push direction. A Linux receiver with GNU coreutils and util-linux (Debian, Ubuntu, Raspberry Pi OS and the like; BusyBox-based systems are not supported). Root on the receiver, either by logging in as root or with passwordless sudo (there is a new “Use sudo on the receiver” option on the connection). rsync 3.2.4 or newer on both ends. Getting started Update the plugin, then follow the guide: https://github.com/sasa-fajkovic/unraid-rsync/blob/main/docs/snapshot-mode.md It covers setup step by step, how a run works, retention with a worked example, restoring, troubleshooting, and how to turn an existing mirror into the first snapshot without copying everything again. Existing mirror jobs are unchanged. Nothing is different unless you turn snapshot mode on for a job. How it was tested Besides the unit tests, I ran a throwaway job against a Raspberry Pi 3B with a 12 TB USB disk and broke it on purpose: aborted manual and scheduled runs, a missing snapshot folder, a receiver clock in the future, a source that suddenly lost three quarters of its files, a run that ended with rsync exit 23, and pruning a snapshot with 100,000 files (about 7 seconds). I’m now moving my own daily jobs (appdata, Immich, Nextcloud and the flash drive) to snapshot mode. Feedback is very welcome, especially from people with receivers other than Debian or Raspberry Pi OS. Bugs and ideas: https://github.com/sasa-fajkovic/unraid-rsync/issues or this thread.
-
[Plugin] Unraid Rsync — multi-job rsync backup scheduler
Great, glad to hear :)
-
[Plugin] Unraid Rsync — multi-job rsync backup scheduler
Hi @stephen niehaus — thanks for the report. Version 2026.09.24 adds a configurable Detailed statistics option, globally or per job: https://github.com/sasa-fajkovic/unraid-rsync/releases/tag/2026.09.24 Choose Older rsync --stats): with Normal/Verbose logging, this keeps --info=progress2 but no longer sends stats2. The existing Current setting remains the default, so other jobs won't change on update. Your older Synology may also reject -mkpath. If so, turn off Create destination path if missing for that job and make sure the destination directory already exists. Please try a dry-run first and let me know if its log shows anything else.
-
[Plugin] Unraid Rsync — multi-job rsync backup scheduler
@d3fc0n0wltraps Welcome :)
-
[Plugin] Unraid Rsync — multi-job rsync backup scheduler
Hey @PandaSharp - I've added a "Summary" level for logging which will reduce it significantly. Choose that :)
-
[Plugin] Unraid Rsync — multi-job rsync backup scheduler
Glad the dry run worked and have high hopes the real run will also work :)
-
[Plugin] Unraid Rsync — multi-job rsync backup scheduler
Hey @PandaSharp let me know how it goes when you give it a shot :)
-
[Plugin] Unraid Rsync — multi-job rsync backup scheduler
Thanks @d3fc0n0wltraps — glad it's replaced the rclone setup. Not a Custom Tab bug and not really fixable on my side: Custom Tab's "Built-In Page" mode copies the body of the selected .page file into a new tab. UnraidRsync.page is only a tab container (Unraid xmenu), so its body is intentionally empty — the seven real pages are separate files. Putting content in the container would add a phantom eighth tab to the normal Settings page, so I'd rather not. Two ways that already work: 1. Use Custom Tab's URL mode with a relative URL: /Settings/UnraidRsync It's same-origin, so it works via IP, hostname or proxy without re-login and doesn't depend on the proxy being up. (Unraid only allows framing from the same origin, which is why the full proxy URL only worked when you were browsing through the proxy.) 2. Or pick the individual pages from the Built-In dropdown — they're listed under their own names: "Overview", "Jobs", "Connections", "Credentials", "Global Settings", "Status", "History" (all unraid.rsync/UR.*.page). One nav tab per page. Option 1 is probably what you want.
fajkovic.sasa
Members
-
Joined
-
Last visited