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 content site becomes unusable after a release and the last backup predates new posts.
xCloud agent capability boundaries · WordPress 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.
xCloud agent capability boundaries · WordPress plugin administration
Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: In-place restore overwrites newer posts, comments and form records.
Before a source copy or backup restore starts, the authorized operator must restrict the target and quarantine outbound mail, payment, fulfillment and other provider effects at the receiving environment. Restored WordPress settings can overwrite plugin suppression; reapply sandbox credentials and verify isolation before tests.
Create a staging environment in xCloud · Site backups in xCloud
Illustrative situation
Illustrative scenario, not a customer case study: A content site becomes unusable after a release and the last backup predates new posts. The recovered copy logs in and contains agreed representative content.
Choose the approach
Choose an alternate restore target first when investigation can continue safely. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · WordPress roles and capabilities · 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.
xCloud agent capability boundaries · WordPress plugin administration
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Establish incident and data delta
- Where
- xCloud selected team/site resource view and owner planning sheet
- Permissions
- Named xCloud team/site administrator; confirm the exact production or staging target.
- Inputs
- Owner, hostname, approved requirements, sample record and decision date. Establish incident and data delta.
- Action
- Identify the affected site, last healthy time and records created since that time. Preserve logs and current files or database evidence before choosing a restore point.
- Expected result
- Incident impact and possible data loss are visible.
- Verify
- Compare backup timestamps with the newest post, form entry and user account.
- If it fails
- If live records are still arriving, establish a controlled intake route before recovery.
Sources: xCloud agent capability boundaries · xCloud MCP documentation and connection profiles
Step 2 of 5
Choose backup and safe target
- Where
- xCloud Site Backup dashboard
- Permissions
- Named xCloud team/site administrator; confirm the exact production or staging target.
- Inputs
- Target team/site, server or plugin version, license and documented prerequisites. Choose backup and safe target.
- Action
- List available xCloud site backups by completion, location and files/database scope. Prefer an isolated target to inspect a candidate point when possible.
- Expected result
- The recovery point and target are deliberate.
- Verify
- Confirm selected backup identifier, storage access and target hostname with the owner.
- If it fails
- If no backup includes required data, investigate alternate copies rather than overwriting the current site.
Sources: Site backups in xCloud · xCloud agent capability boundaries
Step 3 of 5
Restore a test copy in dashboard
- Where
- xCloud Site Backup dashboard
- Permissions
- Named xCloud team/site administrator; confirm the exact production or staging target.
- Inputs
- Approved change scope, backup state, selected version and maintenance window. Restore a test copy in dashboard.
- Action
- In the xCloud dashboard restore the chosen backup to a safe target or follow the documented recreation path. Do not use an inferred MCP restore call.
- Expected result
- A test copy exists without changing public traffic.
- Verify
- Wait for the dashboard operation to finish and inspect logs, WordPress login and representative media.
- If it fails
- If the copy fails, retain the original evidence and try another documented recovery point.
Sources: Site backups in xCloud · xCloud agent capability boundaries · xCloud restore backup to another site · xCloud recreate WordPress from backups
Step 4 of 5
Test restored business journeys
- Where
- WordPress public pages, administrator and relevant external provider
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Test accounts, sample content or transaction, expected result and provider access. Test restored business journeys.
- Action
- Run the site's public and administrator acceptance tests on the copy, including forms and HTTPS. Compare missing posts or submissions with records created after the backup.
- Expected result
- The owner can see exactly what would be recovered and lost.
- Verify
- Record observed URLs, sample identifiers and the delta requiring replay.
- If it fails
- If critical data is missing, defer cutover and plan manual reconciliation or forward repair.
Sources: WordPress roles and capabilities
Step 5 of 5
Cut over after reconciliation
- Where
- WordPress public pages, administrator and relevant external provider
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Observed results, unresolved failures, backup point and owner contacts. Cut over after reconciliation.
- Action
- Approve final target, data reconciliation and routing change with the business owner. Recheck login, content and business flow after traffic moves.
- Expected result
- Visitors reach a verified site and newer records have a disposition.
- Verify
- Have an independent user repeat a representative transaction and inspect the application record.
- If it fails
- If acceptance fails, invoke the pre-agreed routing rollback while preserving records written to either target.
Sources: WordPress roles and capabilities
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 recovered copy logs in and contains agreed representative content. A chat prompt is not a scheduled task.
Manage WordPress updates with Updates Manager · 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.
Recovery decisions
Before restoring, compare the chosen recovery point with newer business records. In-place restore overwrites newer posts, comments and form records. Use the xCloud dashboard for native restore only after the owner approves target and scope; reconcile or preserve newer data first.
Validate the restored copy with representative content, authentication, HTTPS and this guide’s business acceptance test before moving traffic or closing the incident.
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 and scopes to discover
teams.index, servers.show, sites.show
Scopes: read:servers, read:sites
xCloud MCP documentation and connection profiles · xCloud agent capability boundaries
- Configure native WordPress backup and restore dashboard · manual
Native schedule, retention and destination changes and all restores are dashboard-only.
Checkpoint: Use Site → Site Backup. Before restoring, confirm backup, target, scope and treatment of newer records.
- 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.
xCloud agent capability boundaries · Back up and restore Docker apps
- 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.
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: In the xCloud dashboard restore the chosen backup to a safe target or follow the documented recreation path. Do not use an inferred MCP restore call.
- The business owner compares the controlled sample with this observable result: The owner can see exactly what would be recovered and lost.
- 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 recovered copy logs in and contains agreed representative content. Test restored business journeys
- recovery (covered): In-place restore overwrites newer posts, comments and form records. Cut over after reconciliation
Sources
- xCloud agent capability boundaries
- WordPress roles and capabilities
- WordPress plugin administration
- Site backups in xCloud
- WordPress hardening handbook
- Create a staging environment in xCloud
- xCloud MCP documentation and connection profiles
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- xCloud restore backup to another site
- xCloud recreate WordPress from backups
- Back up and restore Docker apps