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 agency sees both local and remote backups and wants to know which one is usable.
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 remote label alone does not prove an accessible backup.
Illustrative situation
Illustrative scenario: an agency has local and remote backup entries. It compares scope, completion and storage access, then proposes an isolated rehearsal; no restore is performed in this review.
Choose the approach
Compare completion, scope, retention and restore access for the same site. 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
List available points by date and storage location
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- List available points by date and storage location; exact site identity, named approver and controlled sample data.
- Action
- List local and remote points for the same site with completion time, source and storage location.
- Expected result
- The comparison uses like-for-like backups.
- Verify
- The comparison uses like-for-like backups. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If a label belongs to another site, exclude it.
Sources: WordPress roles and capabilities · Site backups in xCloud
Step 2 of 5
Compare file and database scope and failure status
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Compare file and database scope and failure status; exact site identity, named approver and controlled sample data.
- Action
- Compare files/database scope, retention and failure status for each point. Mark any excluded uploads or tables in the comparison sheet.
- Expected result
- The reviewer can say what each backup would recover.
- Verify
- The reviewer can say what each backup would recover. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If one excludes uploads or database, mark it incomplete for this task.
Sources: WordPress roles and capabilities · Site backups in xCloud
Step 3 of 5
Check credentials and destination accessibility
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Check credentials and destination accessibility; exact site identity, named approver and controlled sample data.
- Action
- Ask storage owners to verify access to remote object and local retention without revealing credentials.
- Expected result
- Both paths have known access owners.
- Verify
- Both paths have known access owners. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If the object is unavailable, do not treat a remote label as protection.
Sources: WordPress roles and capabilities · Site backups in xCloud
Step 4 of 5
Propose a safe restore rehearsal
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Restore a candidate to a safe test site; exact site identity, named approver and controlled sample data.
- Action
- Write a separate restore rehearsal request naming the candidate backup, isolated target, outbound quarantine and owner. Do not restore in this comparison task.
- Expected result
- A later operator can execute a bounded proof without overwriting production.
- Verify
- A later operator can execute a bounded proof without overwriting production. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If no isolated target exists, mark restore proof as pending.
Sources: WordPress roles and capabilities · Site backups in xCloud
Step 5 of 5
Choose primary and alternate recovery paths
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Choose primary and alternate recovery paths; exact site identity, named approver and controlled sample data.
- Action
- Choose primary and alternate points and document likely data gap versus current records.
- Expected result
- The owner knows the recovery tradeoff.
- Verify
- The owner knows the recovery tradeoff. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If newer business records are unaccounted for, keep the decision provisional.
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: The selected recovery point can be restored to an isolated target. 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
This comparison does not restore data. If a candidate lacks accessible files or database, select another point and request a separately approved isolated rehearsal before calling recovery proven.
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.
Copyable agent brief
Manual checkpoints
- The named site, business or provider owner supplies application evidence the connected hosting reads cannot observe.
- A separately approved operator performs any later configuration, staging, update, restore or publication described in the decision sheet.
- The owner accepts the review finding and proposed checks without treating the unexecuted change as completed.
Feature coverage
- business-acceptance (covered): The selected recovery point can be restored to an isolated target. Propose a safe restore rehearsal
- recovery (covered): A remote label alone does not prove an accessible backup. Choose primary and alternate recovery paths