Backups and recovery

Check before changing

Open the selected site’s Backups section and inspect the available records and timestamps. The UI may expose backup-related operations, but availability and retention are service-specific. A visible record is not proof that a restore has been tested or that every recent change is included.

Recovery is operator-controlled

Recovery is operator-controlled. A restore can overwrite current content or data and may affect connected services. Contact support with the site, environment, desired recovery point, and impact context. Do not treat a failed backup fix or capture-retry flow as a supported automatic recovery path; neither is documented as an available workflow here.

Prepare a recovery request

Pause risky changes if practical; record the relevant time window and symptoms; identify whether files, database content, or both are involved; and wait for an explicit completion confirmation before resuming writes. Do not send credentials or customer data dumps in a ticket.