WHM Backup Configuration: Incremental vs Compressed for Large Datasets

Backup Strategy for High-Volume Account Servers

Managing backups for servers with a high volume of large accounts requires a balance between disk I/O, local storage capacity, and the ability to move data to remote destinations. cPanel & WHM provides both compressed archives and incremental backups via the Backup Configuration interface.

Incremental backups utilize hard-linked directory trees to reduce disk space and execution time. However, this structure differs significantly from the portable tarballs generated by compressed backups, which are typically required for seamless transport to S3-compatible object storage or SFTP destinations.

When configuring retention policies for large datasets, there is a trade-off between the speed of local snapshots and the portability of the resulting archives.

• Compressed backups are I/O intensive but highly portable.
• Incremental backups are space-efficient but rely on a chain of snapshots for restoration.

What are the specific implications for remote transport when using incremental backups compared to compressed archives? Does the system automatically flatten incremental snapshots into portable archives during the transport process to additional destinations?