Destination
For individual types of backup destinations, please read the following notes for important setup details and troubleshooting tips.
Local/remote backup destination:
- New external drives might need to be formatted before serving as the backup destination.
- Before creating a backup task, make sure you have already attached the external drives properly to your Synology NAS. You can go to Control Panel > External Devices to check the status of the USB/eSATA drives. External drives cannot be selected as the backup destination if the external drive is being initialized, formatted, or is malfunctioning.
- Remote mounted shared folders cannot be selected as the backup source or destination.
- If an encrypted shared folder is unmounted, it cannot be chosen as backup destination.
- The file system of the destination supports ext4, Btrfs, FAT, NTFS, HFS+, and PetaSpace.
- The following shared folders cannot be selected as a backup destination: photo, surveillance, home, and homes.
- You can set the access privilege of a backup task by editing the permission of the backup destination folder via File Station:
- A user is allowed to restore data from a backup destination, if he has read privilege to each file/folder in the backup destination folder.
- A user is allowed to delete backup versions from a backup destination, if he has write privilege to each file/folder in the backup destination folder.
- Only the backup task owner can perform Back up now. The default owner of a backup task is the user who created the task. You can change the owner of a backup task by editing the owner of the backup destination folder via File Station.
- A task owner cannot be a group.
Remote rsync backup destination:
- The following modes are available when creating a backup task with rsync-compatible servers as the network backup destination: rsync daemon mode, which is used when you select a backup module (shared folder on the rsync-compatible server) from the drop-down menu next to Backup module; and remote shell mode, which is enabled only when you enter an absolute path (starting with "/") in Backup module.
- If you want to access a destination server over the Internet using its hostname, the hostname must be an FQDN (Fully Qualified Domain Name), for example abc.bcd.com.
- When backing up from one Synology NAS device to another, you are prompted to enter the username and password for an account at the destination. When backing up to shared folders on another Synology NAS, you can do so according to the access privilege settings of the folders. Only shared folders to which the specified user account has access privileges will be visible. If you cannot find the desired shared folder at the destination, please check your access privileges.
- Transfer encryption is supported only when the destination server supports encrypted network backup and authentication password is not empty.
- Remote shell mode only supports transfer encryption.
- If you are backing up files to a Synology NAS device through an rsync client, the file names must be in UTF-8 encoding.
- If you are backing up files from your Synology NAS to an rsync-compatible server, you will need to input the correct rsync backup account name and password. You will also need to choose the correct backup module with Write privilege.
Synology C2 Backup backup destination:
- To back up files onto Synology C2 Backup service, you must have a Synology Account.
- Backup task will start after your authorization to Synology C2 service.
- Every task name must be unique and can contain 1 to 32 Unicode characters, except the following:
~ ` ! @ # $ % ^ & * ( ) - _ = + [ { ] } \ | ; : ' " < > / ?
- Once the backup task is set up with the client-side encryption enabled, you can no longer disable the client-side encryption, and the password is not changeable as well. For better backup performance, data compression is always enabled.
- If you select Enable client-side encryption, your password/encryption key is required to restore data on the Synology C2 Backup web page. Loss of password/encryption key will result in permanent loss of backed up data.
- Version lock may not be supported during the Beta program.
- Retention policy for backup versions stored on Synology C2 service during the Beta program:
- Retain the latest version of each day in the past 7 days.
- Retain the latest version of each week in the past 30 days.
WebDAV backup destination:
- Backup files are stored in the Folder selected on the WebDAV server, put to directory of your choosing.
- The default server address automatically starts with the http:// prefix (e.g. http://SERVER_ADDRESS:5005/PATH).
- For encrypted connection, the server address should start with the https:// prefix (e.g. https://SERVER_ADDRESS:5006/PATH).
- Some backup files may not contain specific filename extensions; therefore, WebDAV server supports all files either with or without filename extensions.
- When setting up WebDAV server via Internet Information Services on Windows, please add . and .* filename extensions to MIME type.
Amazon S3 backup destination:
- When creating backup tasks with Amazon S3 server as the network backup destination, various options are available, such as transfer encryption, backup to Amazon S3 RRS (Reduced Redundancy Storage), and others. Please note that some options, like transfer encryption, might reduce the speed of backup tasks.
- Backup files are stored in the Bucket selected on the Amazon S3 server, and the set Key value begins with a directory name of your choosing.
- Only the modified/added data chunks will be backed up to Amazon S3 server.
- Each Bucket on Amazon S3 must have a unique name. In addition, the name should:
- be in the range of 3 to 63 characters.
- contain only lowercase letters, numbers, periods (.), and dashes (-).
- start and end with a number or a letter, and cannot end with a dash (-), contain two adjacent periods, or contain dashes next to periods (e.g., "my-.bucket.com" and "my.-bucket" are invalid).
- The maximum length of an Amazon S3 KEY is 1024 characters. To ensure successful backup to Amazon S3 for single-version tasks, the maximum path length is 1024 minus the destination folder name combined with the filename.
- Storage class supports Amazon S3 Standard, Amazon S3 RRS (Reduced Redundancy Storage), and Amazon S3 Standard - Infrequent Access (Standard - IA):
- If you enable Amazon S3 RRS support, only data modified subsequently will be backed up to the RRS storage; in other words, data already backed up to Amazon S3's standard storage will not be backed up to RRS again.
- If you enable Amazon S3 Standard - IA support, only the data content will be backed up to the Standard - IA storage, and the rest (e.g. configuration file and index) will backed up to Amazon S3's standard storage.
- Moving backed up files from Amazon S3 to Amazon Glacier is not supported. If files are moved from Amazon S3 to Amazon Glacier via the AWS Management console, the related backup tasks might fail.
- Backing up files to virtual hosted-style buckets with SSL is not supported.
- When transferring a file, the file will be split into parts. The part size can be set by the option Multipart Upload Part Size in task settings with 512MB as the default size. If the network environment is not stable, the option is recommended to be a smaller number.
Microsoft Azure backup destination:
- When creating backup tasks with Microsoft Azure server as the network backup destination, various options are available, (e.g. transfer encryption). Please note that some options, like transfer encryption, might reduce the speed of backup tasks.
- Only the modified/added data chunks will be backed up to Microsoft Azure server.
- Each Container on Microsoft Azure must have a unique name. In addition, the name should:
- be in the range of 3 to 63 characters.
- contain only lowercase letters, numbers, and dashes (-).
- start and end with a number or a letter, and cannot contain two adjacent dashes.
- The maximum length of an Microsoft Azure Blob Name is 1024 characters. To ensure successful backup to Microsoft Azure for single-version tasks, the maximum path length is 1024 minus the destination folder name combined with the filename.
- The authentication failure warning message may be caused by the incorrect authentication information, a network connection problem, or the time on your Synology NAS and the remote server do not match. To check the time setting on your Synology NAS, please go to Control Panel > Regional Options > Time to synchronize time with the NTP server.
OpenStack Swift backup destination:
- Backup files are stored in the Container selected on the OpenStack Swift server, put to directory of your choosing.
- The data structure of OpenStack Swift includes a pair of Container and Object without any folder structure.
- Each Container on OpenStack Swift must have a unique name, and the naming should follow the rules below:
- Its length must be between 1 and 256 characters.
- No slash (/) character should be used.
IBM Softlayer backup destination:
- Backup files are stored in the Region and Container selected on the IBM Softlayer server, put to directory of your choosing.
- IBM Softlayer uses the OpenStack Swift protocol for data transfer.
- The data structure of IBM Softlayer includes a pair of Container and Object without any folder structure.
- Each Container on IBM Softlayer must have a unique name, and the naming should follow the rules below:
- Its length must be between 1 and 256 characters.
- No slash (/) character should be used.
Rackspace backup destination:
- Backup files are stored in the Region and Container selected on the Rackspace server, put to directory of your choosing.
- Rackspace uses the OpenStack Swift protocol for data transfer.
- The data structure of Rackspace includes a pair of Container and Object without any folder structure.
- Each Container on Rackspace must have a unique name, and the naming should follow the rules below:
- Its length must be between 1 and 256 characters.
- No slash (/) character should be used.
Amazon Drive backup destination:
- Amazon Drive uses OAuth 2.0 for authorization.
- Backup files are stored in the folder chosen in the Amazon Drive server.
- Each folder in Amazon Drive must have a unique name, and must not contain any special characters.
- Connections with Amazon Drive are encrypted by default.
Dropbox backup destination:
- Dropbox uses OAuth 2.0 for authorization.
- Backup files are stored in the Folder selected on the Dropbox server, put to directory of your choosing.
- Each Folder on Dropbox must have a unique name, and the naming should follow the rules below:
- Its length must be between 1 and 256 characters.
- No slash (/) or backslash (\) character should be used.
- Connection with Dropbox is encrypted by default.
Google Drive backup destination:
- Google Drive uses OAuth 2.0 for authorization.
- Backup files are stored in the Folder selected on the Google Drive server, put to directory of your choosing.
- Each Folder on Google Drive must have a unique name, and the naming should not use any slash (/) character.
- Connection with Google Drive is encrypted by default.
hubiC backup destination:
- Backup files are stored in the Container selected on the hubiC server, put to directory of your choosing.
- hubiC uses OAuth 2.0 for authorization, and uses the OpenStack Swift protocol for data transfer.
- The data structure of hubiC includes a pair of Container and Object without any folder structure.
- Each Container on hubiC must have a unique name, and the naming should follow the rules below:
- Its length must be between 1 and 256 characters.
- No slash (/) character should be used.
HiDrive backup destination:
- Backup files are stored in the Folder selected on the HiDrive server, put to directory of your choosing.
- Connection with the HiDrive server is encrypted by default.
- For detailed information of how to set up a STRATO HiDrive account, refer to this article.
- Connection with HiDrive uses the rsync protocol for data transfer. In this way, free HiDrive accounts are not supported. Please refer to the product specifications.
SFR NAS Backup backup destination:
- When creating backup tasks with SFR NAS Backup server as the network backup destination, various options are available, such as transfer encryption, and others. Please note that some options, like transfer encryption, might reduce the speed of backup tasks.
- Backup files are stored in the Bucket selected on the SFR NAS Backup server, and the set Key value begins with a directory name of your choosing.
- Only the modified/added data chunks will be backed up to SFR NAS Backup server.
- Each Bucket on SFR NAS Backup must have a unique name. In addition, the name should:
- be in the range of 3 to 63 characters.
- contain only lowercase letters, numbers, periods (.), and dashes (-).
- start and end with a number or a letter, and cannot end with a dash (-), contain two adjacent periods, or contain dashes next to periods (e.g., "my-.bucket.com" and "my.-bucket" are invalid).
- The maximum length of an SFR NAS Backup KEY is 1024 characters. To ensure successful backup to SFR NAS BACKUP for single-version tasks, the maximum path length is 1024 minus the destination folder name combined with the filename.
- When transferring a file, the file will be split into parts. The part size can be set by the option Multipart Upload Part Size in task settings with 64MB as the default size. If the network environment is not stable, you are recommended to set a smaller number.
hicloud S3 backup destination:
- When creating backup tasks with hicloud S3 server as the network backup destination, various options are available, (e.g. transfer encryption). Please note that some options, like transfer encryption, might reduce the speed of backup tasks.
- Backup files are stored in the Bucket selected on the hicloud S3 server, and the Set KEY Value begins with a directory name of your choosing.
- Only the modified/added data chunks will be backed up to hicloud S3 server.
- Each Bucket on hicloud S3 must have a unique name. In addition, the name should:
- be in the range of 3 to 63 characters.
- contain only lowercase letters, numbers, periods (.), and dashes (-).
- start and end with a number or a letter, and cannot end with a dash (-), contain two adjacent periods, or contain dashes next to periods (e.g., "my-.bucket.com" and "my.-bucket" are invalid).
- The maximum length of an hicloud S3 KEY is 255 characters. To ensure successful backup to hicloud S3 for single-version tasks, the maximum path length is 1024 minus the destination folder name combined with the filename.
- When transferring a file, the file will be split into parts. The part size can be set by the option Multipart Upload Part Size in task settings with 512MB as the default size. If the network environment is not stable, it is recommended to set a smaller number.
Other S3-compatible backup destinations:
- To use other S3-compatible clouds, enter the IP address/domain of the desired S3-compatible cloud in the S3 Server field when prompted.
- If there is any usage issue, please refer to the relevant documentation or contact the S3-compatible cloud service provider.
- Google Cloud Storage can also serve as an S3-compatible backup target with the interoperability option enabled.
Note:
- When backing up files to cloud-based destinations, local index will occupy 1% to 4% storage usage in the same volume shared by Hyper Backup.