Encrypted WordPress backups.
xbackupman backs up a WordPress site as a single unit — the files and the database together — so a restore brings back a coherent site, not a mismatched half. Everything is encrypted with AES-256-GCM in the worker and stored in a bucket you own.
What gets captured
- Your WordPress files — themes, plugins, uploads and wp-config — archived over SSH.
- The site database, dumped consistently so posts, users and settings match the files exactly.
- Both captured in one snapshot, then gzipped and sealed with AES-256-GCM before upload.
- A SHA-256 checksum per snapshot to verify the whole site backup is intact.
How it works
Connect the site
Point xbackupman at the WordPress install: SSH access to the files and credentials for its database. That is enough to capture the full site.
Capture files and database together
The worker archives the site directory and dumps the database in the same run, so the two halves are a matched pair rather than snapshots taken minutes apart.
Encrypt and store
The combined snapshot is compressed and sealed with AES-256-GCM in the worker, then the ciphertext is uploaded to your own S3-compatible bucket.
Verify and schedule
Each snapshot is SHA-256 checksummed. Run it nightly before your traffic peaks, and let retention prune old copies while always keeping the last one.
Your storage, your keys
Your WordPress snapshots live in your own bucket — S3, R2, B2 or MinIO — not on our servers. Because files and database are encrypted before they leave the worker, your provider stores ciphertext only. You keep full ownership of the site backup and can restore or migrate it on your own terms.
xbackupman never stores your backups on its own servers. It orchestrates the pipeline and records metadata — the encrypted artifacts live only in the S3-compatible bucket you connect. See how encryption works.
One-click restore
Restoring replays both halves onto a target: the files are unpacked and the database is reloaded so the recovered site is internally consistent. Restores go to a separate destination by default, which makes them ideal for spinning up a staging clone or migrating a site to a new host without risking the live one.
Questions
QWhy back up files and database together?
A WordPress site is only coherent when its files and database match. Capturing both in one run avoids the classic failure where restored plugins expect database rows that a separately-timed dump doesn't have.
QCan I use this to migrate WordPress to a new host?
Yes. Because a snapshot is a complete, self-consistent copy and restores can target a different destination, it doubles as a clean migration or staging-clone path.
QDoes it capture my uploads and plugins?
Yes. The file archive covers the whole install — themes, plugins, the uploads directory and wp-config — alongside the database dump.
QHow often should I back up a WordPress site?
Nightly suits most sites; busy stores or news sites may want hourly. Set any cron cadence, and integrity verification lets you trust each snapshot before you need it.
Back up more
One engine covers every source you run — on a single schedule, in one dashboard, encrypted into the same storage.