# Compare local and remote WordPress backups Compare local and remote backup scope, status and access, then propose an isolated restore rehearsal for the selected point. Canonical: https://xcloud.host/use-cases/solutions/compare-local-and-remote-wordpress-backups/ Published: 2026-09-30 · Updated: 2026-09-30 · Technical review: 2026-09-30 Evidence: Source reviewed; no production deployment test claimed Editorial owner: xCloud editorial Intent: Map failure scenarios to storage location and verify which backup set is available. For: business-owner, operator ## Requirements and responsibilities - Have named ownership of the domain, selected xCloud team and site, and WordPress administrator access. For this scenario, agree who supplies the data and signs off: An agency sees both local and remote backups and wants to know which one is usable. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) - Use a compatible Nginx or OpenLiteSpeed stack for native WordPress. Verify current server resources, plan eligibility and each selected plugin or service license and requirements before installing; a Docker server does not host a new native WordPress site. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) - Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: A remote label alone does not prove an accessible backup. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) ## Illustrative situation Illustrative scenario: an agency has local and remote backup entries. It compares scope, completion and storage access, then proposes an isolated rehearsal; no restore is performed in this review. ## Choose the approach - Compare completion, scope, retention and restore access for the same site. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) - Keep application setup, domain/DNS ownership, mail delivery and external integrations with their named administrators. Use a plain documented path when a proposed integration cannot be demonstrated end to end. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) ## Dashboard and application procedure ### 1. List available points by date and storage location **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** List available points by date and storage location; exact site identity, named approver and controlled sample data. **Action:** List local and remote points for the same site with completion time, source and storage location. **Expected result:** The comparison uses like-for-like backups. **Verify:** The comparison uses like-for-like backups. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If a label belongs to another site, exclude it. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) ### 2. Compare file and database scope and failure status **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Compare file and database scope and failure status; exact site identity, named approver and controlled sample data. **Action:** Compare files/database scope, retention and failure status for each point. Mark any excluded uploads or tables in the comparison sheet. **Expected result:** The reviewer can say what each backup would recover. **Verify:** The reviewer can say what each backup would recover. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If one excludes uploads or database, mark it incomplete for this task. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) ### 3. Check credentials and destination accessibility **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Check credentials and destination accessibility; exact site identity, named approver and controlled sample data. **Action:** Ask storage owners to verify access to remote object and local retention without revealing credentials. **Expected result:** Both paths have known access owners. **Verify:** Both paths have known access owners. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If the object is unavailable, do not treat a remote label as protection. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) ### 4. Propose a safe restore rehearsal **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Restore a candidate to a safe test site; exact site identity, named approver and controlled sample data. **Action:** Write a separate restore rehearsal request naming the candidate backup, isolated target, outbound quarantine and owner. Do not restore in this comparison task. **Expected result:** A later operator can execute a bounded proof without overwriting production. **Verify:** A later operator can execute a bounded proof without overwriting production. Record the exact account or record tested, result, and time with the responsible owner. **If it fails:** If no isolated target exists, mark restore proof as pending. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) ### 5. Choose primary and alternate recovery paths **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Choose primary and alternate recovery paths; exact site identity, named approver and controlled sample data. **Action:** Choose primary and alternate points and document likely data gap versus current records. **Expected result:** The owner knows the recovery tradeoff. **Verify:** The owner knows the recovery tradeoff. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If newer business records are unaccounted for, keep the decision provisional. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) ## Maintenance - Assign a cadence for selected WordPress core, theme and plugin updates, review version-based findings and retest the path in this guide. In particular, repeat: The selected recovery point can be restored to an isolated target. A chat prompt is not a scheduled task. Sources: [Manage WordPress updates with Updates Manager](https://xcloud.host/docs/manage-wordpress-updates-with-updates-manager/); [Vulnerability Checker in xCloud](https://xcloud.host/docs/vulnerability-checker-in-xcloud/) - Record actual backup completion, storage access and responsible staff. Recheck connected application and provider behavior after changes rather than relying on a site health status alone. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) ## Recovery decisions - This comparison does not restore data. If a candidate lacks accessible files or database, select another point and request a separately approved isolated rehearsal before calling recovery proven. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) ## AI handoff Connect xCloud MCP through the current documented profile and grant only the scopes needed for the selected team. Discover tool schemas first. Read resources to plan; require approval for any supported write. Use returned dashboard URLs for manual work. The packaged REST wrapper accepts GET requests only. ### Supported scope - **Confirm requirements and inspect resources** (mcp; read): Discover the connected profile and operation schema first; only teams granted to the connection are visible. Checkpoint: Confirm exact team, server and site identity. Use dashboard\_url returned by the resource; do not invent a dashboard link. Operation identifiers to discover: teams.index, servers.show, sites.show. Scopes: read:servers, read:sites. Sources: [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) - **Review a WordPress business journey** (app; manual): Application data and observed transactions cannot be inferred from xCloud resource reads. Use authorized test accounts and the application or provider evidence. Checkpoint: Record the test identity, timestamp, expected outcome, observed result and owner decision. Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) ### Copyable agent brief ```text Review compare local and remote wordpress backups for the exact site and team I name. Use permitted reads and ask for application evidence you cannot observe. Work through: List local and remote points for the same site with completion time, source and storage location.; Compare files/database scope, retention and failure status for each point. Mark any excluded uploads or tables in the comparison sheet.; Ask storage owners to verify access to remote object and local retention without revealing credentials.; Write a separate restore rehearsal request naming the candidate backup, isolated target, outbound quarantine and owner. Do not restore in this comparison task.; Choose primary and alternate points and document likely data gap versus current records. Return observations, uncertainties, a decision and a separately approvable operator checklist. Do not create, restore, configure, publish or update anything in this review. ``` ### Manual checkpoints - The named site, business or provider owner supplies application evidence the connected hosting reads cannot observe. - A separately approved operator performs any later configuration, staging, update, restore or publication described in the decision sheet. - The owner accepts the review finding and proposed checks without treating the unexecuted change as completed. ## Feature coverage - **business-acceptance** (covered): The selected recovery point can be restored to an isolated target. Steps: phase-4 - **recovery** (covered): A remote label alone does not prove an accessible backup. Steps: phase-5 ## Sources - [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) — reviewed 2026-09-30; v4.4.2 package; xCloud v2.8.8 capability review - [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) — reviewed 2026-09-30 - [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) — reviewed 2026-09-30 - [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) — reviewed 2026-09-30 - [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) — reviewed 2026-09-30 - [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs) — reviewed 2026-09-30 - [Manage WordPress updates with Updates Manager](https://xcloud.host/docs/manage-wordpress-updates-with-updates-manager/) — reviewed 2026-09-30 - [Vulnerability Checker in xCloud](https://xcloud.host/docs/vulnerability-checker-in-xcloud/) — reviewed 2026-09-30 ## Continue [Explore the next WordPress workflow](https://xcloud.host/use-cases/solutions/prepare-a-wordpress-migration-cutover/) - [Back up and recover a Docker application](https://xcloud.host/use-cases/operations/docker-backup-and-recovery/)