Synology is meant to be easy and intuitive to use. Backing up from Synology to Synology is a breeze, but once you try to use another standard way of making backup like rsync, it becomes the most unintuitive and frustrating experience.
This guide explains how to back up data from a Synology NAS to TrueNAS using the Rsync daemon, including the gotchas and confusing parts that will save you hours of troubleshooting.
1. Set Up TrueNAS #
- Create a backup dataset
- Set the share type to
Appsor add read/write permissions for the app user.
- Set the share type to
- Install the Rsync Daemon app (one app per backup)
- Set the appropriate rsync port.
- Add a module:
- Name
- Choose host path to the dataset, give read/write access
- Set app user and group ID
- Set host allow to only the Synology IP
- Install the app
Tailscale (Optional, for secure connectivity) #
- Install the Tailscale app on Synology and follow the steps here: Tailscale Synology Guide
- Schedule automatic updates
- Enable outbound connections
- Adjust Synology firewall settings if needed
2. Rsync on Synology #
- No need to enable SSH or rsync server on Synology for this method.
- Use Hyper Backup:
-
Go to Hyper Backup > New Backup > rsync > Single Version
-
Setup:
- Server type: Rsync-compatible server
- Server name or IP address: TrueNAS IP address (not domain)
- Transfer Encryption: Off
- Port: Rsync daemon port
- Username: Anything (seriously, type anything - it doesn’t matter)
- Password: Can be empty (Synology asks for it but ignores whatever you put)
- Backup module: Choose the created module
Note: Synology’s UI requires username and password fields, but when using rsync daemon without authentication, these values are ignored. Don’t waste time trying to figure out the “correct” credentials.
-
Click Next and choose what to back up
-
3. Troubleshooting #
- rsync: [generator] failed to set permissions on “/.” (in backuptruenas): Operation not permitted (1)
- Solution: Ensure correct permissions are set in the Rsync daemon app (read/write access).
- Insufficient privileges to access destination shared folder.
- Solution: Creating a new dataset as
appsfixes this.
- Solution: Creating a new dataset as
- Connectivity:
- SSH into Synology and use
pingandsshto test connectivity to TrueNAS.
- SSH into Synology and use