Changing Compression levels

[ChuckS42]

Sorry if this has been answered elsewhere, but if so I cannot find it.

Just upgraded to V7. Is there anything special I need to do if I want to change my Compression level from the new "High" to the new "Optimal"? In other words, can I just change it and be done, or do I have to start a new Active Full with the new setting, or even an entirely new job?

[Vitaliy S.]

Hi Chris,

In order to apply new compression settings, you need to run an active full backup.

Thanks!

[cparker4486]

Vitaliy,

Is the v6 Extreme equivalent to the v7 High or v7 Extreme? Even better, is there a document that explains the changes there? I don't see it in Release Notes.

[Vitaliy S.]

Extreme is the same in both versions, while V6.5 Optimal = V7 High.

Our new default compression level with a proprietary algorithm implementation leverages advanced CPU instruction sets (SSE extensions). There are no other changes in compression levels. Please find the description of all compression levels in our User Guide (page 40).

[ChuckS42]

by Vitaliy S. » Wed Aug 21, 2013 8:04 pm
Hi Chuck,

In order to apply new compression settings, you need to run an active full backup.

Thanks!

By any chance will Veeam automatically see that I've changed the compression setting and run a new Full on its own? Or do I need to do that manually?

[Vitaliy S.]

You need to do that manually, Veeam will automatically apply new compression settings on the next scheduled active full job run.

[m.novelli]

You need to do that manually, Veeam will automatically apply new compression settings on the next scheduled active full job run.

Hi Vitaly, all my customers Veeam servers are set to run a full backup on Saturday. It's not clear to me if I should run manually a Full Active Backup or if is enough my default configuration

Thanks

Marco

[Vitaliy S.]

It appears that in new version there is no need to trigger this run manually, all settings will be applied automatically on the next job run. New full is required only if you change storage optimization settings.

[m.novelli]

Excellent!

Marco

[oli4]

Hello all
We have upgraded from Veeam B&R V6.5 to V7. We are doing daily incremental Veeam Backups with monthly Full Backups.

I have now a question abou the change of the compression level during upgrade from V6.5 to V7. In the manuals Veeam stated the following:

If you are upgrading to 7.0 from the previous version of Veeam Backup & Replication, consider that compression level you have previously set for your jobs will be preserved (compression level named Optimal in version 6.5 will appear as High in the user interface after the upgrade). However, all the newly created jobs will have the new compression level in effect.

What does this exactly mean? The compression level shows High after upgrade but still uses Optimal? Or does the level now shows High and after a Full Backup also uses High?
And what is the difference between the V6.5 Optimal and the V7 High level? Is there any? Or is the V6.5 Optimal the V7 High?

Regards
Oli4

[foggy]

Please review the thread above for the answers. You jobs will continue to use the same compression algorithm (now called High) until you explicitly change it to the new Optimal level. The new Optimal compression algorithm uses significantly less CPU resources, however provides a bit less savings.

[haslund]

Is there any difference if Backup mode is Reverse Incremental or Incremental?
...or how is it handled when you have the reverse incrementally created VBK file in Optimal compression and the new incremental run is in Extreme compression fx?

Will the newly reverse incrementally created full vbk file then contain a mix of optimal compression blocks and extreme compression blocks?

The documentation suggests just running the job will be fine: http://helpcenter.veeam.com/backup/70/h ... ation.html
However I am under the impression that for a backup job using Reverse Incremental I will be forced to run an Active Full before any new backups will use the new compression level.

[foggy]

Yes, it will contain a mix of blocks with different compression levels (each block has its own compression level flag). So on-the-fly change of compression levels is supported, no need to perform an active full.

[haslund]

Thank you for the clarification foggy.
It would be super cool if the documentation explained this in the same manner as you just did.

[foggy]

I will ask documentation team to update the corresponding topic appropriately.

[b.vanhaastrecht]

Hi,

What will happen to a regular backup job's data if we would disable the option to decompress before storing on a repository.
- Will existing data be compressed?
- Will synthetic full compress previous uncompressed full data when creating a new synthetic full file?
- Is a active full perhaps needed?

I would like to get an overview of impact if we are going to disable the decompress before storing option.

Kind Regards,
Bastiaan

[foggy]

I assume it works the same way as changing compression level in the job (see above). Existing data will not be compressed, synthetic full will contain both compressed and uncompressed data, no active full is required for this setting to take effect.

[b.vanhaastrecht]

So only blocks that change gets compressed. So if we want to acchive full compression, we do need a full run?

[foggy]

Correct, active full will result in the new fully compressed backup file. Previous backups will be left intact.