Rarod,
Thank you for bringing this issue back
From the information we gathered from your server, seems like the server load is caused indeed from cPanel's internal /script/restorepkg script.
I believe that this is a great example for "it's not a bug, it's a feature" case. I'll try to explain -
cPanel's internal /script/restorepkg system should accept "path/to/incremental_backup" as per their help -
Code:
[email protected] home2]# /scripts/restorepkg --help
/usr/local/cpanel/bin/restorepkg [--unrestricted] [--restricted] [--force] [--newuser <username>] [--allow_reseller] [--skipaccount] [--ip=(y|n|custom IP)] [--disable=<module>[,<module>]] -- [cpuser|/path/to/cpuser-file|/path/to/extracted-cpuser-file|/path/to/incremental_backup]
Regardless of JetBackup, let's make a test with a small account -
Create an incremental backup -
/scripts/pkgacct --incremental frooty /home2/
Restore the incremental backup -
/scripts/restorepkg --force /home2/cpmove-frooty
Although we used "incremental" backup to restore the backup, seems like cPanel will create an archive, and then will extract it again -
Code:
8683 frooty 20 0 121708 1244 960 S 14.0 0.0 0:00.42 /usr/bin/gtar --extract --no-same-owner --preserve-permissions --file - --no-wildcards-m+
8682 root 20 0 121860 1068 884 D 11.0 0.0 0:00.33 /usr/bin/gtar --create --file - --no-wildcards-match-slash --anchored --sparse --blockin+
This is also documented in the restore log -
Code:
[ 6581][RESTORE:1 ][A:frooty ]: ArchiveManager
[ 6581][RESTORE:1 ][A:frooty ]: Preparing archive for restoration …
[ 6581][RESTORE:1 ][A:frooty ]: This archive’s payload appears to be in the archive’s “cpmove-frooty” directory.
[ 6581][RESTORE:1 ][A:frooty ]: ArchiveManager
[ 6581][RESTORE:1 ][A:frooty ]: The system successfully prepared the archive for restoration.
When doing this with 18G account, you should expect high load
Going back to JetBackup, we are working on a workaround for this where you should be able to restore files directly to the homedir (reverse rsync), allowing much faster restores and using less CPU.