How to add an external backup destination (off-server backups)
A destination is a place where backup jobs put their copies. This server is always a destination. Add an external one so your backups survive if the server itself is lost. You can add as many destinations as you like and use a different one for each backup job.
Before you start
- You need the administrator panel (
https://<server>:2087). Resellers and customers cannot add destinations. - Have the storage ready: a bucket and access key, an SFTP or FTP login, or a Google, Microsoft or Dropbox account.
Steps
- Open Backup Jobs in the menu (section Websites).
- Under Destinations, click Add destination.
- Name — a name you will recognise, for example
Backblaze B2. - Storage — choose one of:
- S3-compatible (Amazon S3, Backblaze B2, Wasabi, Cloudflare R2, MinIO…) — see back up to S3-compatible storage
- SFTP server or FTP server (TLS) — see back up to an SFTP or FTP server
- Google Drive, Microsoft OneDrive or Dropbox — see back up to Google Drive, OneDrive or Dropbox
- Fill in the fields for that kind of storage and the folder (Bucket and folder (S3) / folder,
backupsby default). - Click Save.
- For S3, SFTP and FTP the connection is tested at once and the result is shown at the top of the page, for example "Connected: the folder is reachable and writable."
- For Google Drive, OneDrive and Dropbox you are asked to Connect the account next.
- Open a backup job (or create one), choose the new destination under Destination and click Save.
Good to know
- Passwords and secret keys are stored encrypted and never shown again. When you edit a destination, leave Secret key / password empty to keep the saved one.
- Click Test next to a destination at any time to check that the folder is still reachable and writable.
- A destination that is not connected shows Not connected and cannot be chosen in a backup job.
- To an external destination, each run sends one archive per account. The archive is not kept on the server; a restore fetches it. If sending fails, the archive is kept on the server instead and the backup shows external copy failed.
- On the destination, archives are stored as
<folder>/<account>/<account>-<date>-<time>-<id>.tar, each with a file list next to it (.files.gz). - Removing a destination is possible only when no backup job uses it. Copies already stored there are not deleted.
Common questions
Can I send different jobs to different destinations?
Yes. Each backup job has its own Destination. For example, databases every hour to this server and a full copy every night to external storage.
Can I keep the same copy both on this server and externally?
Not with one job: a job to an external destination does not keep its archive on the server. Make two jobs, one to This server (incremental) and one to the external destination.
Which storage should I choose?
S3-compatible object storage is usually the cheapest and fastest for many archives. An SFTP server you already own works as well. Google Drive, OneDrive and Dropbox suit small servers with few accounts.
Thank you — this helps us improve the article.
Still stuck?
Ask the AI about your exact situation — it answers from this knowledge base — or contact us.
Related articles
- How to back up to S3, Backblaze B2, Wasabi or Cloudflare R2
Store backups in an S3-compatible bucket (Amazon S3, Backblaze B2, Wasabi, Cloudflare R2, MinIO): the endpoint, keys, bucket and region to enter.
- How to back up to your own SFTP or FTP server
Send backup archives to your own SFTP or FTP server: the host, port, login and folder to enter, and what the FTP server must support.
- How to back up to Google Drive, OneDrive or Dropbox
Connect a Google Drive, Microsoft OneDrive or Dropbox account as a backup destination by signing in once in the browser and pasting back the address.
- How to create a backup job (schedule automatic backups)
Schedule automatic backups of files, databases and email — from every 15 minutes to monthly — with how many copies to keep and where to store them.