# Recreate a WordPress site from a backup Recreate a lost WordPress site through xCloud’s backup recreation flow, verify the isolated result and reconcile newer records before DNS cutover. Canonical: https://xcloud.host/use-cases/solutions/recreate-a-wordpress-site-from-a-backup/ 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: Choose a target and domain, inspect backup source, and verify the rebuilt site. 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: A WordPress site is lost and the team must rebuild from available backups. 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: Wrong backup scope can omit uploads or database content. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) - Before any database copy or restore starts, the authorized operator restricts the target and quarantines outbound mail, payment, fulfillment and other provider effects. Restored settings may overwrite plugin suppression; reapply sandbox credentials and verify isolation before testing. Sources: [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-create-a-staging-environment-in-xcloud/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) ## Illustrative situation Illustrative scenario, not a customer case study: A WordPress site is lost and the team must rebuild from available backups. The replacement serves the correct content and administration works. ## Choose the approach - Choose a compatible target and a recovery point before recreation. 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. Inventory available files, database and dns controls **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Inventory available files, database and dns controls; exact site identity, named approver and controlled sample data. **Action:** Inventory available backup files, database point, intended hostname and current DNS owner; list newest business records that might be absent. **Expected result:** The reconstruction plan names data gaps. **Verify:** The reconstruction plan names data gaps. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If no restorable point exists, investigate alternate exports before changing routing. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud recreate WordPress from backups](https://xcloud.host/docs/recreate-wordpress-website-from-backups/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) ### 2. Select the recreate destination **Where:** xCloud Add New Site → Recreate Site From Backup **Permissions:** Named xCloud team/site administrator; confirm target and scope. **Inputs:** Create a compatible target wordpress environment; exact site identity, named approver and controlled sample data. **Action:** In xCloud Add New Site choose Recreate Site From Backup, then select the compatible server and destination/domain while keeping public DNS unchanged. Confirm the exact source backup and settings before starting. **Expected result:** The dashboard presents the selected backup and destination for explicit review. **Verify:** The dashboard presents the selected backup and destination for explicit review. Record the exact account or record tested, result, and time with the responsible owner. **If it fails:** If server/PHP stack differs, verify plugin compatibility first. Capability: Create a WordPress site 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); [xCloud recreate WordPress from backups](https://xcloud.host/docs/recreate-wordpress-website-from-backups/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) ### 3. Start recreation from backup **Where:** xCloud Recreate Site From Backup dashboard **Permissions:** Named xCloud team/site administrator; confirm target and scope. **Inputs:** Follow xcloud recreate-from-backup dashboard procedure; exact site identity, named approver and controlled sample data. **Action:** After the owner confirms the displayed source, destination and settings, choose Start in the xCloud recreation flow. Wait for the operation to finish and preserve its status and logs. **Expected result:** The recreated site loads backup files and database at the approved destination. **Verify:** The recreated site loads backup files and database at the approved destination. Record the exact account or record tested, result, and time with the responsible owner. **If it fails:** If restore reports missing files or schema issues, stop cutover and inspect another point. Capability: Restore a backup Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [xCloud restore backup to another site](https://xcloud.host/docs/how-to-restore-a-backup-to-another-site/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud recreate WordPress from backups](https://xcloud.host/docs/recreate-wordpress-website-from-backups/) ### 4. Check site url, media, users and representative transactions **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Check site url, media, users and representative transactions; exact site identity, named approver and controlled sample data. **Action:** Inspect WordPress login, media, internal links, forms and representative transactions on the new target. **Expected result:** Business owner can accept the reconstructed copy. **Verify:** Business owner can accept the reconstructed copy. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If newer orders or submissions are absent, reconcile them before traffic switch. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud recreate WordPress from backups](https://xcloud.host/docs/recreate-wordpress-website-from-backups/); [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) ### 5. Switch traffic only after owner signs recovery record **Where:** Authorized DNS provider and public browser **Permissions:** Named xCloud team/site administrator; confirm target and scope. **Inputs:** Switch traffic only after owner signs recovery record; exact site identity, named approver and controlled sample data. **Action:** With domain owner's approval update routing to the verified target and check HTTPS, canonical host and application flows. **Expected result:** Visitors reach the recovered site. **Verify:** Visitors reach the recovered site. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If DNS routes inconsistently, keep old evidence and follow the rollback plan. Capability: Change domain DNS and verify routing Sources: [xCloud WordPress migration guide](https://xcloud.host/docs/guide-to-wordpress-site-migration-on-xcloud/); [Enable HTTPS and configure SSL certificates in xCloud](https://xcloud.host/docs/enable-https-in-xcloud-configure-ssl-certificates/); [xCloud recreate WordPress from backups](https://xcloud.host/docs/recreate-wordpress-website-from-backups/); [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 replacement serves the correct content and administration works. 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 - Before restoring, compare the chosen recovery point with newer business records. Wrong backup scope can omit uploads or database content. Use the xCloud dashboard for native restore only after the owner approves target and scope; reconcile or preserve newer data first. 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) - Validate the restored copy with representative content, authentication, HTTPS and this guide’s business acceptance test before moving traffic or closing the incident. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) ## 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/) - **Create a WordPress site** (mcp; write): Requires a compatible Nginx or OpenLiteSpeed server; Docker and single-site agentic servers cannot host a new WordPress site. Checkpoint: Approve the exact server, domain, capacity, cost and creation inputs before provisioning. Verify completion and HTTPS. Operation identifiers to discover: servers.sites.wordpress.create. Scopes: write:sites. 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) - **Restore a backup** (dashboard; manual): Native and Docker restore operations are dashboard-only. An in-place Docker restore replaces current data. Checkpoint: Use Site → Site Backup → Previous Backups → Restore Backup (or Restore to Another Site where offered). Confirm exact target and recovery point before proceeding. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [Back up and restore Docker apps](https://xcloud.host/docs/backup-and-restore-docker-apps/) - **Change domain DNS and verify routing** (app; manual): DNS changes belong to the domain provider or authorized DNS integration; reading an xCloud site does not establish public propagation or certificate validity. Checkpoint: Approve exact hostname and record values; check authoritative DNS and live HTTPS from an independent session. Sources: [xCloud WordPress migration guide](https://xcloud.host/docs/guide-to-wordpress-site-migration-on-xcloud/); [Enable HTTPS and configure SSL certificates in xCloud](https://xcloud.host/docs/enable-https-in-xcloud-configure-ssl-certificates/) ### Copyable agent brief ```text Help with recreate a wordpress site from a backup for the exact xCloud team and site I name. Read available hosting identity and state first, then ask the named WordPress, app, provider or dashboard owner for operations and records outside this connection. Prepare these authored tasks: Inventory available files, database and dns controls; Select the recreate destination; Start recreation from backup; Check site url, media, users and representative transactions; Switch traffic only after owner signs recovery record. The acceptance check is: Business owner can accept the reconstructed copy. Do not infer application transactions or completed dashboard jobs from hosting resource reads. WordPress staging push/pull, backup schedule, restore and cache-setting changes require the authorized dashboard owner; the packaged REST wrapper is GET-only. ``` ### Manual checkpoints - The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: After the owner confirms the displayed source, destination and settings, choose Start in the xCloud recreation flow. Wait for the operation to finish and preserve its status and logs. - The business owner compares the controlled sample with this observable result: Business owner can accept the reconstructed copy. - Staging push/pull, native backup schedules, restores and cache-setting edits require the authorized xCloud dashboard operator; the packaged REST wrapper is GET-only. ## Feature coverage - **business-acceptance** (covered): The replacement serves the correct content and administration works. Steps: phase-4 - **recovery** (covered): Wrong backup scope can omit uploads or database content. 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 - [Create a staging environment in xCloud](https://xcloud.host/docs/how-to-create-a-staging-environment-in-xcloud/) — 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 - [xCloud recreate WordPress from backups](https://xcloud.host/docs/recreate-wordpress-website-from-backups/) — reviewed 2026-09-30 - [xCloud restore backup to another site](https://xcloud.host/docs/how-to-restore-a-backup-to-another-site/) — reviewed 2026-09-30 - [xCloud WordPress migration guide](https://xcloud.host/docs/guide-to-wordpress-site-migration-on-xcloud/) — reviewed 2026-09-30 - [Enable HTTPS and configure SSL certificates in xCloud](https://xcloud.host/docs/enable-https-in-xcloud-configure-ssl-certificates/) — reviewed 2026-09-30 - [Back up and restore Docker apps](https://xcloud.host/docs/backup-and-restore-docker-apps/) — reviewed 2026-09-30 ## Continue [Explore the next WordPress workflow](https://xcloud.host/use-cases/solutions/schedule-wordpress-remote-backups/) - [Back up and recover a Docker application](https://xcloud.host/use-cases/operations/docker-backup-and-recovery/)