WHM Backup Configuration: Scope, Storage and Recovery Checks

WHM backup configuration defines which data is captured, when it is captured and where it is retained. Enabling a schedule is not enough: a usable recovery plan needs a complete scope, capacity checks, protected off-server copies and periodic restore testing.

Define the recovery requirements first

List the accounts and components you need to recover, how much recent data loss is acceptable, and how long recovery can take. Include websites, databases, mail and required server configuration. Identify services hosted elsewhere so they are not silently omitted.

This is an authorized WHM administrator task. Use a provider-approved HTTPS hostname and valid certificate rather than the old unencrypted port-2086 example. Do not bypass a certificate warning or assume every reseller has these controls.

Review the WHM settings

Open Backup > Backup Configuration. Review enabled status, selected users, backup format, schedule, retention, disk-space checks and local storage. Select accounts deliberately; suspended accounts and new accounts need a defined coverage policy rather than an assumption that every user is protected.

Choose the database and system-file scope with your administrator. A raw copy of an active database directory is not automatically a consistent logical backup, and it is not interchangeable with a per-account SQL export. Server-level files can require a manual administrator recovery; an account restore does not rebuild every operating-system setting.

Keep recovery copies off the source

Add an authenticated encrypted remote destination and allocate local space for backup creation, queued transfers and restore staging. See the WHM SFTP destination guide for transport-specific checks.

Distinguish local and remote retention and consider what happens after a failed backup. Do not configure cleanup that removes the last usable copy before a new one is verified. An off-server account that the source can delete from is not automatically an immutable backup.

Verify actual backup coverage

1. Observe a scheduled run and inspect account-generation and transfer failures.
2. Compare the expected account inventory with completed local/remote archives and dates.
3. Retrieve a representative copy and restore it into a separate authorized environment.
4. Test the recovered website, databases, mail and required configuration. Document missing components and the time required to restore them.

Protect logs and archives from public access. Review the plan when software, accounts or retention requirements change. Do not force a full backup during peak production load simply to see whether the feature is enabled.

References: WHM Backup Configuration and cPanel system-backup recovery boundaries. Reviewed October 14, 2026. No customer backup schedule or restore was changed or executed.