Upgrade from 11.32 to 11.40/11.42 what happens to index version?

Hi ​@ApK  

The clients which are using Indexing V1 will not be automatically upgraded to indexing V2 when you upgrade the Commvault version from 11.32 to 11.40/11.42. 

For Virtualization clients:

- Starting with 11.36, Indexing Version 1 for the Virtual Server Agent (VSA) will be end of life and will no longer be supported for new VSA features (new functionality will use VM‑centric indexing instead). 

https://documentation.commvault.com/11.40/software/deprecation_notice_for_indexing_v1_for_virtual_server_agent.html

- Refer to the below article for important considerations and the process to migrate the Virtualization workloads. 

https://documentation.commvault.com/11.40/commcell-console/migration_of_virtualization_clients_to_latest_version_of_indexing.html

For File system agents:

- Firstly, you can refer to the below article to check and confirm the agents that support migration from V1 to V2 indexing. 

Agents that support Indexing V2- https://documentation.commvault.com/2024e/commcell-console/agents_that_use_indexing_indexing_version_1_and_indexing_version_2.html
 

​​​​​​​-Post checking, please refer to the below article for further the prerequisites and procedure. . 

https://documentation.commvault.com/2023e/commcell-console/migration_of_clients_to_indexing_version_2.html

​​​​​​​Let us know if you have any queries. 

Hi ​@ApK  , 

This is a good point unfortunately the current feature release upgrade does not include automatic index upgrade for now so it needs to be performed manually for the mentioned DBs and fs agents these workloads will be supported after the upgrade however the main concern is with VSA as it is now deprecated.

The best practice is that after completing the upgrade and within the downtime window you should run the index upgrade workflow If you have additional time I would also recommend upgrading the other workloads as well.

If you face any issues during or after the upgrade please update us here and I will keep an eye on it.

Good luck

Thanks,
Mohammed Ramadan
Commvault PS Engineer
 

Hi Kalaivanan & Mohammed

Thanks for your replies. The issue here, is that I don’t have to much space on my platform, and I need to upgrade to 11.40/11.42 before I get more storage for the platform, so my concern was that it would upgrade the index during the upgrade of the software and by this consume more storage. 

Would there be any issues not upgrading the index and wait until I get more storage?

Thanks.

Hi ​@ApK  , 

The migration process itself does not duplicate backup data my friend It clones configuration and metadata not the actual backup data after the migration he first backup job on the new V2 client will be a full backup which will consume additional storage space most of time we schedule it at the same time of the weekly full by this we prevent the space issue .

you can wait until upgrade your storage but you will not have support for v1 indexing if something go wrong we dont know if you plan your migration as i mention above it will be fine .

Hi ​@ApK 
 

As Mohammed mentioned, there will be no additional storage consumption apart from the fact that the first backup after migration will be a full backup.

• For virtualization clients (e.g., vCenter Client), when you run the V1 to V2 workflow, a new vCenter client is created with Indexing Version V2.The first backup from this new V2 client will be a full backup, establishing a new baseline.

• Subsequent backups will then follow the configured schedule (incremental, synthetic full, etc.) based on this baseline.

The backup activity of the old vCenter client will be disabled, and backups will continue from the new V2 client. However, you will still retain the ability to browse and restore data from the old backup jobs associated with the previous vCenter client.

Since V1 indexing is deprecated for Virtualization clients, we suggest you to follow the steps that was shared earlier and migrate the V1 clients to V2 indexing.  

Regards,

Kalaivanan. 

!--endfragment>