Skip to main content
Question

Upgrade from 11.32 to 11.40 blocked by legacy 11.24 clients — Best practice to retain backups?

  • Nov 17, 2026 8:48 PM UTC
  • 2 replies
  • 9 views

Forum|alt.badge.img

Hi everyone.

We are planning to upgrade our Commvault environment from v11.32 to v11.40.
 

However, we currently have several legacy clients running v11.24. These servers are no longer in production or reachable, but we still need to keep them registered in the CommCell to retain their historical backups and metadata.

 

Since v11.24 clients are unsupported on a v11.40 CommServe and will block the pre-upgrade checks:

 

Is there any built-in feature or parameter during the upgrade wizard to bypass or ignore inactive v11.24 clients?

If we simply Deconfigure these v11.24 clients, will that completely clear the v11.40 pre-upgrade compatibility blocker while keeping all their historical backup data and metadata intact for future restores?

Are there any specific caveats or extra steps we should take (besides a full DR Backup) before running the upgrade with deconfigured v11.24 clients in the CommCell DB?

 

Any advice or confirmation from those who have gone through a similar upgrade path would be greatly appreciated!

2 replies

Forum|alt.badge.img+17
  • Vaulter
  • Nov 18, 2026 1:11 AM UTC

Hi ​@Acceso al wasabi con permisos ,

We can run a SimUpdatePackageStatus script to remove the package information from the CSDB. This operation will remove only the SP24 package details; the jobs will remain intact in both the storage and the CommServe database.

Based on our internal testing, file system restores work as expected after running the script. However, we have not yet validated the behaviour for other agent types.

If the Client count is high I would request to log support case to review the Database and share the bulk clean up script.


Forum|alt.badge.img

Hi Pradeep.

Thank you so much for your support. We'll evaluate what you mentioned, as in this case, the environment has a high number of customers.

Thank you very much for the feedback.