Restore Reseller Backups
Restore RAPP full accounts, home directories, websites, mail, databases and relative paths with backup ownership checks, service availability and recovery safeguards.
Open Manage Backups → Restore Backups. Global backups must be enabled.
Choose a backup
The provider's reseller-pool restore permission controls whether the list includes reseller-owned storage pools. Without it, the list is limited to your reseller's backups in root-owned pools. Ask the provider to check this policy when an expected record is absent.
The table identifies the backup ID, username, method, storage pool, reseller, security label, date/time and size. Expanded details include the backup path/type and schedule identity, owner and type. Search for the account and compare the date and destination before selecting an action.
The Secured label is based on the pool being owned by root. It is not a claim that the archive was cryptographically verified or that the transport is encrypted. Reseller-owned pools are labelled Unsecured by this table.
Recovery actions and fields
Every action carries the selected backup ID and username. The confirmation dialog requests the additional resource where needed.
| Action | Additional input and availability |
|---|---|
| Full account | No resource field. Available even when the account is marked removed. |
| Home directory | No resource field; the account must exist. |
| Website | Domain name, including a supported wildcard domain where applicable; existing account required. |
| Email account | Valid email address; existing account required. |
| MySQL database | Database name; existing account required. |
| File | Relative file path; existing account required. |
| Directory | Relative directory path; existing account required. |
| PostgreSQL database | Database name; shown for an existing account when PostgreSQL support is available. |
| MongoDB database | Database name; shown for an existing account when MongoDB support is available. |
File and directory values must not start or end with /, contain .., or include ampersand, backslash or double quote. Enter paths relative to the account's home rather than absolute server paths. Database names must pass the form's name validator and must not start or end with underscore or hyphen.
Safe recovery workflow
- Preserve current data and coordinate any interruption with the account owner.
- Confirm the username, backup ID, date and exact recovery scope.
- Select an available action, enter the resource if requested and review the confirmation.
- Submit once. A restore already in progress for that user blocks another request.
- Wait for completion and verify the recovered website, files, mail or database.
Starting is not completing
A success message states that restoration started. It does not prove that the recovered application works or that every component finished. Verify the outcome before declaring recovery complete.
The server checks that the backup belongs to the reseller before starting recovery. Demo mode blocks restore requests. Do not delete restore lock files to bypass an in-progress message; ask the provider to investigate a persistent lock. Partial actions depend on the account and service availability; a missing button is not evidence that a backup contains no data.