Restore a DirectAdmin user archive when you need to recover account data or import an account onto a prepared server. Restoring can replace current content and configuration, so first decide exactly which point in time and data types you need.
IN THIS ARTICLE
Prepare for the change
Confirm the archive source, date, completeness and trusted ownership. Take a separate backup of the current account before an overwrite. Verify destination capacity, software compatibility, IP mappings and the receiving reseller. For active shops or mailboxes, identify data created after the backup that must not be lost.
01 Restore one DirectAdmin user backup safely
- Place the archive in a location accessible through the supported Admin Backup/Transfer restore workflow, or configure the supported remote source.
- Open Restore, select the exact archive and review the account identity. Check whether the account already exists and how the selected restore affects its current data.
- Choose the intended IP handling and any permitted restore options. Existing-account ownership is not necessarily changed by an option intended for newly created accounts.
- For a production overwrite, stop or control new application writes during the final backup and restore window. Restore into an isolated test account or server first whenever practical.
- Start the restore and follow its task status and messages. Let the task processor finish; launching repeated jobs can compound conflicts and resource pressure.
- Test the recovered account before changing public DNS or declaring recovery complete. Reconcile newer transactions or mail through a separate planned process when necessary.
Will restoring a database merge recent orders?
No. Treat a database restore as replacement unless you have explicitly engineered and tested a separate data reconciliation process. Export or preserve newer business records before the operation.
Check the backup or recovered data
Check website content, database connectivity, mailbox access, scheduled jobs and file ownership. Confirm the restored date with a known record, not only a working home page. Test a new controlled write and ensure backups will cover the recovered account.
If the change does not work
If the restore fails, retain the archive and task error. Investigate space, archive integrity, account conflicts or compatibility before retrying. If the result is wrong, use the pre-restore backup and documented maintenance plan; a second arbitrary restore is not a safe merge strategy.