Skip to main content

Check backups and recovery options

Use this guide to check what was captured, where it is retained and whether a recovery option is available. A queued request or a successful local capture does not by itself establish a verified remote recovery point.

Before you start​

Console backup actions require an entitled, active project, owner permission and enabled backup services. Before requesting a capture, check the available project controls for an acknowledged, enabled backup policy and whether a capture is included. Ask support if the policy or eligibility is unclear.

Verification scope: the retained-recovery portal entry was checked live with an empty authorization list. The project-specific controls below were checked in source. Their availability depends on your project; no backup, upload, download or restore was executed for this guide.

Check the backup settings and evidence​

  1. If your project offers Backup destinations, open it and select the intended environment. Check the scheduling and destination environments separately; their selectors are independent.
  2. Review the applied schedule, timezone, destination and retention settings. Compare Desired revision with Applied revision. A saved change is not active until it has been acknowledged.
  3. For a complete Odoo recovery point, check that Include filestore attachments is enabled in the applied settings. A database-only capture omits those files. Also check whether the policy is Local capture only or uses a registered remote destination.
  4. Review Recent captures and Latest remote recovery point. Distinguish Captured locally, Upload pending, Upload failed and Remote verified. Check the recorded capture time and restore availability.

Request a backup, when enabled​

  1. Check the applied scope and destination first. The local backup button inherits the backup policy, including whether attachments are included and whether a remote upload follows. Its label does not override that policy.
  2. Open Operations and select the intended Environment. Explicitly select and confirm the intended environment every time; do not rely on a preselected value.
  3. Select local backup and read the confirmation. Proceed only when the target and applied backup scope are correct. If the policy is paused or the action is unavailable, ask support before proceeding.
  4. Keep the queued reference. Refresh the project and check Builds & releases → Recent operations for the capture outcome. Check remote-upload status separately when a destination is configured.

Review recovery options​

  1. If your project offers Assurance Cloud → Recovery, inspect the recovery point's capture time, included data, exclusions, target and recipient.
  2. If a drill or portable export is offered, review its exact scope before authorizing it. Authorization records a decision; execution and a ready result are separate stages. It does not immediately restore over live Odoo.
  3. For an existing authorization, open Recovery and retained system packages using the authorized Odoo owner account. This access is separate from an active paid console subscription.
  4. Follow the authorization's current status and retrieval deadline. When a package is ready and eligible, request a fresh download link. It is single-use and valid for up to five minutes; follow the displayed expiry. Reissue an expired link only while the recorded retrieval period remains open.
  5. Before any actual restore, agree the recovery point, intended target, complete database-and-filestore set, treatment of newer data and expected interruption with support. No general customer Restore Live control was established in this review.

Expected result​

You can identify the data and time covered by a capture, whether a remote copy was verified, and whether an authorized recovery package is ready. A download does not install a recovery, cancel service or erase data.

Troubleshooting and limitations​

  • Backup unavailable: ask Corvus to confirm owner access, project readiness, applied policy and plan eligibility. Do not repeatedly submit a request with an uncertain outcome.
  • Saved settings not applied: check the later applied revision and status before relying on the new schedule.
  • Upload failed: a local capture may still exist, but remote verification has not succeeded. Contact support with the capture reference and displayed state.
  • No retained authorization or expired retrieval period: ask support to check the current record. A fresh link cannot extend the underlying retrieval period.
  • Local copy only: it shares the node's failure risk. A synthetic result is not independent offsite recovery proof.
  • Package size and scope: confirm package eligibility, size limits and the available delivery route with support. Do not interpret a portable-download limit as a limit on backup storage, database size or your hosting plan.
  • Retention and recovery promises: actual plan limits and observed states apply. A retention setting is not a guaranteed deletion deadline, and these screens do not establish a recovery-time or recovery-point guarantee.

Guide version 1.1, verified 28 October 2026 (UTC). Evidence includes the live recovery portal, public operations tour and source-reviewed conditional controls. Use Support handoff for an unavailable or unclear recovery path.