01
Installs next to JetBackup
A WHM plugin. It doesn’t turn off or change what’s already running.
02
Copies in parallel
Makes its own backups, in a separate folder and index, on the same destination. Compare both.
03
Flip the switch when ready
Stops and disables JetBackup’s services without uninstalling. You can turn it back on until you confirm removal.
The path of a backup
Your server
conta01 … conta68
files · email · databases
Salvo agent
runs on the server itself
compresses · dedupes · encrypts
Your storage
local disk or SFTP; S3 planned
encrypted data only
JetBackupJetBackup keeps running in parallel, in a separate folder on the same destination, until you flip the switch.
Space at the destination
How much the backup of 12 accounts took
100% is the size of the accounts at the source (6.11 GB).
Splitting by account costs 28% more than a single repository, but keeps each account isolated for restores and deletion.
Source, uncompressed
6.11 GB
Salvo: one repository per account, zstd-fastest
2.94 GB
One repository for all, zstd-fastest
Source: Compression vs deduplication · Oct 15, 2026
2.30 GB
Calculator
How much your server would take
An estimate: move the controls to your server’s size.
202 GBOn Salvo, per account · 3 GB per account, on average
Source, uncompressed
420 GB
On Salvo, per account
202 GB
One repository for all
218 GB estimated savings
estimatedEstimate based on 12 WordPress accounts (6.11 GB) measured on Oct 15, 2026, first copy. Results vary with content: videos and already-compressed files save less.
160 GB
What gets copied
FilesEach account’s folder, incrementally: only what changed is read again.
EmailIn the cPanel phase: each mailbox on its own, so you restore only the one you need.
DatabasesMySQL and MariaDB, one dump per database: InnoDB without locking; MyISAM locked only while copied. PostgreSQL not yet.
ConfigurationOn cPanel, through pkgacct: domains, DNS, email accounts, database users, SSL, cron and FTP.