Restore dry-run checks before recovery
Before anything on your site is modified, every restore runs its own safety checks at restore time: - The backup artifacts must be present (missing cloud copies are downloaded first) - Each required artifact is checked against its stored SHA-256 checksum - A safety checkpoint (a…
Restore confidence states and chain health
Each restore point can carry one of five readiness states: - Healthy: Central's records and checksum metadata look complete for this restore point. - Legacy format: informational only — the backup uses an older format without manifest integrity metadata. Restore-time safety…
Backup limits by plan: storage and restore points
Cloud storage, restore points and the largest single backup for each plan, and what happens when a limit is reached.
Bring Your Own Storage (BYOS): add your own cloud bucket
Bring Your Own Storage (BYOS) lets you mirror every PowerSEC cloud backup into a storage bucket you own and control — on top of the PowerSEC-managed copy. This adds an independent, off-site copy in an account you control, so a problem with one copy needn't affect the other. Who…
Backup reliability on large or memory-constrained sites
PowerSEC backups are designed to run in passes so large sites can complete without relying on one long request. Reliability on constrained hosting Recent improvements reduce the chance of memory exhaustion on shared or memory-limited hosting. Large backup file lists are stored…
Restore a site from backup
Restoring a site from a PowerSEC backup takes a few clicks from your Central dashboard.
Backup schedule: weekly full + daily differential
Scheduled cloud backups take a full backup about once a week and a daily differential in between. Every restore point carries a complete copy of the database.