Question

Change Storge policy on VMgroups

Forum|Forum|10 days ago
June 12, 2026
3 replies
24 views

+1

Zawro
Apprentice

Hi, I’m chatting with Commvault chat bot and I have a question. Can someone explain what happens in the following case:

I have a VM group that is assigned to Storage Policy X with deduplication, and incremental backups are running there with a synthetic full on Sundays. I then change the VM group’s Storage Policy to Y with a new deduplication database. The chat says that a new full backup is not triggered automatically—instead, incremental backups continue on the new storage.

“The practical consequences for VM groups (virtualization, Index V2)—such as no automatic full, and the inability to restore from incrementals after a policy change—are documented mainly in Knowledge Base articles (KB62892, KB62688) and action_items.”

However, those incrementals cannot be restored because the new database does not have a physical (true) full backup, and a synthetic full also cannot be created because there is no full.

So why isn’t there any warning or information when changing the Storage Policy or Plan that, in the case of a VM group, a manual full backup must be triggered?

+12

Sureshkumar S
Vaulter
Forum|Forum|7 days ago
June 15, 2026

Hi @Zawro ,

Good day!

Change in Storage Policy subclient association. Retain the last full backup on the old Storage Policy until a new full backup job runs on the new Storage Policy.

Ref : https://documentation.commvault.com/v11/commcell-console/data_aging_troubleshooting.html#:~:text=Change%20in%20Storage,on%20the%20cycles.

I couldnt see the KB articles mentioned . Are you unable to restore or run backups now in your infra ?

Regards,

Sureshkumar S

Like

Z

+1

Zawro
Author
Apprentice
Forum|Forum|5 days ago
June 17, 2026

Commvault chat said this :

If you change the storage policy/plan for a VM group (with Indexing V2), the next backup will not be forced to full. Incremental backups will continue as scheduled, and the cycle will only complete with the next scheduled full backup under the new policy.

Here is KB, but is connnected to older version.

https://support.commvault.com/Article/Details/62892

So, how exactly does it work with the VM backup that uses Index2? Why is there a difference between Index and Index2? Does that mean that if I plan to use only synthetic fulls and incrementals, then after changing the plan to a new DDB, if I don’t manually force a full backup, incrementals will be created and won’t be restorable becasue they will not have base ( full)?