[SOLVED] backup no longer compressing after upgrade to 4.2

[vkhera]

I upgraded all nodes in my cluster from 4.1 to 4.2 on Friday (April 29). Since then, all backups are no longer compressed. I just verified that the "LZO" option is selected in the backup configuration.

Is anyone else noticing this?

From one of my small VMs that backs up weekly:

[filer]% ls -l vzdump-qemu-100-2016_04_*
-rw-r--r--  1 root  wheel        4304 Apr 16 02:46 vzdump-qemu-100-2016_04_16-02_45_02.log
-rw-r--r--  1 root  wheel  1701051105 Apr 16 02:46 vzdump-qemu-100-2016_04_16-02_45_02.vma.lzo
-rw-r--r--  1 root  wheel        3671 Apr 23 02:46 vzdump-qemu-100-2016_04_23-02_45_01.log
-rw-r--r--  1 root  wheel  1703106758 Apr 23 02:46 vzdump-qemu-100-2016_04_23-02_45_01.vma.lzo
-rw-r--r--  1 root  wheel        7818 Apr 30 02:49 vzdump-qemu-100-2016_04_30-02_45_02.log
-rw-r--r--  1 root  wheel  4012897792 Apr 30 02:49 vzdump-qemu-100-2016_04_30-02_45_02.vma

Other VMs that backup daily currently show all backups as uncompressed, since I only keep three.

 

[dcsapak]

it seems you created the backup tasks precisely at the wrong time
we had a short time, where vzdump would take 'lzo' as the default value (if no option was set), and the gui set no option when lzo was selected
now, vzdump does only compress when the option is given and the webgui does this correctly (although it seems that a missing value is still interpreted as lzo)

it should work if you set it once to 'none' (click ok) and the again to 'lzo'
this should write a new cron entry where the option is there

hope this helps

 

[vkhera]

Yes, that solved the issue. Thanks!