Techie GainInfrastructure Operations Platform
Free trial

Set Up Backups

Choose what to back up, where the copies go and how often, then run a first backup. Archives go straight to your storage, never to the platform.

Before you start: A connected server, and somewhere to store the copies.

  1. 1

    Add a backup source

    On Backups, under Operations, What is backed up lists your sources. Add source asks for a name, the server, and a directory, a MariaDB, MySQL or PostgreSQL database, or both. No database password is needed: the server’s own administrator access is used.

  2. 2

    Add backup storage

    Backup storage supports Dropbox, Amazon S3, Backblaze B2, DigitalOcean Spaces, Hetzner Object Storage, Wasabi, Cloudflare R2, any other S3-compatible storage, or the server itself. Dropbox is connected with a button and needs no keys; the S3 providers need an access key and secret. A copy kept on the server is lost if the server is lost, and the page says so.

  3. 3

    Create a schedule

    Under Automatic backups, choose New schedule: the source, the destination, daily or weekly, and how many copies to keep. A full backup copies the directory and the database; database only is small enough to run more often.

  4. 4

    Run a backup now

    Back up now starts a backup immediately. It can take a few minutes and appears in Backup history while it runs. A finished backup downloads as .tar.gz directly from your bucket, or as .zip converted on your server first.

  5. 5

    Restore a backup

    Restore checks the archive against its recorded checksum before changing anything, moves current files aside rather than deleting them, and asks you to type the source name to confirm. A backup in cloud storage can be restored to a different server, which moves the source there.