Direct Admin Backups

1. How to Create the Backup

As a reseller, you have access to the “Manage User Backups” tool. This is more powerful than a standard user backup because it can package all your sub-accounts simultaneously.

Steps to Backup:

  1. Log in to your DirectAdmin Reseller Level dashboard.
  2. Navigate to Reseller Tools > Manage User Backups.
  3. Step 1 (Who): Select “All Users” to ensure every client account under your wing is included.
  4. Step 2 (When): Select “Now.”
  5. Step 3 (Where): * Local: Saves to your current server (you’ll need to download it via FTP or File Manager afterward).
    • FTP/SFTP: Highly Recommended. This sends the backup directly to a storage location under your control (like a home NAS, a different VPS, or a cloud storage mount).
  6. Step 4 (What): Ensure “All Data” is selected.

2. The “Migration” Reality Check

While you can easily back up your data, restoring it to a new reseller account at a different company has some technical hurdles:

The Permission Hurdle

Standard Reseller accounts usually do not have the permission to “Restore” backups that they didn’t create on that specific server. This is a security measure to prevent resellers from accidentally overwriting system settings or other users.

The Solutions:

  • The “Helpful Host” Method: Most new hosting providers will perform a “cPanel/DirectAdmin Migration” for free. You simply give them your backup files (or your old login), and their Root Administrators will restore them for you. Since they have Root access, they can bypass the restrictions that standard resellers have.
  • The Manual Method: If you are forced to do it yourself without host help, you would have to recreate each user account manually and then restore the individual user backups one by one at the User Level. It’s tedious, but it works.

3. Best Practices for Control

To truly be “under your control,” don’t just keep the backups on the same server.

  • Remote Storage: Use a service like Wasabi, Backblaze B2, or even a cheap storage VPS.
  • Frequency: Set up a “Cron Job” in the Manage User Backups section to automate this weekly or daily.
  • Test It: Download one backup file and check that it contains your public_html and mysql folders.

[!IMPORTANT] A backup is only as good as its last successful test. Every few months, try restoring a single low-stakes site to a different environment to ensure the files aren’t corrupted.

Setting Up the Automated Transfer

In the Manage User Backups menu, you can configure the transfer directly to your storage servers.

Configuration Details:

  • Transfer Protocol: Use SFTP (Port 22). Standard FTP sends your credentials in plain text, which is a risk when sending data across the open web.
  • Path: Specify a dedicated folder on your storage server (e.g., /backups/directadmin/).
  • Scheduling: Under “Step 2,” choose “Cron Schedule.” A common practice for resellers is a weekly full backup or a daily incremental if your storage allows it.

Important Technical Note: The “Admin” Factor

When you move to a new provider, you will likely encounter the IP and Nameserver mismatch.

  1. IP Addresses: Your backups contain the IP address of your current host. When restored to a new host, the sites won’t work immediately. The new host’s admin will need to run the DirectAdmin ipswap.sh script or manually change the IPs in the User settings.
  2. DNS: Ensure your TTL (Time to Live) on your DNS records is set low (e.g., 300 seconds) if you suspect you’ll need to move soon. This makes the “switch” to the new server happen almost instantly once you update the records.

Summary of the “Control” Workflow

StepActionLocation
1. ExportDirectAdmin packages Users into .tar.gz files.Current Reseller Host
2. TransportAutomated SFTP transfer.The Web
3. StorageFiles sit encrypted on your hardware.Your Storage Servers
4. ImportNew Host’s Root Admin restores the files.New Reseller Host

One Final Tip: The “Reseller Config”

DirectAdmin backups generally include user data, emails, and databases, but they don’t always include your specific Reseller-level customizations (like custom Skin packages or specific ACL/Command Layer settings).

If you have spent a lot of time customizing “Packages” for your clients, make sure to take screenshots or notes of those configurations. Those usually have to be recreated manually on a new server before you import the users.

gemini.google.com