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 owner wants to inspect a backup without replacing the public WordPress site.
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: Public DNS or email on a test copy can create confusion.
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: An owner wants to inspect a backup without replacing the public WordPress site. The restored copy has expected login, media and sample data.
Choose the approach
Choose a safe target with distinct domain and access controls. 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
Identify source backup date and expected contents
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Identify source backup date and expected contents; exact site identity, named approver and controlled sample data.
- Action
- Select the source backup date, expected files/database scope and representative user/content records.
- Expected result
- The owner knows what the copy should contain.
- Verify
- The owner knows what the copy should contain. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If the backup identifier is ambiguous, inspect xCloud history before proceeding.
Sources: WordPress roles and capabilities · xCloud restore backup to another site · Site backups in xCloud
Step 2 of 5
Review the isolated destination
- Where
- xCloud Site Backup and destination site overview
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Prepare isolated target and confirm capacity; exact site identity, named approver and controlled sample data.
- Action
- Ask the xCloud owner to identify an existing eligible target or propose a restricted new target and domain with capacity and an outbound-mail suppression plan. This review does not create a site.
- Expected result
- The approved target is identified and cannot be confused with public production.
- Verify
- The approved target is identified and cannot be confused with public production. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If the target could send real customer notices, disable delivery on the copy first.
Sources: WordPress roles and capabilities · xCloud restore backup to another site · Site backups in xCloud
Step 3 of 5
Use dashboard restore-to-another-site path
- Where
- xCloud Site Backup dashboard
- Permissions
- Named xCloud team/site administrator; confirm target and scope.
- Inputs
- Use dashboard restore-to-another-site path; exact site identity, named approver and controlled sample data.
- Action
- In the xCloud dashboard choose restore to another site, verify source point and destination, then start the approved operation.
- Expected result
- A copy is restored without overwriting public site.
- Verify
- A copy is restored without overwriting public site. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If the target shown is production, cancel before confirmation.
Sources: Site backups in xCloud · xCloud restore backup to another site · xCloud agent capability boundaries
Step 4 of 5
Check urls, login, media and email suppression
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Check urls, login, media and email suppression; exact site identity, named approver and controlled sample data.
- Action
- On the copy inspect login, representative media, content URLs and business records while keeping search indexing and email controlled.
- Expected result
- The backup content matches expectation.
- Verify
- The backup content matches expectation. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If database or uploads are missing, investigate backup scope and try another point.
Sources: WordPress roles and capabilities · xCloud restore backup to another site · Site backups in xCloud
Step 5 of 5
Record copy disposition
- Where
- Recovery decision sheet and xCloud site inventory
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Document differences and keep public routing unchanged; exact site identity, named approver and controlled sample data.
- Action
- Record differences from current production and ask the owner to decide whether to retain or delete the copy in a separate authorized dashboard action.
- Expected result
- The rehearsal report names an owner and a later cleanup decision.
- Verify
- The rehearsal report names an owner and a later cleanup decision. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If live data appeared on the test domain, restrict access and review exposure.
Sources: WordPress roles and capabilities · xCloud restore backup to another site · 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 restored copy has expected login, media and sample data. 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. Public DNS or email on a test copy can create confusion. 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.
- 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
- Business owner review and acceptance app · manual
Human planning, acceptance and record reconciliation cannot be inferred from xCloud resource reads. The business owner chooses the application's source of truth.
Checkpoint: Record approved criteria, observed application evidence, unresolved questions and named follow-up.
WordPress roles and capabilities · xCloud agent capability boundaries
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: In the xCloud dashboard choose restore to another site, verify source point and destination, then start the approved operation.
- The business owner compares the controlled sample with this observable result: The backup content matches expectation.
- 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 restored copy has expected login, media and sample data. Check urls, login, media and email suppression
- recovery (covered): Public DNS or email on a test copy can create confusion. Record copy disposition
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