| description |
|---|
This page describes what a "destination" is to Duplicati and lists some of the available providers |
Duplicati makes backups of files, called the source, and places the backup data at a destination chosen by the user. To make Duplicati as versatile as possible, each of the destinations are implemented as a "destination" (or "backend"), each with different properties.
Some storage providers support multiple protocols with each their strenghts, and you can generally pick which storage destination provider you like, but if there is a specific implementation for a given storage provider, that is usually the best pick.
Destinations in this category are general purpose enough, or commonly used, so they can be used across a range of storage providers. Destinations in this category are:
- File destination (any path in the filesystem)
- S3-compatible
- FTP
- SFTP (SSH)
- WebDAV
- OpenStack
- Rclone (binary required)
Storage destinations in this category are specific to one particular provider and implemented using either their public API description, or by using libraries implemented for that provider. Destinations in this category are:
- Backblaze B2
- Box.com
- Rackspace CloudFiles
- Mega.nz
- Aliyun OSS
- Tencent COS
- Jottacloud
- pCloud
- Azure Blob Storage
- Google Cloud Storage
- Microsoft Group Drive
- SharePoint
- Amazon S3
Storage destinations in this category are also specific to one particular provider, but these storage provider products are generally intended to be used as file synchronization storage. When they are used with Duplicati, the backup files will generally be visible as part of the synchronization files. Destinations in this category are:
Storage destinations in this category are utilizing a decentralized storage strategy and requires knowledge about each system to have it working. Some of these may require additional servers or intermediary providers and may have different speed characteristics, compared to other storage providers. Destinations in this category are: