How to Back Up WordPress by DirectAdmin

admin

4 hours ago

How to Back Up WordPress by DirectAdmin backup tutorial showing files database offsite storage and restore verification

How to Back Up WordPress by DirectAdmin is for DirectAdmin users, resellers, and server admins who need a panel-level backup path for WordPress. Use this method when hosting-account backups, reseller-managed backups, and server migrations where WordPress is one site inside a DirectAdmin account.

A good WordPress backup includes the website files and the database. The files carry themes, plugins, uploads, configuration, and custom code. The database carries posts, pages, users, settings, WooCommerce orders, booking records, form entries, menus, and plugin data. Before you change WordPress core, PHP, DNS, plugins, themes, checkout, or a page builder, make sure you know which backup contains both halves.

When this backup method makes sense

DirectAdmin user or admin backups is a good fit when you already have that tool available and need a practical restore path. It is especially useful before updates, redesign work, hosting migrations, malware cleanup, PHP changes, database work, and plugin troubleshooting.

Before you begin

Confirm the WordPress URL and document root so you back up the right site.
Find the database name in wp-config.php or the hosting panel.
Check free disk space; many backup failures start with a full account.
Pause risky work until the backup finishes and you can see the file.
For stores and booking sites, note the last order, booking, or form entry before the backup.

Backup steps

Open DirectAdmin and find the backup or create/restore backup area available to your access level.
Select the website files and MySQL database data needed for the WordPress site.
Create the backup and wait for DirectAdmin to finish packaging it.
Download the backup or move it to a remote backup location configured by the admin.
Record which database belongs to the WordPress site by checking wp-config.php.
For admin-level backups, confirm the account can be restored from the Admin Backup/Transfer area.

Automated backups and cron

DirectAdmin admins can configure user backups and remote backup transfer workflows. For one WordPress site, combine panel backups with plugin or database-specific backups before risky changes.

For WordPress plugin backups, remember that WordPress scheduled tasks often depend on WP-Cron. WP-Cron runs when WordPress receives traffic and notices a task is due. That is fine for many small sites, but low-traffic sites can run late. For business-critical sites, pair plugin schedules with a real server cron, hosting-panel backups, or provider backups where available.

How to test restore readiness

Restore through the DirectAdmin restore workflow for backups created by DirectAdmin. For partial manual restores, extract the site files and import the matching database carefully.

Do not test your only restore for the first time during an outage. Use a staging copy, temporary subdomain, local development environment, or provider restore preview when available. After restore, check login, home page, important pages, media, forms, checkout, email delivery, permalinks, and cache behavior.

Common mistakes

Restoring an entire user account when only one site needed recovery.
Not checking database compatibility before restoring old SQL dumps.
Backing up files without database data.
Not monitoring long restores for large accounts.

Where to store the backup

Keep at least one copy outside the web server. Good destinations include your own Google Drive, Dropbox, OneDrive, S3-compatible storage, Backblaze B2, Wasabi, SFTP, a provider backup vault, or a secure internal backup server. The exact tool matters less than the restore test, retention policy, and separation from the production account.

Fix I.T. Phill recommendation

Use DirectAdmin user or admin backups as one layer, not the whole plan. Keep a second backup path for important sites, especially WooCommerce, bookings, memberships, and agency-managed sites. Before major updates, take a fresh manual backup even if automatic backups are already scheduled.