Skip to Content
Browse documentation

Restore Account Backups in UAPP

Select a permitted account backup and restore a full account, home directory, website, mailbox, database, file or directory in UAPP.

Open Manage Backups → Restore Backups. Global backups must be enabled.

Select a backup

Review backup identity, date, method and destination/owner information before choosing an action. Use the list controls to locate the intended recovery point.

The account's recorded backups can appear even when restore is not permitted. Provider settings determine whether reseller-owned and user-owned pools can be restored; root/provider-owned backups are the baseline scope. Another restore in progress disables restore actions. PostgreSQL and MongoDB actions additionally depend on detected server configuration.

Restore scopes and inputs

Every operation requires the selected backup ID. Additional fields depend on scope:

ScopeRequired input
Full AccountSelected backup only; broad account recovery.
Home DirectorySelected backup only; account home recovery.
WebsiteDomain name contained in the intended recovery point.
Email AccountValid mailbox email address.
MySQL DatabaseDatabase name.
PostgreSQL DatabaseDatabase name.
MongoDB DatabaseDatabase name.
FileFile path relative to account home.
DirectoryDirectory path relative to account home.

Database-name validation allows word characters and hyphens, without a leading/trailing underscore or hyphen. Relative paths must not start/end with a slash, contain .., ampersands, backslashes or double quotes. Use the path in the backup; this is not a free-form remote download destination.

The server checks ownership/permission for the selected backup. A valid text field alone does not prove the requested object exists in that backup.

Start restoration

  1. Preserve current data and choose the narrowest suitable restore scope.
  2. Select the intended backup and restore action.
  3. Check the selected recovery point and target.
  4. Enter any required domain, mailbox, database or relative path.
  5. Read the confirmation warning and confirm.
  6. Wait for the current restore to finish, then verify the application/data.

Restore can replace current data

Restoring older data can overwrite newer files, mail, databases or configuration within the selected scope. A full-account restore is broader than restoring a single file. Plan downtime and retain a current recovery copy where needed.

All nine restore actions are blocked in demo mode. The server prevents starting another restore while it detects one in progress. A started message is not completion; do not repeatedly resubmit while work may be running.

If a backup is unavailable or restore remains blocked, ask the provider to inspect storage access, permission and task state. Do not delete recovery data or change pool credentials until the issue is understood.