Local restore points solve a specific problem
A local restore point is stored on or near the connected WordPress installation. It can be created immediately before a plugin repair, configuration change, or update and restored without transferring a large archive across the internet. That speed makes local storage useful for transactional rollback when the server itself remains healthy.
Local storage also shares the server's risks. Disk failure, account suspension, malware, ransomware, accidental deletion, or a full filesystem can damage both the site and its backup. Retention must prevent archives from consuming the disk, and backup creation should fail clearly when available space is too low.
Off-site copies protect against infrastructure loss
An off-site backup is stored in a separate account or object-storage system with independent credentials. It remains available when the origin server is lost. Encryption, lifecycle retention, access logging, regional requirements, and deletion controls matter because these archives can contain customer data, orders, uploads, and configuration secrets.
Do not assume an archive is restorable because an upload completed. Record checksums, database export status, WordPress version, PHP compatibility, and archive contents. Periodic restoration to an isolated environment is the strongest proof that the recovery path works.
Use both layers in a recovery policy
Before a repair, create a short-lived local restore point for rapid rollback. On a schedule, copy protected backups off site according to the business recovery objective. Define how much data the organization can lose, how quickly service must return, and who can authorize restoration. WooCommerce and membership sites also need a plan for reconciling transactions created after the selected backup.
WPFixAgent currently uses local restore points in standard repair workflows and exposes custom object-storage integration for controlled Enterprise deployments. Whatever storage system is used, treat backup status, retention, verification, and restore history as operational evidence rather than a simple checkbox.
