DirectAdmin Backups and Restore — Complete Guide

DirectAdmin handles backups with a different philosophy than cPanel — simpler, more transparent, and with the actual archive files visible in your file manager. Once you understand the workflow, you can back up your whole site, individual databases, or specific directories with a few clicks. This guide covers everything from on-demand backups to scheduling and restore.

What gets backed up

A DirectAdmin full backup includes:

• All files in your /public_html/ and home directory.
• All databases and database users.
• Email accounts, email storage, mailbox configurations.
• DNS zones for your domains.
• Domain configurations (subdomains, parked, addon).
• FTP accounts.
• Forwarders, autoresponders, mailing lists.

Output is a single .tar.gz archive — restorable on any DirectAdmin server, useful for migrations.

Creating a manual backup

1. Log in to DirectAdmin.
2. Navigate to Account Manager → Create/Restore Backups (User level).
3. Under Create Backup, select what to include:
   • Home Directory (files).
   • Domain configurations.
   • Email accounts/data.
   • Databases.
   • (Tick all for a full backup.)
4. Click Create Backup.

Backup runs server-side. Progress is shown; for large accounts it can take 5-30 minutes. When complete, the backup file appears under Existing Backups with a download link.

Download the archive to local storage. The backup file is also stored under /home/youruser/backups/ on the server until you remove it.

Automatic / scheduled backups (admin-level)

iWebVault’s DirectAdmin servers run server-level scheduled backups handled at the admin level. Daily, weekly, and monthly snapshots are created off-server, similar to JetBackup on cPanel servers. You don’t need to configure these — they run automatically.

For users wanting an additional layer (on top of our server-level backups), manual backups via the User panel give you copies you control directly.

Restoring from a backup

Restoring a full backup file

1. Navigate to Account Manager → Create/Restore Backups.
2. Under Restore Backup, the backup files in /home/youruser/backups/ are listed.
3. If your backup file is elsewhere, upload it via File Manager to /backups/ first.
4. Select which components to restore (home dir, domains, mail, databases).
5. Click Select Restore Options → Restore.

The restore overwrites your current state for the selected components. Use carefully — you can’t undo a restore without another backup.

Restoring a single file or directory

DirectAdmin’s user-level restore is all-or-nothing for the components included. To restore one file:

1. Download the backup .tar.gz.
2. Extract it locally (Mac/Linux: tar -xzf backup.tar.gz; Windows: 7-Zip).
3. Find the file you need in the extracted tree.
4. Upload that single file back via File Manager.

For frequent single-file restores, consider asking us to restore from our server-level backup system — we can pull individual files from any backup point without the user-level full-restore overhead.

Restoring a single database

1. Extract the backup archive.
2. Find backup/databases/yourdb.sql.
3. In DirectAdmin → MySQL Management → phpMyAdmin → select the target database → Import → upload the .sql file.

For very large databases that timeout on web import, upload the SQL file to the server via File Manager and contact support to import from the command line.

Storage location and disk usage

User-level backups live in /home/youruser/backups/. They count against your disk quota.

Practice: download backup → delete from server → keep local copy. Avoids consuming disk for backups that don’t need to live on the server.

The server-level (off-server) backups iWebVault maintains separately don’t count against your quota — those exist outside your account.

Migration use case

One of DirectAdmin backup’s killer features: portability. To move an account between DirectAdmin servers:

1. Source server: create full backup, download.
2. Target server: upload backup to /backups/ in the new account.
3. Target server: restore.

Site is essentially cloned. Then update DNS to point at the new server and you’re done.

Backup strategy that works

• Server-level backups (automatic, by us): daily/weekly/monthly snapshots, off-server. No action needed.
• Manual backups (occasional): before any risky change (major plugin update, theme switch, file migration). 5 minutes of insurance.
• Periodic downloads (monthly): grab a backup to your own storage. Independent copy you control.
• Application-level backups (continuous): WordPress + UpdraftPlus, or your framework’s equivalent. Finer-grained restores than full-account snapshots.

Common DA backup issues

“Backup creation fails with disk space error.” The backup needs roughly as much free space as your account uses. If you’re at 90% quota, the backup can’t be created locally. Free space, or contact support to back up to external storage.

“Restore says ‘invalid backup format’.” The file isn’t a DirectAdmin user backup. cPanel backups, pkgacct files, or random tarballs won’t import. Verify the file came from a DirectAdmin user-level backup.

“Backup downloads but the .tar.gz is corrupted.” Slow connection, partial download. Re-download. Use a download manager that supports resume for large files.

“Restore completed but site is broken.” Backup was older than expected — restored to a state before some critical config change. Either restore from a more recent backup, or manually re-apply the missing changes.

“Want to schedule user-level backups.” The User panel doesn’t directly schedule. Workaround: cron job that calls the DA backup API (advanced). Simpler: rely on our server-level scheduled backups, supplemented by manual ones before changes.

What’s next

• Database management for selective restore: DirectAdmin databases.
• File-level access: DirectAdmin File Manager and permissions.
• Migration overall: Migrating a domain.

DirectAdmin backups are transparent — you can see the files, download them, restore them. Combined with our server-level backup infrastructure, you get a robust multi-layer safety net without complexity.