Docs · Guides

Guides

Docs is how to operate Reaver Backup. Guides is how to choose an approach — plugin vs server, one dashboard for many sites, restic without glue scripts — and why this architecture exists.

Read the docs First backup

Docs

How to operate Reaver Backup

Install, agents, schedules, restore, destinations, API, MCP. Procedural, on purpose.

Open documentation

Guides

How to choose an approach

Who this is for, who should stay on a plugin, and what “easy backups you host yourself” actually means.

You are here

Start here

Ready to try it

Your first backup with Reaver Backup

Five steps, about 15 minutes: install, connect a server, pick storage, run a backup, confirm a snapshot you can restore.

How do I install Reaver Backup and take a first WordPress backup?

Choosing an approach

Site owners after a scare

Plugin backups vs server-level backups

Three layers: a plugin inside WordPress, a host snapshot you do not control, and a server agent that still runs when WP is dead.

Restore when wp-admin will not load; plugin vs host backups.
Agencies, freelancers, and operators with several WordPress sites

Many WordPress sites, one dashboard

One agent per server. Auto-discover from Nginx or Apache. Site-pack pricing instead of logging into forty wp-admins.

How do I back up all my client WordPress sites from one place?
Self-hosters and operators who already trust restic (or want restic under a UI) for WordPress on Linux

Restic WordPress backups without glue scripts

The dump + files + forget loop you already know, with discovery, schedules, retention, and a restore UI.

How do I run restic WordPress backups to B2 or S3 without maintaining cron scripts?
Switchers

Coming from UpdraftPlus, BlogVault, or BackupBuddy

Same job — schedule, offsite, restore. Different control plane: no plugin on every site, storage you choose, no vendor vault.

Self-hosted UpdraftPlus or BlogVault alternative that stores files on storage I own?

When it matters

Operators with vhosts Coming soon

Auto-discover WordPress on Nginx or Apache

We read sites-enabled (server_name + root), then wp-config.php for the database. Anything else is a path you point at.

How does Reaver Backup find my WordPress sites?

Anyone who has been locked out

Restore when wp-admin is dead

Plugin restore assumes WordPress boots. Walk a white screen, malware, or a blown database from the dashboard instead.

How do I restore WordPress when wp-admin will not load?
Operators whose WordPress box is dead, or who are moving a site onto a fresh Linux host

Restore WordPress to a new server with Reaver Backup

Install the database and web server first. Then pair a new agent, attach the offsite destination, and restore the snapshot.

How do I restore a WordPress site onto a new server with Reaver Backup?
Anyone picking a backup destination for a website, app, directory, or database (WordPress is a common example)

Where should your backups live?

Local is a fast first backup. Offsite to S3, B2, or SSH is real DR. You own the bucket.

Where should I store my backups?
Agencies comparing cost Coming soon

Site-pack pricing vs paying per site

The math for 1, 5, 40, and 100 sites against typical plugin and SaaS bills.

Is per-site backup pricing cheaper than a site pack?

Homelab and mixed fleets Coming soon

Directory and database backups that are not WordPress

Apps, static roots, extra databases. WordPress is a happy path, not the only workload.

Can I back up directories and databases that are not WordPress?

Who should not use this

Shared hosting with no SSH — stay on a plugin. A fully managed vault and zero servers of your own — same. Reaver Backup is the self-hosted way to get plugin-easy backups: a dashboard you host, an agent on the web server, and a restic repo on storage you configure.

Next step

Start with one site. About 15 minutes.

Free edition, local storage, no account required. Offsite and site packs live on Pricing.

Install First backup walkthrough