Salta al contenuto principale

Compression rate still cannot be adjusted on existing backup tasks

Thread needs solution

Since release this issue was classified as known by the support team, yet there is still not update which fixes this issue and it starts to get very annoying.

I refuse to wait for TI 2016, just because you will not fix your own issues introduced with TI 2015.

Please fix that one can change the compression rate in an existing backup task
> extended options > Performance.

This worked for all releases of True Image since 2009 and I cannot accept the current state.

Allegato Dimensione
screenshot_165.png 48.81 KB
0 Users found this helpful

I cannot comment on your preference to be able to change the compression during the course of a backup chain, but I disagree this is a bug.

I am open-minded to explain why it is a bug:

a. Let's assume the following situation:

1. you configure a backup, which can have quite complex settings.
2. you choose a compression rate
3. you find out that the CPU is bottlenecking the transfer speed to the backup target because the cpu is incapable of providing enough power for the process
4. you may simply want to abort the backup and select a different compression.

This was valid through all TI versions till TI 2014. Not so for TI 2015. You need to create a new backup job, not even cloning will unlock the setting. This is known to the Acronis support (2nd level) and even they are unhappy about that and consider this as a bug.

I hope this explains why it simply doesn't make change to change this feature at all compared to all previous TI version. As a MVP you should have a good understanding, that the issue is not that I would like to change the compression in a chain, because I agree this might not be that important.

b. Hence it is not completely useless to want that. First of all every backup has his own checksum so changing a compression level would not make previous backups invalid. You may want to change the compression even during a chain of backup.
Ineviteably the compression does not only affect the size but also affect the speed of the backup based on CPU requirement, also when restoring.
For this you might want to change the compression if you notice that you run out of space in a complex chain (perhaps because you wrongly adapted the data growth) but you need to maintain the numbers of backups to comply with security rules.

bumped because there is no official comment on this yet this bug still exists.