Skip to main content
commvault.com commvault.com
Question

Upgrade from VSA v1 to v2 - what happens to backupSet structure?

  • June 3, 2026
  • 3 replies
  • 25 views
D
Apprentice
Forum|alt.badge.img+2

Hi,

I have some questions about the workflow for upgrading: VSA V1 to V2 Migration Workflow.

In VMWare we have not only the defaultbackupSet but also many other backupSets where we sort different subclients.

As far as I’ve understood, the backupSets are being considered legacy, and VMGroup can only be created it in the default backupset.

What will happen to all of the subclients in the other backupsets under the client if I would run this workflow?

Would they all go into the defaultBackupSet or would the new client maintain the structure of the backupSets and now VMGroups, even though they are not the defaultBackupSet.

 

Does anyone have any experience with this?

 

Kind regards,

Daniel

3 replies

Paul G
Explorer
Forum|alt.badge.img+2
  • Paul GExplorer
  • Explorer
  • June 4, 2026

Hi ​@danbj,

I don't recall having a situation where I had a environment where multiple backup sets were used for the virtualisation client when running the migration workflow.

I just checked the documentation and I see the following lin in the workflow process documentation.

Clones all backup sets and subclients under the VSA Indexing Version 1 client and migrates them to the latest version of indexing.

Migration of Virtualization Clients to the Latest Version of Indexing

This would mean all your backup sets will be recreated under the new v2 client.

 

Could you tell me why you use multiple backup sets? They may not work correctly or interfere with restores under the new v2 model. If so, you might be better of by creating the new client and subclients yourself.

Kind regards,

Paul

 

K
Vaulter
Forum|alt.badge.img+2
  • KalaivananVaulter
  • Vaulter
  • June 5, 2026

Hi ​@danbj 

 

After V1 to V2 migration, only the defaultBackupSet exists on the new V2 client, and all VM Groups (converted from subclients) are found there. The legacy backup sets remain on the old (now suffixed) client for historical/restore purposes but are not used for new backups.

  • Legacy V1 backup sets and subclients remain on the original (now suffixed with _V1) client for historical reference and access to old backup jobs.
  • The new V2 client (created by the workflow) will have only a single defaultBackupSet. All migrated subclients from all backup sets are now represented as VM Groups under this defaultBackupSet.
  • No additional backup sets are created in the V2 client. The structure is flattened: all VM Groups reside under the single defaultBackupSet.The original backup sets (other than defaultBackupSet) are not migrated or recreated in the V2 client.
  • Old backup sets and subclients on the original V1 client are typically renamed with a _V1 suffix and can be used for restores of legacy data, but are not active for new backups.

 

Regards,

Kalaivanan. 

Paul G
Explorer
Forum|alt.badge.img+2
  • Paul GExplorer
  • Explorer
  • June 5, 2026

Hi ​@Kalaivanan,

Thank you for the clarification. This means this line in the documentation is incorrect or can be interpreted incorrectly?

Clones all backup sets and subclients under the VSA Indexing Version 1 client and migrates them to the latest version of indexing.

Migration of Virtualization Clients to the Latest Version of Indexing

Good to know that the backup sets will be merged but what settings will be kept? How does the workflow decide which backup set filters will retained?

Kind regards,

Paul Germanus

Readiverse Academy Certifications

description of image
Terms & ConditionsAccessibility statement