Backups & restore — Cheat Sheet

Your sites are backed up automatically — nothing to set up. This page is the quick primer: what's protecting your site right now, how to take a snapshot you can actually restore from, how to get your own data out, and how to pull an offsite copy back down. Everything here links to the full story.

What's protecting your site, in 30 seconds

Nightly database dumps — every site's database is dumped on the server each night and kept 14 days by default. → Off-site backups & mybackup
A safety copy before anything destructive — a Restore snapshots the current site first, and offsite restores land in a staging folder, so you can't lose what you have now. → Backing up and restoring in the UI
Manual snapshots, on demand — the panel's Backup and Restore tasks, whenever you want one. → same page
Encrypted offsite backups — copies pushed to your own cloud storage (hosted accounts and PRO-licensed servers). → Off-site backups & mybackup

Take a snapshot you can actually restore from

The single most useful move on this page. Run the panel's Backup task: the form opens on "Site files with classic mysqldump DB" — the complete snapshot the Restore task can rebuild a whole site from. The two partial modes save the database only or the site files only; each restores exactly what it holds (the task log says plainly what came back and what was left as it was), and partial snapshots are labelled as such in your backup lists.

→ Backing up and restoring in the UI

Roll a site back

Run the panel's Restore task and pick a backup. Before it changes anything, BOA takes a fresh snapshot of the site as it is right now — labelled "Generated before being restored to a previous version" — so a restore can never cost you your current state.

→ Backing up and restoring in the UI

Export your site yourself — no ticket

From your site's limited shell (oN.ftp), pull the database out in one line, or copy the whole site directory home:

BASH

ssh [email protected] 'drush @example.com sql-dump' > dump.sql
rsync -avzuL [email protected]:clients/myclient/example.com ./

Use drush11 on Drupal 8+ — a bare domain keeps the same alias (@example.com); a multi-dot name hyphenates every dot but the last (@sub-example.com). The -L on rsync is not optional — without it you copy dead symlinks instead of your files.

→ Exporting your site · Shell & SFTP access

Pull an offsite backup back down (hosted & PRO)

Off-site backups come with every hosted account (self-hosted servers need a BOA PRO licence). If they're switched on for you, fetch one from your own oN.ftp shell. This is restore-only — there is no backup verb, because the offsite copies are made for you automatically:

BASH

mybackup restore <SERVICE> [RESTORE_PATH] [RESTORE_TIME]

The job is queued, you're emailed when it finishes (if your account has an email address on file), and everything lands in ~/static/restores/ — it never overwrites your live files. Keep your encryption passphrase safe: a lost one can't be reset, and the offsite copies can't be opened without it.

→ Off-site backups & mybackup

Trim retention to free up quota

The nightly dumps count against your disk quota. Shorten how many days are kept with a one-line control file — the whole number is days to keep:

BASH

echo 7 > ~/static/control/dBackupCycle.info

An empty or missing file means the default 14; anything that isn't a plain number from 1 to 9999 is ignored and the cleanup runs on the default instead. → Off-site backups & mybackup

The files and dials most people touch

File / setting	What it controls	Default
`~/static/control/dBackupCycle.info`	Days of nightly DB dumps kept before pruning	`14`
Panel Backup Mode (Backup task)	Which snapshot you get — the complete mode is preselected; partial snapshots are labelled in the lists	(opens on files + classic DB)
`~/static/control/remote_backups/credentials/<service>.txt`	Switches on encrypted offsite backups for one provider	(none)
`~/static/control/MyQuick.info`	Fast per-table dumps — the archive then has no single `database.sql`	(on by default; opt out via `MyClassic.info`)

The full set lives on the backup pages: the 3 panel Backup Modes, the 11 cloud-storage services mybackup understands, and the 4 offsite fine-tune files (include.txt, exclude.txt, and their *_regexp.txt pair). See Backups on your sites and the control-files reference.

If something's weird

Restore brought back less than you expected. The archive was a partial one — the task log states which half was restored and which was left as it was; take future backups in the complete mode (the form default); what each mode restores.
The archive has no database.sql. Fast per-table dumps were used → rebuild from a classic-mode Backup, or export with drush @site sql-dump; exporting your site.
Not sure the nightly or offsite schedule is firing? That's a host-side check → start here, or ask your host.

Going deeper

The whole topic, in depth: Backups on your sites — the UI tasks, mybackup and quotas, how your files are stored, and exporting everything.
Moving a site instead of restoring one: Cloning & migrating · Importing a site.
The backup engine and retention internals (for operators): Backups internals · Retention · multiback operations.