GoAdmio
GoAdmio Documentation

Recover Terminated Accounts

From the GoAdmio knowledge base.

Recover Terminated Accounts

This page explains the Recover Terminated Accounts screen in the GoAdmio Admin Panel. It lets you restore a hosting account that was previously terminated — provided that snapshots or backups are enabled and available.

Location: Admin Panel → Accounts & Plans → Recover Terminated Accounts


Overview

Terminating an account deletes its files, databases, email, and configuration (see Terminate Accounts). If the account was terminated by mistake, or the customer later requests restoration, the Recover Terminated Accounts page is the starting point.

Recovery works by restoring the account from a scheduled snapshot or backup. Without one, recovery is not possible — the data is permanently gone.

> Important: Recovery depends entirely on snapshots or backups being enabled and available before the account was terminated. If neither was scheduled, the Recover action will not be able to restore the account. Enable snapshots on all production servers.


Prerequisites

Before you attempt recovery, confirm:

  1. Scheduled snapshots are enabled — See Schedule Snapshot. The snapshot schedule must have been active before the account was terminated.
  2. At least one snapshot exists that predates the termination. See Snapshots for the list.
  3. The domain is not currently assigned to another account. If it is, release it first.
  4. You know the original domain and username of the terminated account.
  5. Sufficient disk space exists on the server for the restored data.
> Warning: If you did not enable Schedule Snapshot or Schedule Backup before the termination, the account cannot be recovered. In that case, only a manual restore from an external backup is possible.

How to Recover a Terminated Account

Step 1 — Open Recover Terminated Accounts

  1. Log in to the GoAdmio Admin Panel.
  2. Navigate to Accounts & Plans → Recover Terminated Accounts.

Step 2 — Locate the Account

The page lists terminated accounts that are recoverable. You can search by:

  • Original domain (e.g., example.com)
  • Original username (e.g., example)
  • Termination date
Select the account you want to recover.

Step 3 — Choose a Snapshot

If the account has more than one snapshot, choose the most recent one from before the termination:

| Snapshot date | Choose when |
|---|---|
| Most recent | You want the latest data prior to termination |
| Older | The most recent snapshot was taken after a problem (e.g., malware) |

> Tip: If you are recovering because of a compromise or data corruption, choose a snapshot from before the incident.

Step 4 — Recover

  1. Confirm the snapshot selection.
  2. Click Recover.
  3. Wait for the restore to complete. Large accounts may take several minutes.
The account is recreated with the original username, domain, files, databases, and email from the chosen snapshot.

Step 5 — Verify the Account

After recovery:

  1. Confirm the account appears in List Accounts.
  2. Verify the website loads.
  3. Check that databases are present and accessible via MySQL Databases.
  4. Verify email accounts and mailboxes via Email Accounts.
  5. Confirm the DNS zone is correct via DNS Manager.
  6. Check the assigned PHP version via MultiPHP Manager.
  7. Run Fix Permissions if files are not owned by the correct user.

What Gets Restored

A full account recovery from a snapshot typically restores:

| Component | Restored |
|---|---|
| Files (home directory) | ✅ |
| MySQL databases | ✅ |
| Email accounts and mailboxes | ✅ |
| Email forwarders and autoresponders | ✅ |
| FTP accounts | ✅ |
| Cron jobs | ✅ |
| DNS zone | ⚠️ Depends on snapshot configuration |
| SSL certificates | ⚠️ Re-issue if not restored |
| PHP version assignment | ⚠️ Verify and re-assign if needed |
| Package and limits | ⚠️ Re-assign via Modify Account |

> Note: Some settings live outside the account snapshot (system-level configuration, package definitions, SSL issuance). Review the account after recovery and re-apply anything that was not captured.


If Recovery Fails

| Failure | Likely cause | Solution |
|---|---|---|
| "No snapshots found" | Snapshots were never enabled, or were purged | Restore from an external backup via Restore Full Backup |
| "Snapshot too old" | Snapshot retention policy removed it | Check Snapshots for the retention window; extend it for future accounts |
| "Domain already in use" | Another account now owns the domain | Release the domain from the other account first |
| "Insufficient disk space" | Server is out of room for the restore | Free space, or expand storage |
| "Restore partial failure" | Corrupted snapshot or missing components | Try an older snapshot; if all fail, use an external backup |
| Account restored but website shows an error | Permissions or PHP version mismatch | Run Fix Permissions; re-assign PHP version |


Preventing Data Loss

The most reliable defense against accidental termination is a layered backup strategy:

| Layer | Tool | Purpose |
|---|---|---|
| Snapshots | Schedule Snapshot / Snapshots | Fast recovery from recent accidental deletion |
| Scheduled backups | Schedule Backup | Point-in-time backups to local or remote storage |
| Remote backups | Copy Files and Folders, Backup Wizard | Off-site copy in case the server is lost |
| Account copies | /go/backup, /go/serversync | Migrate or duplicate accounts across servers |

> Tip: Enable Schedule Snapshot on every production server. It is the fastest way to undo accidental terminations, account deletions, or file loss from a compromised account.


Related Pages

Troubleshooting

| Problem | Likely cause | Solution |
|---|---|---|
| Recover page is empty | No terminated accounts, or none with snapshots | Verify the account was terminated recently and that snapshots exist |
| "Snapshots not enabled" | Schedule Snapshot was never configured | Enable snapshots now; recover this account from an external backup |
| Account recovers but email is missing | Snapshot excluded mailboxes | Check snapshot scope; restore email separately from a backup |
| Account recovers but DNS does not resolve | Zone not included in snapshot | Recreate the zone in DNS Manager from the customer's records or backup |
| Website shows a 500 error after recovery | PHP version or permissions mismatch | Reassign PHP via MultiPHP Manager; run Fix Permissions |
| SSL certificate not restored | Certificates are system-level, not account-level | Re-issue via Install Free SSL Certificate |
| Recovery takes too long | Large account or slow storage | Wait; monitor via Process Monitor |
| Recovered account cannot log in | Password reset by recovery | Use Password Modification to set a new password and notify the customer |


Best Practices

  1. Enable snapshots before you need them — recovery is only possible if a snapshot predates the termination.
  2. Do not terminate accounts impulsively — prefer Suspend Account until the situation is resolved.
  3. Document the termination — keep a record of who terminated the account, when, and why.
  4. Keep off-site backups — snapshots protect against accidental deletion, but not against server loss.
  5. Test recovery regularly — recover a non-critical account on a staging server to confirm snapshots work.
  6. Retain backups per policy — match retention to legal and business requirements.
Last updated: 2026-11-08
↑