What it does
SiteVault writes restore points into the site's own server — a web-denied directory at wp-content/wpch-vault/ — rather than a vendor cloud. WPClientHub only orchestrates: it schedules the job and stores the manifest, checksums and size of each restore point. The backup payload itself never transits or rests on WPClientHub's servers. That means no storage bill that grows with your site count, and nothing of your clients' data to lose in a breach of us.
The connector does the actual work on the site: a chunked, time-boxed, incremental snapshot of the database and wp-content, checksummed with SHA-256 in a manifest, optionally streamed straight to storage you own.
How to
- Open a site's Backups tab to see its restore points, or the portfolio Backups page for coverage across every site ("Never backed up", "On a schedule", "One copy only", "Replicated offsite").
- Click Back up now for an on-demand restore point.
- Set a recurring schedule from the same tab so restore points happen without you remembering to click anything.
Limits & defaults
| Setting | Default |
|---|---|
| Where restore points live | wp-content/wpch-vault/ on the site's own server, protected against direct web access |
| What WPClientHub stores | Manifests, checksums, sizes and schedules only — never the archive itself |
| Restore points kept locally | Set by your backup schedule (not a fixed number of 3 anymore) |
| Permissions | Owner, admin and tech can start/schedule backups; viewer is read-only |
Troubleshooting
A site shows "Never backed up"
Either no schedule has been set, or the first run hasn't completed yet — start one with Back up now.
A backup is failing repeatedly
You'll get an email once a profile has failed 3 times running, or produced nothing completed in 3 days — see Troubleshooting.
I need my backups off this server entirely
See Offsite storage — restore points can stream straight to storage you control.