Emergency server help: get in touch

What changed in DirectAdmin system backups after sysbk was replaced (1.709) — and what you must add

DirectAdmin 1.709 replaced the sysbk script with a built-in system backup that archives panel and service configuration but not user data; this guide explains what the new backup covers, how to configure it, and what you still need to back up separately.

Published Updated 8 min read

Update, 9 October 2026: corrected after an independent review. The 1.709 update moved custom paths into sysbk.custom_paths (we had said they were lost and belonged in sysbk.conf), the Roundcube database is still backed up, and remote copies use FTP or SCP. We removed a task.queue command we could not confirm, and the coverage check now uses a private temporary folder. We checked the files and settings on DirectAdmin 1.712; we did not run a full system backup for this update.

Applies to DirectAdmin 1.709 and later

Short answer: From 1.709, System Backup (Admin Level → System Backup) runs a script bundled with DirectAdmin. Its settings are in /usr/local/directadmin/data/admin/sysbk.conf. Extra paths are in /usr/local/directadmin/data/admin/sysbk.custom_paths, where the update merged your old custom.dirs and custom.files lists. User home directories and user-owned databases are no longer included (DirectAdmin’s own Roundcube database still is), so keep the admin-level backups as well. Check the custom path list, confirm the paths really are in an archive, and keep both backup types off the server with a tested restore procedure. (Reviewed October 2026.)

For many years DirectAdmin servers had a system-level backup script called sysbk that archived /etc, the panel’s configuration and a few other directories to a local path or remote host. In 1.709 the System Backup page switched to a backup script bundled with DirectAdmin. During the update its settings file moved to /usr/local/directadmin/data/admin/sysbk.conf, and the old custom.dirs and custom.files lists were merged into one list, /usr/local/directadmin/data/admin/sysbk.custom_paths. The change is welcome because sysbk was a shell script with a long list of hard-coded paths, but the new backup has a narrower scope than some administrators expect, and a server that relies on it alone is not recoverable.

What the new system backup covers

The system backup is for server configuration. On our DirectAdmin 1.712 lab server (checked 9 October 2026), sysbk.conf has on/off switches for the web-server, DNS (BIND) and MySQL parts and for the custom path list, plus the local backup path and the remote copy settings. DirectAdmin’s 1.709 change log says user home directories and user-owned MySQL databases are no longer included, and that the Roundcube database (da_roundcube) is. Which files end up in the archive depends on your build and settings, so check a real archive (shown below) rather than trusting a list in any guide, this one included.

What it does not include is the substance: user home directories, mailboxes and user-owned databases. These are covered by the admin-level backups described in Admin, reseller and user backups. The system backup is the complement to those, not a replacement, and the two together are the minimum for a full restore.

Configuring it

The settings file is a shell-style KEY="value" file. Review at least where backups are written and whether they are copied off the server. These are the setting names on our 1.712 lab; check yours:

grep -E '^\s*(BACKUP_PATH|USE_RTRANS|RTRANS_METHOD|FTP_HOST|SCP_HOST|CUSTOM_BK)=' /usr/local/directadmin/data/admin/sysbk.conf

BACKUP_PATH is the local folder; it needs enough free space. USE_RTRANS="1" turns on the remote copy, and RTRANS_METHOD is ftp or scp, with the matching FTP_ or SCP_ settings (remote FTP also needs the ncftp package). Pick a time that does not collide with the admin backup run, because both compress heavily and running them together doubles the I/O spike. Results appear in Admin Level → Message System, and the run is logged to /var/log/directadmin/sysbk.status.log.

If you had customised the old sysbk to include extra directories or files (a custom scripts folder, an application deployed outside /home, a Redis dump directory), the 1.709 update moved them for you. It merged the old custom.dirs and custom.files lists into sysbk.custom_paths, one path per line, and removed DirectAdmin’s own paths and user home directories from the merged list. Check that every path you depend on is still there:

cat /usr/local/directadmin/data/admin/sysbk.custom_paths

Add missing paths to sysbk.custom_paths, not to sysbk.conf, which holds the settings. Then confirm in a real archive that they were backed up (see the check below). A path that is not in the archive is not backed up, and there is no warning.

To run it straight away rather than waiting for the schedule, start it from Admin Level → System Backup and follow the log:

tail -f /var/log/directadmin/sysbk.status.log

An earlier version of this guide gave a task.queue line to start the backup from the shell. We could not confirm that syntax for a current build, so it has been removed.

What you must add yourself

The system backup and the admin backups together still leave gaps that a serious hosting operation closes separately.

  • Operating system packages and kernel state. Neither backup records the installed package list. Dump it daily so a rebuild can reinstall the same packages: rpm -qa --qf '%{NAME}\n' | sort > /root/pkglist.txt on AlmaLinux, or dpkg --get-selections on Debian, and add the file to sysbk.custom_paths.
  • Database server configuration and binary logs. Check that /etc/my.cnf and /etc/my.cnf.d/ are in the system backup archive, and add them to sysbk.custom_paths if not. If you use binary logs for point-in-time recovery, they need their own copy job; the admin backup takes a logical dump per account, not the binlogs.
  • Off-server copies. A backup on the same disk is a convenience, not protection. Push both backup types to a remote target, and keep at least one copy that the server cannot delete or overwrite (object-lock on S3, or a pull-based rsync from the backup host).
  • A restore procedure. Write down the order: install the OS, install DirectAdmin with the same license, restore the system backup, run ./build all d or the targeted rebuilds to regenerate service configuration, then restore the admin backups. Test it on a throwaway VM once so the notes reflect reality.
  • Secrets that live outside the panel. API keys in /root/, SSH host keys if you want clients not to see a changed fingerprint, and any application .env files outside user homes.

Common pitfall: trusting the message system alone

The message system tells you a backup ran, not that it is usable. A backup that succeeds while silently excluding a path you forgot to add reports success every night. Once a quarter, and after every DirectAdmin update, list a system backup archive and compare it with the live server. Replace ARCHIVE.tar.gz with one of your system backup archives; the lists go into a private temporary folder:

t=$(mktemp -d)
tar tzf ARCHIVE.tar.gz | sed 's#^\./##' | sort > "$t/inbackup.txt"
find /etc /usr/local/directadmin/conf /usr/local/directadmin/data -type f | sed 's#^/##' | sort > "$t/live.txt"
comm -13 "$t/inbackup.txt" "$t/live.txt" | head -n 50
rm -rf "$t"

Each line printed is a file that is on the server but not in that archive. Some of it will be noise, and some of it will be the file you would have needed.

Keep it running

Schedule the system backup nightly and the admin backup nightly or weekly according to how much data you can afford to lose, and confirm both offsite. Run our backup verify script on the receiving host so a missing or truncated archive raises an alert the same day. After every DirectAdmin update, check sysbk.custom_paths and repeat the archive comparison: a configuration directory added by a new release is only backed up if the bundled script includes it or you add it.

Official documentation: DirectAdmin 1.709 change log: system backup script update, DirectAdmin documentation.

Related guides: Admin, reseller and user backups in DirectAdmin: remote FTP/S3 targets and restores · Certificate not renewing on DirectAdmin: reading the Provisioning History page and lego output · Consolidate snapshots when ESXi reports “Virtual machine disks consolidation is needed”.

Frequently asked questions

Does the DirectAdmin system backup include user websites and databases?

No. Since 1.709 it leaves out user home directories, mailboxes and user-owned MySQL or MariaDB databases (DirectAdmin’s own Roundcube database is still included). Those are covered by the admin, reseller and user backups, and a full restore needs both types.

How long does the system backup take to run?

Usually a few minutes, because it archives configuration directories measured in megabytes rather than user data; the time grows with the paths listed in sysbk.custom_paths and with a slow remote destination.

Can I undo this?

There is nothing to reverse in the backup itself, but the retired sysbk script is not restored by any update; the 1.709 update moved the old script’s extra paths into sysbk.custom_paths, so check that list. A wrong backup path or remote copy setting is corrected in sysbk.conf.

Maintenance record

This guide changes servers, data or security settings, so we re-check it against current versions on a fixed schedule. Take a backup or snapshot before you start.

Maintained by
srvScripts editorial team
Supported versions
DirectAdmin 1.709 and later
Last full review
Next review

Share this guide

Free website test

Is your website set up right?

Check SSL, security headers, redirects, robots.txt, sitemap, llms.txt and security.txt in one test. It takes about 30 seconds.