Hello,
I'm using pigz for backup (pigz=1 in vzdump.conf). It really helps because of smaller archive size, and in my case the bottleneck is slow backup storage. Therefore, smaller backups writes faster and take less space. But recently I discovered that restore uses gzip, not pigz (you can see it in the process list). This is really confusing. I was sure the option in vzdump.conf tell Proxmox to use pigz instead of gzip for backup and restore, but it uses gzip for restore. And restore with gzip takes more time than backup with pigz.
As I understand it, I can just make simlink /bin/gzip -> /usr/bin/pigz. Pigz options seems fully compatible with gzip. In this case I don't need option in vzdump.conf. But i will need to check simlink every time I install updates, in case some gzip update overwrite it.
Is there more proper way to do this? Maybe there's another option in some configuration file, like pigz=1 in vzdump.conf?
I'm using pigz for backup (pigz=1 in vzdump.conf). It really helps because of smaller archive size, and in my case the bottleneck is slow backup storage. Therefore, smaller backups writes faster and take less space. But recently I discovered that restore uses gzip, not pigz (you can see it in the process list). This is really confusing. I was sure the option in vzdump.conf tell Proxmox to use pigz instead of gzip for backup and restore, but it uses gzip for restore. And restore with gzip takes more time than backup with pigz.
As I understand it, I can just make simlink /bin/gzip -> /usr/bin/pigz. Pigz options seems fully compatible with gzip. In this case I don't need option in vzdump.conf. But i will need to check simlink every time I install updates, in case some gzip update overwrite it.
Is there more proper way to do this? Maybe there's another option in some configuration file, like pigz=1 in vzdump.conf?
Last edited: