Site Backups

This guide aims to help you set up automated daily site backups. Site backups are full backups of your site files (media, themes, and plugins) and database.

Daily Backups

Before you can enable site backups, you must add a storage provider, which are cloud storage providers where your backup files will be stored. Navigate to the Backups tab under a site and click Add Storage Provider.

Add storage provider

SpinupWP currently supports Amazon S3, DigitalOcean Spaces and Google Cloud Storage. To quickly get started with your preferred storage provider, please follow the appropriate guide from the following list:

Amazon S3
DigitalOcean Spaces
Google Cloud Storage

Once you’ve created your provider, enter the bucket name and region where you would like backups to be stored. The bucket must already exist on your chosen storage provider before entering it on SpinupWP.

Select a retention period (in days), which is the length of time to keep backups on your chosen storage provider. When a backup is older than the retention period, it will be removed.

Site Backups

Site backups are carried out at 1AM UTC every day. Backups are carried out in a rolling fashion. Meaning, that servers with multiple sites that have backups enabled will only carry out one site backup at a time. This is to prevent overloading your server’s system resources. Therefore, even though site backups are queued at 1AM UTC, not all backups will be started instantly.

Daily Database Backups

With daily database backups turned on, your database will be exported as an SQL file, gzipped, and saved to your storage provider in the following location:

{BUCKET}/{DOMAIN}/{DATE-DATABASE_NAME}.sql.gz

Daily Database Backups

Daily File Backups

With daily file backups turned on, all files and folders within the site’s root folder will be balled up into an archive file (tar) and compressed (gzip).

{BUCKET}/{DOMAIN}/{DATE}-files.tar.gz

Daily File Backups

Paths to Exclude

There may be files or folders that you do no wish to include in your file backups. For example, if you’re using WP Offload Media to offload your Media Library there’s no reason to include those files in your daily backups because they’re already stored offsite. In this case excluding your uploads folder may make sense:

Exclude uploads directory

Similarly, if you’re using Composer to manage PHP dependencies, it’s likely that you don’t want to include the root vendor directory in your backups.

Exclude composer vendor directory

It’s also possible to exclude certain file types. For example, MP4 video files:

Exclude MP4 files

The following paths are automatically excluded from all backups:

/sites/{DOMAIN}/logs
/sites/{DOMAIN}/.bare_repo
/sites/{DOMAIN}/.bash_logout
/sites/{DOMAIN}/.bashrc
/sites/{DOMAIN}/.cloud-locale-test.skip
/sites/{DOMAIN}/.composer
/sites/{DOMAIN}/.profile
/sites/{DOMAIN}/.repo
/sites/{DOMAIN}/.ssh

Paths which you manually exclude will be appended to this list.

On-Demand Backup

There may be times when you wish to trigger a backup instantly. This is useful if you’re making changes to your site and wish to take a snapshot before deploying any changes. You can perform an on-demand backup at anytime. Navigate to the backups tab on the site screen and click Backup Now.

Full Server Backups

SpinupWP doesn’t provide full server backups or snapshots (as they’re also known). We believe that these types of backups are best performed by your server provider (DigitalOcean, etc). Full server backups can be enabled when provisioning a new server in SpinupWP (for supported providers). Alternatively, they can be enabled via your server provider’s control panel at anytime.

Full server backups

Manage Storage Providers

Storage providers are attached to your personal account or a team account. Here you can add, edit or delete storage providers.

Manage storage providers

Ready to give SpinupWP a try?

Not sure if SpinupWP is the right fit for you? Send us an email at sudo@spinupwp.com and we’ll give you our no-BS opinion.