Skip to main content
Question

Commvault Backup Options

  • June 1, 2026
  • 2 replies
  • 40 views

Forum|alt.badge.img+9

Can Commvault store full backups and incremental backups in separate buckets, with immutability enabled only for the full backup bucket, to optimize costs? If feasible, what are the pros, cons, and key considerations of this design?

2 replies

Lukas3D
Explorer
Forum|alt.badge.img+13
  • Explorer
  • June 1, 2026

Hi,

That won't work under the hood. Due to the built-in software deduplication, the system breaks data down into millions of small chunks rather than structured .bak files, meaning there is no distinct file-level separation between fulls and incrementals.

 

Ideally, we'd handle this via mixed retention on a single copy (e.g., 14 days immutable, transitioning to non-immutable for the rest of the month to save costs), which is a feature I've requested in the past, but as of now technically it won’t be possible. 

 

As it stands, the only workaround is to split this into two separate copies: a standard non-immutable copy for daily backups, and a separate immutable copy for e.g. weekly fulls. Unfortunately, because of the two sets of data involved, this approach won't offer the cost optimization you are looking for.


Erase4ndReuseMedia
Community All Star
Forum|alt.badge.img+17

While you could conceivably use the “Incremental Storage Policy” feature to separate your Full and Incremental backup data, any level of cost optimisation would be highly dependent on your retention requirements.