I'd first suggest actually installing Munin via WHM->Cpanel->Manage Plugins, wait a day or two, and then look at WHM->Munin->Network to see what network usage is happening at the time. (If your data center doesn't provide this information and you've got no 3rd party monitoring in place).
You might want to look at changing the backup times (under Server Configuration->Configure cPanel Cron Jobs) if 2am is a busy time for you. I'm not aware of a in-built cPanel bandwidth/throughput limiting thing for backups.
You could try, under WHM->Tweak settings, to reduce the compression settings (which will then reduce the CPU usage, but will increase the filesize of the backups) and also under Tweak Settings->Settings, you could change the "I/O priority at which nightly backups are run" and under Tweak Settings->Stats and Logs->"Extra CPUs for server load" you could reduce that setting.
You could look at using IPTables to rate limit outbound packets to S3 (see ServerFault
for inspiration on how to do this). However, since S3 operates on ports 80/443, you'll need to be careful to restrict this to S3's IP range as otherwise things such as calls to Paypal/Stripe etc for payment confirmations will be impacted - Amazon do make their IP ranges available (see their knowledge article
), but it will involve keeping the list up to date.
Jetbackup does offer a CPU Limit, IO Read limit and IO Write Limit restrictions (under Settings->Resource), but whilst that does support S3, Backback and many others, I can't see a way of limiting the used bandwidth within it.
The other alternative I can think of is to just save the backups locally and then use rsync with the --bwlimit
setting to push up to S3 (which you could then use WHM's Backup Configuration->Custom destination to setup) OR you could try modifying the appropriate file /var/cpanel/backups/ (which is read by /usr/local/cpanel/Cpanel/Transport/Files/AmazonS3.pm ) to add the max_bandwidth
parameter and see if it works (I haven't tried it myself).
[ Edit: I've just noticed that you *might* be able to use
aws configure set default.s3.max_bandwidth 5MB/s
as root from the command line to limit it - according to this blog post