synology-windows-ssh-rsync-backup | Synology Windows computer backup via rsync | Continuous Backup library

Enable SSH on your Synology NAS if you haven't already. Go to Control Panel - Terminal, and check "Enable SSH service". Log into your Synology via SSH. Create a /root/.ssh directory if it doesn't already exist.
Enable SSH on your Synology NAS if you haven't already. Go to Control Panel - Terminal, and check "Enable SSH service".
Log into your Synology via SSH.
Create a /root/.ssh directory if it doesn't already exist mkdir /root/.ssh chmod 700 /root/.ssh
Upload server/validate-rsync.sh to your /root/.ssh/validate-rsync.sh. Then chmod it so it can be run: chmod 755 /root/.ssh/validate-rsync.sh
Create an authorized_keys file for later use: touch /root/.ssh/authorized_keys chmod 600 /root/.ssh/authorized_keys
Ensure private/public key logins are enabled in /etc/ssh/sshd_config. vi /etc/ssh/sshd_config You want to ensure the following lines are uncommented: PubkeyAuthentication yes AuthorizedKeysFile .ssh/authorized_keys
You should reboot your Synology to ensure the settings are applied: reboot
Setup a share on your Synology NAS for backups (eg, 'backup').
For each client you want to backup, you will need to do the following:.
Generate a private/public key pair for the computer. You can do this by running ssh-keygen.exe, or have generate-client-keys.cmd do it for you: generate-client-keys.cmd or generate-client-keys.cmd [computername] If you run ssh-keygen.exe on your own, you should name the files rsync-keys-[computername]: ssh-keygen.exe -t dsa -f rsync-keys-[computername] If you run ssh-keygen.exe on your own, do not specify a password, or clients will need to enter it every time they backup.
Grab the public key out of rsync-keys-[computername].pub, and put it into your Synology backup user's .ssh/authorized_keys: vi ~/.ssh/authorized_keys You will want to prefix the authorized key with your validation command. It should look something like this command="[validate-rsync.sh location] [backup volume root]" [contents of rsync-keys-x.pub] For example: command="/root/.ssh/validate-rsync.sh /volume1/backup/MYCOMPUTER" ssh-dss AAAdsadasds... This ensures that the public/private key is only used for rsync (and can't be used as a shell login), and that the rsync starts at the specified root path and no higher (so it can't destroy the rest of the filesystem).
Copy backup-TEMPLATE.cmd to backup-[computername].cmd
Edit the backup-[computername].cmd file to ensure %rsyncPath% is correct. The following DOS environment variable is available to you, which is set in config.csv: %rsyncRootPath% - Remote root rsync path You should set rsyncPath to the root remote rsync path you want to use. For example: set rsyncPath=%rsyncRootPath%/%COMPUTERNAME% or set rsyncPath=%rsyncRootPath%/bob/%COMPUTERNAME% %rsyncRootPath% is set in config.csv to your Synology backup volume (eg, /volume1/backup), so %rsyncPath% would evaluate to this if your current computer's name is MYCOMPUTER: /volume1/backup/MYCOMPUTER You can see this is the same path that you put in the authorized_keys file.
Edit the backup-[computername].cmd file to run the appropriate rsync commands. The following DOS environment variables are available to you, which are set in start-backup.cmd: %rsyncStandardOpts% - Standard rsync command-line options %rsyncConnectionString% - Rsync connection string For example: set cmdArgs=rsync %rsyncStandardOpts% "/cygdrive/c/users/bob/documents/" %rsyncConnectionString%:%rsyncPath%/documents echo Starting %cmdArgs% call %cmdArgs%
Copy the client/ directories to the target computer, say C:\backup. If you are using %vcsUpdateCmd%, you can checkout the client directory so you can push remote updates (see above).
Setup a scheduled task (via Windows Task Scheduler) to run start-backup.cmd as often as you wish.
Create the computer's backup directory on your Synology NAS: mkdir /volume1/backup/MYCOMPUTER