Use Admin Backup/Transfer to create account archives on a schedule and copy them to storage that survives a failure of the hosting server. A backup stored only beside the live website does not protect against loss of that server or its disks.
IN THIS ARTICLE
What you need before you begin
Choose a storage destination supported by the installed DirectAdmin version and your security requirements. Restrict its credentials and protect the archive because it contains private website, database and mail data. Estimate archive size, local staging space, transfer time and remote retention capacity.
01 Schedule off-server DirectAdmin account backups
- Open Admin Backup/Transfer and create a backup task. Select the accounts deliberately, including how new accounts will be covered in future schedules.
- Choose the required data types. For an account recovery plan, include website files, databases, mail data and account configuration rather than assuming a partial archive is complete.
- Set a schedule outside peak workload periods and avoid overlapping jobs. Check the server timezone and the expected duration.
- Configure the supported remote destination and test authentication and permissions. Prefer encrypted transport where supported; do not send sensitive archives over an untrusted plaintext path.
- Run one backup immediately, inspect completion messages and confirm the remote file exists with a plausible size. Define retention separately if the destination or task does not implement the policy you need.
- Restore a representative account into an isolated environment, then record the recovery steps and the credentials needed to retrieve the archive.
Is an account backup a complete server image?
No. DirectAdmin account archives and a server-level configuration or system backup serve different purposes. Document how the operating system, licenses, custom services and off-panel data will also be recovered.
Check the backup or recovered data
Check both the panel result and destination inventory. Confirm a later scheduled run completes without manual intervention and that old archives are removed only after newer usable copies exist. Monitor free staging space as well as remote capacity.
Troubleshoot unexpected results
An interrupted upload is not a successful remote backup. Investigate transfer logs, quotas, credentials and available temporary space. Keep a known-good archive while retrying. Do not automatically restore backups onto a DNS-clustered standby without planning how restored zones and addresses will affect live traffic.