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 publisher wants remote backups after a local storage incident.
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: A configured schedule without completed runs is not protection.
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.
Create a staging environment in xCloud · Site backups in xCloud
Illustrative situation
Illustrative scenario, not a customer case study: A publisher wants remote backups after a local storage incident. A scheduled run completes at the destination and a sample restore works.
Choose the approach
Select supported remote destination and retention with access owner. 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
Define backup frequency, storage owner and data scope
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Define backup frequency, storage owner and data scope; exact site identity, named approver and controlled sample data.
- Action
- Choose required recovery interval, data scope, storage account owner and retention period based on publication frequency.
- Expected result
- Backup policy matches editorial loss tolerance.
- Verify
- Backup policy matches editorial loss tolerance. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If owner cannot access remote storage, resolve access before scheduling.
Sources: WordPress roles and capabilities · Site backups in xCloud
Step 2 of 5
Connect supported remote storage in dashboard
- Where
- xCloud Site Backup dashboard
- Permissions
- Named xCloud team/site administrator; confirm target and scope.
- Inputs
- Connect supported remote storage in dashboard; exact site identity, named approver and controlled sample data.
- Action
- In xCloud dashboard connect a supported remote destination and test credentials without exposing secrets in a report.
- Expected result
- The destination is available to the site.
- Verify
- The destination is available to the site. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If connection fails, do not assume local backup has become remote.
Sources: Site backups in xCloud · xCloud agent capability boundaries
Step 3 of 5
Set native WordPress schedule and retention manually
- Where
- xCloud Site Backup dashboard
- Permissions
- Named xCloud team/site administrator; confirm target and scope.
- Inputs
- Set native wordpress schedule and retention manually; exact site identity, named approver and controlled sample data.
- Action
- Set native WordPress schedule, retention and destination in Site Backup dashboard; inspect the first completed remote run.
- Expected result
- A real remote backup point exists.
- Verify
- A real remote backup point exists. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If first job is pending or failed, troubleshoot and rerun before calling the schedule ready.
Sources: Site backups in xCloud · xCloud agent capability boundaries
Step 4 of 5
Inspect first completed run and remote object presence
- Where
- xCloud Site Backup dashboard
- Permissions
- Named xCloud team/site administrator; confirm target and scope.
- Inputs
- Inspect first completed run and remote object presence; exact site identity, named approver and controlled sample data.
- Action
- Restore a point to a safe target in the dashboard; check login, recent post and upload.
- Expected result
- The remote point is recoverable.
- Verify
- The remote point is recoverable. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If restore cannot read the object, correct storage access and repeat.
Sources: Site backups in xCloud · xCloud restore backup to another site · xCloud agent capability boundaries
Step 5 of 5
Rehearse safe restore and review failed-run alerts
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Rehearse safe restore and review failed-run alerts; exact site identity, named approver and controlled sample data.
- Action
- Assign a staff owner to inspect failed jobs and compare backup age with new posts before any future restore.
- Expected result
- The policy has operational follow-through.
- Verify
- The policy has operational follow-through. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If a site incident occurs between runs, prepare a replay plan for newer work.
Sources: WordPress roles and capabilities · 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: A scheduled run completes at the destination and a sample restore works. 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. A configured schedule without completed runs is not protection. 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
- 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.
- 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
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: Set native WordPress schedule, retention and destination in Site Backup dashboard; inspect the first completed remote run.
- The business owner compares the controlled sample with this observable result: The remote point is recoverable.
- 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): A scheduled run completes at the destination and a sample restore works. Inspect first completed run and remote object presence
- recovery (covered): A configured schedule without completed runs is not protection. Rehearse safe restore and review failed-run alerts
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
- Back up and restore Docker apps