Backup the Synology server to a remote Synology server or RSync Server
From SynologyWiki
This is a guide on how to use the Synology function Network Backup.
Network backup is a function where one Synology server can backup to another Synology server via the network interface. This function is designed to operate over a LAN or a WAN Network connection and is beneficial for offices that wish to insure that their data is protected by fire, flood, vandalism or some other catastrophic event.
To use this function for Internet use, please forward ports 873, (and 22 for encryption) for the remote Synology product.
Note: This guide will be covering backing up to a Synology Server to another Synology Server.
Backing up/Restoring data from a RSync Compatible Server uses the same procedure as backing up to a Synology Server however it requires different information. For further clarification about what information is different, please look here.
Contents |
Setting up Network Backup
How to restore data via Network Recovery
Backup the Synology Server to a remote RSync Compatible Server
|
When selecting RSync Compatible Server from the server type, either creating a Network Backup task or performing a Network Recovery the menu will change to show the reflected image on the right hand side. Please fill in the information as follows.
| |
|
After this information has been entered in, continue on with the task that is being executed, with the remaining steps from the above guides. |
Backup Procedure Failure & Error Messages
The rsync backup process has a directory & file path name limitation imposed by Linux of 1024 bytes, in windows it is 248 bytes. The synology servers use 58 bytes for the servername_MacAddress path record. Hence the following rules apply to rsync backups:
- Any files where the path exceeds 996bytes (=1024-58) will NOT be backed up and the procedure will finish reporting backup failed. It will be reported by email (if configured) and in the Network Backup log.
- Any files where the path exceeds 190bytes (=248-58) will be backed up and a warning listed in the Network Backup log. You can check the existence of those files using FTP, but if you browse them by Samba they will be invisible as samba does not support such long file pathnames.
To view the directory&filename path lengths;
- Create a file containing all the files names with their full paths, i.e.
- For Windows - Map a network drive to the Synolgy Server folder containing the data you want to rsync. Open the command prompt (DOS) change to the mapped network drive (e.g. enter the command "m:" for drive m), make sure you are at the root of it (i.e. enter "cd \") and then enter the command "dir /a/s/b > list.txt" which will create a file called list.txt in the root of m:
- For Linux - Lets assume your errors are when backing up your music folder, enter the command "cd /root" and the use the command "find /volume1/music -name * > /volume1/music/list.txt" to create a file /volume1/music/list.txt. Note: we changed to "/root" because the find command sometimes produces errors if you are not in "/root".
- Open the file list.txt in a spreadsheet program (e.g. excel) and use the string length function (LEN in excel) to display the number of characters in each filename path, and then sort the results to find the the longest culprits.
Notes
- With Network Backup the initial backup will always be a full backup, where all content from one server will be replicated to the secondary server. Subsequent backups will be incremental, where only modified data will be replicated to the backup server.
- Suggested strategy: It's recommended to perform the initial (or full) backup while both servers are within a LAN. Afterwards, move the backup server to the remote location. Once the backup server is online at the remote location, reconfigure the first server to the new IP address of the secondary server, and then incremental backups can take place. This way, it avoids saturating the Internet bandwidth for the initial backup.
