Storage
Where backups are sent — the S3 buckets, FTP/SFTP servers and Google Drive accounts this server can write to.
Integrations → Storage holds the places this server is allowed to send backups. Connect a destination once here, then choose it on each application you protect.
Each row shows the provider, the path or bucket, the account it connects as, and
when the connection was last tested. Test re-runs the check on demand; the
… menu edits or removes the destination.
Saving a destination tests it as part of the save, so a destination that saved cleanly already works. The row still reads Never tested until you press Test once yourself — that column records your tests, not the panel's.
Connecting one
The full walkthrough — every provider, every field, and what the panel refuses to connect to — lives with the feature that consumes it:
Storage destinations
S3, FTP, SFTP and Google Drive: the form end to end, with the credentials each one needs.
Turn backups on
Point an application at a destination and choose how often it is copied.
Worth knowing
- Destinations are server-wide. Every application on this server can be pointed at any of them; they are not owned by one site.
- Removing a destination does not delete the archives already sitting in it. It only stops this server writing more. An application still scheduled to use it will start failing its backups.
- The panel's own database is never sent here. It is backed up separately by the update script. See Backups.
- Adding, editing and removing needs Storage · Manage.