V2 Backups Part 3. Setting Up Remote Website Backups

7 min read

Currently the new backup system is BETA only. 

Please do not rely on Beta Backups V2 for your production websites. By running these backups you are agreeing to also maintain separate comprehensive third-party backups of all sites with Backups V2 enabled.

Any ticket submitted for a website with a Backups v2 issue will be treated primarily as a bug report and there is no critical/urgent support or support guarantees.

Activating V2 Backups

To activate backups 2.0 head to your Servers page and click on the name of the server you wish to activate it on.

Warning: This will disable Borg and purge all existing Borg backups from your system. You are responsible for ensuring you have existing backups in place. By enabling Backups v2 you accept full responsibility for this action and confirm you have alternative backups in place. Only enable if you agree to these conditions. Once enabled, this can not be disabled. Borg is going back to the Delta Quadrant.


GridPane’s remote backup system allows you to back your websites up at four different external providers. We recommend three types of backups for your security and ability to recover from worst case scenario type situations: –

  1. Full server backups at your IaaS provider
  2. Local website backups directly on your server
  3. Remote backups so you have completely separate backups at a secure third party

A backup or several on your local machine isn’t a bad idea either. We highly recommend you take advantage of the remote backup options available to you. Storage at each of these providers is relatively inexpensive – especially Backblaze and Wasabi.

Setup Your API Credentials

You can choose from four different providers – Backblaze, Wasabi, Amazon S3, and Dropbox. To get started, below are links that will help you create and then set your API keys inside your GridPane account: –

  1. Create and Set Your Backblaze B2 API Credentials
  2. Create and Set Your Wasabi API Credentials
  3. Create and Set Your Amazon S3 API Credentials
  4. Create and Set Your Dropbox API Credentials

Getting Started with Remote Backups

To get started, head over to the Sites page in your account:

Then click on the name of any of your websites to open up the site configuration modal, and navigate through to the backups tab.

Here you’ll see the new options available for the new backup system. You’ll see both local and remote options are located in this tab, and you can learn more about local backups in this article:

Local Website Backups


You must select your backup provider as shown in the section below if you want to activate automatic backups. We regularly get support tickets that remote backups cannot be activated, but this is always due to no backup provider being specified.

Set Your Backup Provider/s

Before you can setup your remote backups you need to have API keys added to your account. If you haven’t done this yet, please choose a provider and follow the articles linked above to get your API keys created and added to GridPane.

Once you have API keys configured, you will be able to select your provider from the “Select Remote Storage Provider” dropdown.

Choose your provider, choose the specific API key you wish to use, and click the “Add Remote Storage” button.

This will immediately create a remote backup of your website.

Once this has finished you will be able to set up automatic backups and take manual backups, and the restore and purge options for your remote storage option will then become available.

Automatic Backups

You have the option to set your remote backups on an automatic schedule. This can be set at any of the following intervals:

  1. Hourly
  2. Daily
  3. Weekly
  4. Monthly

Select your preferred schedule from the dropdown, then choose the specific time you would like backups for this website to take place.

Once you’ve configured your choices, hit the Update button to confirm.  If you’re unsure about what time to choose, simply select the start of the hour.

Backups will then take place automatically according to this schedule.

Setting the Backup Schedule with GP-CLI

To set your local backup schedule via GP-CLI instead of the UI, you can use the following commands. You’ll also need to swap out “{storage.provider}” with the correct syntax as well like so:

  • aws-s3
  • backblaze
  • wasabi
  • dropbox

These providers will also need to be attached to the site first for this to work. As this involves API keys, this is better done inside the UI.

Hourly Syntax:

gpbup2 site.url -set-backup-time {storage.provider} hourly {minute}

For example, this would set the backup time at 30 minutes past the hour using Dropbox:

gpbup2 example.com -set-backup-time dropbox hourly 30

Daily Syntax:

gpbup site.url -set-backup-time {storage.provider} daily {hour} {minute)

For example, this would set the backup time to 2.36am using Backblaze B2:

gpbup example.com -set-backup-time backblaze daily 2 36

Weekly Syntax:

gpbup2 site.url -set-backup-time {storage.provider} weekly {hour} {minute} {day}

Here, the first day of the week is Sunday, which is “0”. Monday is “1”, Tuesday “2”, etc. For example, this would set the backup time as 23.05 on a Sunday using Wasabi:

gpbup2 example.com -set-backup-time wasabi weekly 23 5 0

Monthly Syntax:

gpbup2 site.url -set-backup-time {storage.provider} monthly {hour} {minute} {day}

For monthly backups the day has to be between the 1st and 28th day of the month. For example, the following would set the backup time to 20.00 on the 14th day of each month using AWS S3:

gpbup2 example.com -set-backup-time aws-s3 monthly 20 0 14

Manual Backups

You can remotely backup your websites manually any time you need to do so.

You can also tag your backup to make it easily identifiable if you later need to use it to restore your website. 

Restoring from a Remote Backup

If you ever need to restore one of your websites from a remote backup you can do so quickly and easily. Below the remote backup options you’ll find the Restore options.

Select remote from the first dropdown, then choose either automatic or manual from the second, and then choose the backup you wish to restore from in the third dropdown.

When you’ve selected your backup hit the “Restore Now” button.

If you’re not seeing the backup you’re looking for, hit the “Refresh” button to get ensure all of the latest backups are available for you to view.

Restoring on a Different Server

If you’re restoring a backup of your website to a different server, the steps below make this quick and simple.

Step 1. Create a site with the same domain

To restore a remote backup from a different server, first create a site with the same domain (if you want to change the name after you can do this easily by either cloning the site or using the primary domain change function).

Step 2. Fetch all potential sources

Open your sites customizer and click through to the Backups tab.

Here you will see a big blue button labeled “Fetch All Potential Sources“. Click the button to run a search for other servers that host the same domain.

Step 3. Select Your Server and Provider

Now you can select the server and specific backup provider you want to restore from.

Click the “See What’s Available” button.

If you need to, you can also refresh the available sources by clicking the Refresh Sources button.

Step 4. Select and Restore

Now select your desired backup and hit the restore.

Further Reading

For further information about how backup systems work, the available options for configuring them, and for setting up remote backups (available on V2), please see the articles listed below.


Recommended Backup Strategy

V2 Backups

V1 Backups