Keep a fresh copy of the current account wherever possible, even if it contains the problem. Verify the older archive and confirm it belongs to the intended account. Pause application writes when consistency matters; restoring a database does not merge orders or messages created after the backup.

1. If the archive is not already available, upload the compatible DirectAdmin backup to the account backup directory using an authorized transfer method. Keep it outside the public web root.
2. Open Advanced Features > Create/Restore Backups and choose the restore view.
3. Select the exact archive by name and date. Review the offered restore categories and select only the data required for this recovery.
4. Read the overwrite implications and start Restore Backup once. Avoid making unrelated panel changes while the restore is running.
5. Wait for the completion report in the message system. Review every warning, especially database, mail and file failures, before restoring customer access.
6. Test the recovered application and remove temporary public restrictions only after the intended state is confirmed.

Check important files, database records, mail folders and authentication as applicable. Confirm current DNS and external integrations remain appropriate; a restored account configuration can contain older values.

If the archive is not listed, check its location, permissions and supported format. If a restore is partial, retain the log and ask support to identify the failed component rather than repeatedly restoring everything. Preserve both recovery copies until data integrity and the next successful backup are confirmed.

• Creating and downloading a full DirectAdmin account backup
• Creating a selective email, FTP-settings or database backup in DirectAdmin
• Downloading an SQL database backup from DirectAdmin
• Deleting an obsolete DirectAdmin backup archive

• DirectAdmin Evolution: Backup
• DirectAdmin: Backup Restore Migration