Skip to main content

Create a Storage Provider

A Storage Provider in is a location where your data will be backed up. The following are a list of currently supported Storage Providers:

  • Microsoft Azure Blob Storage
  • Google Cloud Storage
  • Local Storage
  • Backblaze B2
  • Linode S3
  • AWS S3
  • SFTP
  • FTP

Creating a new Storage Provider#

Click on the Storage Providers, and press ADD STORAGE PROVIDER at the top right.

Select a Storage Provider type#

The first choice is which type of Storage Provider you are connecting to. Which one you select determines the set of inputs you will be displayed in the following modal that shows after pressing Continue.

Microsoft Azure Blob Storage#

For Azure's Blob Storage you'll need the Blob Container's name as well as the Account Name and Account Key for authentication.

Google Cloud Storage#

GCP Storage takes a bucket name and one of two methods of providing authentication. You can either insert your JSON Token directly or you can specify an absolute path to your JSON Key File, for example /home/dan/my-key-file. The absolute path method would require that key file to exist in exactly the same place on each server that uses this Storage Provider.

Local Storage#

Local Storage works differently to the rest of the Storage Providers because it does not require any connection credentials. This means you could create one instance of your Local Storage and share it between all your servers - whilst being sure to specify the backup location in the Database or File job.

You do have the option of specifying a Local Root Backup Path. This is a path that would be prepended to any job that uses this Storage Provider. For example, you could set the Local Root Backup Path to /home/dan, then in your Database Job you could set the Storage Provider Backup Path to /bakup/database/. This would result in a backup path of /home/dan/bakup/database/.

S3 Based#

If you choose either AWS S3, Linode S3 or Backblaze B2, you will need to provide the name of the bucket, your access key ID and your secret access key. Backblaze name their keys slightly different, but the usage is the same.


SFTP takes the hostname of your server, the user to authenticate as, and the port that SFTP is running on. Then you have four options for authentication:

  1. Password

    For this option you can specify a password that should be used.

  2. Key File Path

    The absolute path to the unencrypted Private Key File. Please note that any server that uses this Storage Provider will need to keep the Key File in the same absolute path location.

  3. SSH Agent

    Select this option if you have added your keys to the SSH Agent already and would like the Bakup Agent to use this method.

    To use the SSH Agent on your server, you will have to make sure it is accessible to the bakupagent user. This is the service user which the bakup agent uses to execute jobs, read the SSH Agent Guide for more details.

  4. Key PEM

    Lastly, you can paste your unecrypted Private Key and we will store it encrypted. Make sure to keep the key in the standard format with newlines. For example:



Similarly to SFTP, you must specify the hostname, user, and port for FTP. Your only authentication option with FTP is a password. If your traffic is going over public networks, we strongly recommend that you take advantage of the TLS option to make sure that no one else can read your data.