Requirements and responsibilities
Name the team, server, hostname, owner and affected users for the WordPress site. Record the current version and the actual business flow that must survive the change. Confirm the current dashboard form, plan eligibility, and server capacity before committing a resource change. A one-click catalog listing is discovery, not permission or proof that the connected MCP profile can install it.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Site backups in xCloud · Manage WordPress core, themes and plugins · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · xCloud restore a WordPress backup to another site
Prepare a non-sensitive test input and an acceptance record. Keep access to the app administrator and an independent observer where possible; omit secrets from AI prompts and client reports.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Site backups in xCloud · Manage WordPress core, themes and plugins · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · xCloud restore a WordPress backup to another site
For WordPress, verify the file and database backup scope and a safe target for recovery. Native scheduling, destination settings, staging synchronization and restore remain dashboard actions. Agree a maintenance window and owner before any action that interrupts the service or overwrites data.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Site backups in xCloud · Manage WordPress core, themes and plugins · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · xCloud restore a WordPress backup to another site
A clone or recovered database may start scheduled jobs and carry live payment, booking, mail or webhook credentials. Arrange provider or network controls that prevent external side effects before the copied application can run. If the current xCloud flow cannot guarantee that isolation, use a sanitized fixture or postpone the clone; changing credentials after startup may be too late.
xCloud restore a WordPress backup to another site · xCloud agent capability boundaries
Illustrative situation
A business discovers an error only after several days. It needs enough WordPress backup history to return to a clean point without losing more membership changes than it can reconcile.
Choose the approach
Retention length should cover detection delay as well as backup frequency.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Site backups in xCloud · Manage WordPress core, themes and plugins · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · xCloud restore a WordPress backup to another site
Deleting older snapshots may remove the last clean point; review history before shortening retention.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Site backups in xCloud · Manage WordPress core, themes and plugins · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · xCloud restore a WordPress backup to another site
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Measure change and discovery lag
- Where
- Business records and incident history
- Permissions
- Authorized xCloud read access to the named team and site; the relevant app or provider owner supplies records outside xCloud.
- Inputs
- Daily transactions, longest detection delay
- Action
- Estimate records created between backups and the time a data defect might go unnoticed. Set acceptable loss and retention window.
- Expected result
- A rationale for frequency and retention.
- Verify
- Review a recent week and one historical incident.
- If it fails
- If the proposed window cannot cover detection lag, extend it.
Sources: xCloud MCP documentation and connection profiles · xCloud agent capability boundaries · Site backups in xCloud
Step 2 of 5
Inspect existing history
- Where
- xCloud Site Backup → Previous Backups
- Permissions
- Authorized xCloud site owner with dashboard rights for the exact setting, backup, staging or restore action and a reviewed target.
- Inputs
- Oldest/newest Completed row, storage destination
- Action
- Record actual snapshot ages, failed runs and whether files and database are included. Check whether remote copies exist.
- Expected result
- A real baseline of recoverable points.
- Verify
- Count completed snapshots across the intended interval.
- If it fails
- If backups are sparse, fix completion before tuning retention.
Sources: Site backups in xCloud · xCloud agent capability boundaries
Step 3 of 5
Choose destination and capacity
- Where
- xCloud backup storage provider
- Permissions
- Authorized xCloud site owner with dashboard rights for the exact setting, backup, staging or restore action and a reviewed target.
- Inputs
- Projected snapshot size, quota, access owner
- Action
- Select supported local/remote destination and estimate storage for the desired window. Confirm provider credentials and restore access.
- Expected result
- A feasible storage policy.
- Verify
- Check free quota and provider connection.
- If it fails
- If remote storage is unreliable, resolve it before deleting local history.
Sources: Site backups in xCloud · xCloud agent capability boundaries · xCloud restore a WordPress backup to another site
Step 4 of 5
Set native retention
- Where
- xCloud Site Backup settings
- Permissions
- Authorized xCloud site owner with dashboard rights for the exact setting, backup, staging or restore action and a reviewed target.
- Inputs
- Agreed retention days, frequency and scope
- Action
- Save the approved frequency and retention in the dashboard, recording the previous values. Do not infer MCP can change native schedule settings.
- Expected result
- A documented saved policy.
- Verify
- Reopen settings to confirm exact values.
- If it fails
- If an old clean point would be deleted, preserve it separately first.
Sources: Site backups in xCloud · xCloud agent capability boundaries
Step 5 of 5
Prove the policy works
- Where
- Backup history and isolated restore target
- Permissions
- Authorized xCloud site owner with dashboard rights for the exact setting, backup, staging or restore action and a reviewed target.
- Inputs
- Completed old/new snapshots, sample record
- Action
- Observe a scheduled run and safely restore one retained snapshot to confirm it opens with expected data.
- Expected result
- Evidence of both retention and recoverability.
- Verify
- Record age, scope and restore result.
- If it fails
- If the snapshot is unusable, revisit storage and backup scope immediately.
Sources: xCloud restore a WordPress backup to another site · Site backups in xCloud · xCloud agent capability boundaries
Maintenance
Review this task after app or template updates and at the cadence agreed with the owner. Record failures as dated observations rather than assuming host health proves service health.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Site backups in xCloud · Manage WordPress core, themes and plugins · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · xCloud restore a WordPress backup to another site
Watch access changes, backup completion, free storage and external providers. Recheck integrations after credential, DNS, mail or source-data changes.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Site backups in xCloud · Manage WordPress core, themes and plugins · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · xCloud restore a WordPress backup to another site
Recovery decisions
Before data recovery, identify incident time, completed backup, target and records created after the snapshot. Preserve current evidence and live data before replacement.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Site backups in xCloud · Manage WordPress core, themes and plugins · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · xCloud restore a WordPress backup to another site
Use the documented dashboard or application recovery procedure with the authorized owner. Repeat the task-specific limited-user check; reconcile newer records before reopening writes.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Site backups in xCloud · Manage WordPress core, themes and plugins · WordPress security hardening · WordPress roles and capabilities · Create WordPress pages · Manage WordPress plugins · xCloud restore a WordPress backup to another site
AI handoff
Connect an authorized xCloud MCP profile and discover its exact tools and team scope. The packaged REST wrapper is GET-only; use dashboard or app controls for undocumented writes.
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
Copyable agent brief
Manual checkpoints
- Approve exact site, target, cost and any write or maintenance window after inspecting the proposed plan.
- An authorized WordPress administrator must configure and test app users, content, integrations and business rules in the app.
- Native WordPress staging, backup schedule/settings, push/pull and all restores are dashboard-only; Docker restore is dashboard-only and replaces state.
- Reconcile data created after the chosen recovery point before any destructive restore.
Feature coverage
- retention decision, evidence and task action (covered): The procedure identifies the authorized task boundary and observable result. Measure change and discovery lag Inspect existing history Choose destination and capacity Set native retention
- backup, ongoing operation and recovery (covered): Recovery and maintenance are checked in the task procedure. Set native retention Prove the policy works
Sources
- xCloud agent capability boundaries
- xCloud MCP documentation and connection profiles
- Site backups in xCloud
- Manage WordPress core, themes and plugins
- WordPress security hardening
- WordPress roles and capabilities
- Create WordPress pages
- Manage WordPress plugins
- xCloud restore a WordPress backup to another site