Validating a remote WHM backup destination

Choose a supported transport with encryption and sufficient remote capacity. Prepare narrowly permitted credentials and a unique per-server path so multiple servers cannot overwrite or prune one another’s files.

1. Open Backup Configuration > Additional Destinations, select the supported destination type and create a new destination.
2. Enter the real host or storage identifier, path and protected credentials in the format requested. Do not add a web URL scheme to a field expecting only a hostname.
3. Decide whether the destination receives account data, system data or only logs. Avoid selecting a logs-only option when you expect full backups.
4. Save and run the destination validation. Read the result and correct path, authentication, network or permission errors.
5. Complete an actual backup transfer, inspect its presence remotely and retrieve a test copy. Verify restoration with the intended method before relying on the destination.

The destination should receive complete backup sets in its unique location, with retention and deletion permissions behaving as intended. Keep alerting active for later credential expiry or storage exhaustion.

If validation succeeds but large transfers fail, check timeouts, bandwidth, remote capacity and transfer logs. Some backup types only support particular transports, such as incremental backups with supported Rsync destinations. Do not remove the only working local copy before remote recovery is demonstrated.

Separate credentials and paths reduce the impact of mistakes or compromise. Grant only the operations the backup workflow needs and document how to rotate the key without interrupting scheduled protection.

• Configuring WHM backups and retention for the available storage
• Investigating a failed WHM backup job
• Restoring an account from a WHM backup
• Choosing which accounts participate in WHM backups

• cPanel: Backup Configuration