Skip to main content
Answer

Recommendation: Software compression with deduplication

  • June 3, 2025
  • 1 reply
  • 83 views

Forum|alt.badge.img+3

We are currently switching to deduplicated storage as part of our migration to plans and therefore looked into recommended settings for everything to work smoothly and the most space efficient.

I already noticed our Commcell had the horizontal scaling option disabled as we upgraded from older versions which resulted in the old default behaviour.

Upon enabling I can now see two DDBs for the two data types we currently backup to this pool: Files and Databases.

From previous experimenting we noticed improved deduplication savings when using no compression for file backups.
For databases it seems the other way around as also suggested in the documentation.

This got me wondering:

  • Is compression with deduplication also recommended for File or VSA backups?
  • If we disable compression on the DDB (e.g. Files), will the setting persist when the DDB is sealed? (because we use WORM/S3 OL)

Best answer by Jon Vengust

Hi Marcel_RE,

 

Typically, software compression is often paired with deduplication to maximise space savings. With that in mind, yes it is recommended to have software compression enabled for File and VSA backups. 

 

Regarding your query about setting persistence, compression would be set at the policy level which the new DDB will inherit as a result.

 

1 reply

Jon Vengust
Vaulter
Forum|alt.badge.img+9
  • Vaulter
  • Answer
  • June 6, 2025

Hi Marcel_RE,

 

Typically, software compression is often paired with deduplication to maximise space savings. With that in mind, yes it is recommended to have software compression enabled for File and VSA backups. 

 

Regarding your query about setting persistence, compression would be set at the policy level which the new DDB will inherit as a result.