SnapShooter Backup Engine

# Overview

SnapShooter have developed a custom engine to facilitate backing up hosted resources to S3-based storage.

Learn how to use SnapShooter's object storage-based backups to backup your data off-site with the provider of your choice.

# Supported Backup Types (Recipes)

• Server File
• Laravel (MySQL)
• Ghost
• MySQL All Databases
• MySQL (Single Databases)
• PostgreSQL (Single Databases)
• WordPress
• MongoDB (Single Databases)
• TYPO3
• Laravel (PostgreSQL)
• GridPane
• Multiple WordPress
• Laravel Forge Whole Server (MySQL)
• UniFi Cloud Controller
• S3 Sync
• Craft CMS (MySQL)
• SpinupWP
• DigitalOcean Managed MySQL (Single Databases)
• Server Disk Cloning
• FTP
• Github
• AWS RDS Aurora MySQL
• AWS RDS MySQL Community
• AWS RDS Mariadb
• ScaleGrid MySQL
• UpCloud Managed MySQL (Single Databases)
• DigitalOcean Managed PostgreSQL
• UpCloud Managed PostgreSQL
• Incremental File

If we don't support what you need, let us know we can easily add more types.

# Private Custom Backup Types

Some customers require custom backup types for their platforms and requirements. We have deployed a number of these for managed hosting providers. If you're interested in a custom type for your team, please get in touch with support.

# Supported Storage Providers

• AWS
• DigitalOcean Spaces
• Backblaze
• Wasabi
• Custom
• Filebase
• Upcloud
• SnapShooter S3

With our custom driver you can add your own storage provider, such as MinIO

Requirements:

• Supports multi-part uploads

# Rclone

We add an Rclone binary to your server, which is self-contained and does not require the installation of any libraries. We keep a copy of rclone in your server's tmp folder. We check its version before every backup against the version SnapShooter has dictated to use and update if required.

We use this for the smooth uploading of backups directly to your storage provider of choice. It enables us to avoid installing AWS CLI which comes with a lot of library dependancies.