Software Upgrades and Updates

Hi team,We are building up a new infra in Azure to be responsible to back up all workloads running in Azure, which are currently managed by a Commcell running on-prem.Having that said, we want to migrate ONLY the Azure workloads from this Commcell to the new one, running in Azure. I know that Commcell migration is not supported for Azure, even on version 11.40 (we are on 11.36 latest MR): CommCell Migration - SupportReconfiguring the pseudo-clients and enabling again VSA backups, it's easy and has been done already.The problem is that there are VMs in Azure runnings DBs, where we do a combination of Filesystem and DB agents backups.What would be the quickest way to move the agents from one Commcell to another to avoid the manual work, as there are several clients? Any way that I can user Export/

Hi Experts, I have an old setup running in Commvault version 11.16 and I am planning to upgrade to 11.32. Could you please help me to get the details how can I achive without interrupt the services ?

Hi,Since I upgraded the CS to 11.36.83 I wasn’t able to connect with MFA option to web console and JAVA.Before the upgrade it works fine and nothing has been changed with the users and groups.I’m also tried to upgrade to 11.36.87 but still no working, when I’m canceling the MFA option we can login with no problem. Any ideas?Thanks 

Hi all,I need to move the CS DB to another location as I didn't follow the best practices for the LV size and mixed it with other stuff on the same volume. For Windows, I could solve everything with my own admin account and MSSMS.However, I need to do this now on the Linux environment and I'm afraid of changing the sa password to allow me connecting to the system remotely and use MSSMS GUI.What happens if I change the sa account password? Can later I force an operation via Commcell console, so Commvault will ask me for the new one?For example, on Linux I can easily do this:stop sql server service/opt/mssql/bin/mssql-conf set-sa-passwordstart sql server serviceUntil here, fine. What about ensuring the Commvault knows the new pwd?The reason is that to perform the change of CS DB location I need to detatch the databases, move the mdf files and attach them again.Is there any other way to do it on Linux environmen

HelloWe just applied the latest maintenance patch to our 11.32. Commvault environment a few days ago to bring us to 11.32.128  (from 11.32.125) and I noticed this morning scans showed a log4j vulnerability. Plugin Output:   Path              : C:\Program Files\Commvault\ContentStore\CVCIEngine\CvPreviewHome\webapps\CvContentPreviewGenApp\WEB-INF\lib\log4j-core-2.17.1.jar  Installed version : 2.17.1  Fixed version     : 2.25.3  Path              : C:\Program Files\Commvault\ContentStore\MessageQueue\lib\optional\log4j-core-2.24.3.jar  Installed version : 2.24.3  Fixed version     : 2.25.3 Is there a fix or patch that Commvault will release to address this.  Maybe in the next months maintenance release?   Any input would be appreciated. ThanksBC

We recently had a scare when Commvault upgraded us to a new feature that we “Thought” our Media Agent couldn’t handle.  Thankfully we were wrong but we want to disable auto updates.  The ticket I had open they said to do the below.  I can not find this option at all.  When I do searches it talks about disabling it in the schedules but I am not seeing the updates in the commcell schedule either.  Not sure what I am doing wrong.Steps:Open the CommCell Console. Navigate to: Control Panel > Additional Settings. Add a new setting: Name:DisableAutomaticPushInstall Category/Path:CommServDB.GxGlobalParam Type: Integer Value:1

we are planning for upgrading cs and SQL version without the hardware refresh, Please help here with the known issues and the necessary steps for upgradation

Cannot see SAP Hana part of the list for database agent download from cloud.commvault.com 

Hi all,we upgraded to the latest release 11.36.33 (from 11.32) and, according to this documentation page (https://kb.commvault.com/article/54270) we should have MongoDB 7.0...but if I check the MongoDB instance that is running now on the commserve, I got release number 6.0.14.Do you have any idea why there is this mismatch ?RegardsGianluca

Team,One of my customer is on SP20, post discussions we have finally convinced them to move on to the latest SP (as per documentation, the latest LTS is SP40), is it advisable to move directly from SP20 to SP40? what will be impact if this is done? Or do we have to upgrade to SP32? If yes, SP32 is also announced EOL.

We are looking to upgrade our environment from 11.32 to 11.40 LTS. Was wondering if anyone out there has been through an upgrade to 11.40 and how it went. Thanks for the input.

Recently we did a upgrade of Commvault to 11.36 from 11.32. During the update, the update failed on our index server because the disk was full. We freed up some space and was able to complete the update. After the update, everything backs up fine except exchange which is our index server. I have gotten nowhere with support. Is there anything I can look for on the index server or Commvault itself? I am running out of ideas. 

I am currently running Commvault version 11.36.80, which manages a VMware vSphere cluster (version 8.0.3) through vCenter (version 8.0.3).I would like to integrate a Proxmox cluster (version 9.0.1) into this environment.When attempting to upgrade Commvault to version 11.40.26, I receive a prompt indicating that the SQL Server must be upgraded first.Below are the steps performed for upgrade SQL Server: SQL Server 2022 Express Edition: When I install SQL Server 2022 Express Edition, I am able to successfully upgrade Commvault to version 11.40.26.

Hi,The below error is generated in the post upgrade phase of the a CommServe upgrade from 11.36.68 to 11.40.26.Install.log2196  7     12/10 14:17:52 ### ### ### - Performing  PostUpgrade tasks for the databases...2196  7     12/10 14:17:52 ### ### ### - Please check [E:\Program Files\Commvault\ContentStore\Log Files\DatabaseUpgrade.log] for granular details2196  7     12/10 14:17:53 ### ### ### - Warning: ["E:\Program Files\Commvault\ContentStore\Base\CvDBUpgradeWrapper.exe" -install -phasename PostUpgrade -clientname 'CommServe' -instance Instance001 -productname ALL -ProductVersion 11.40.26 -oemId 1 -DBUpgradeDir "E:\Program Files\Commvault\ContentStore\Base\DBUpgrade" -DBBackupDir "E:\Program Files\Commvault\ContentStore\iDataAgent\JobResults" -log "E:\Program Files\Commvault\ContentStore\Log Files" -DoNotBackupDB  -resume ] exit code 2 2196  7     12/10 14:17:53 ### ### ### - Error: Failed to complete  PostUpgrade tasks for the databases.

I currently have an environment running Commvault version 11.24, and I am planning to upgrade to version 11.32. The CommServe database is hosted on Microsoft SQL Server 2012.Before proceeding, I need to confirm the following: Is SQL Server 2012 still supported in Commvault 11.32? I would appreciate any guidance or experiences from similar scenarios.

HiI am trying to install an FS agent on Centos 5.4.With an agent V11SP28: I get an error saying ‘could not find any installer to use’.With a V11SP21 agent: the installation gets stuck: Using update installer Bits/linux-x86/LooseUpdates/CU24/linux-glibc2.3/installer/newinstall.gz:I don't know if these two agent versions are compatible with Linux 5. Thanks

Hello Team, the TAR downloader is fine, but i need to use it using AWS Packer to create Golden imageis there a way to have a curl or call api directly to download full package using CLI avoid to install things and/or have a gui a download a package on linux ?

Hello, I am attempting to perform an in-place upgrade of my CommServe in a dark site environment, which includes upgrading the SQL.I am facing a critical problem, and standard procedures have failed. Problem 1: Pre-Upgrade Validation Failure When I run the Setup.exe from my downloaded installation package, the Pre-Upgrade Validation check fails with this error:Automatic upgrade of the existing SQL Server instance is allowed but SQL Standard media is not available in the source media.Context: I downloaded the full installation package from the Commvault Cloud Services portal onto an internet-facing machine. I ensured to include all Third-Party Software (Microsoft SQL Server Standard). I have manually verified that the SQL media

Hello,I am attempting to perform an in-place upgrade of my CommServe in a dark site environment, which includes upgrading the SQL.I am facing a critical loop, and standard procedures have failed. Problem 1: Pre-Upgrade Validation Failure When I run the Setup.exe from my downloaded installation package, the Pre-Upgrade Validation check fails with this error:Automatic upgrade of the existing SQL Server instance is allowed but SQL Standard media is not available in the source media.Context: I downloaded the full installation package from the Commvault Cloud Services portal onto an internet-facing machine. I ensured to include all Third-Party Software (Microsoft SQL Server Standard). I have manually verified that the SQL media is physical

Just throwing this out there in case anyone else is ever searching for CVE-2025-48989 and Commvault as keywords. I contacted Commvault Support to confirm that the instance of Tomcat in Commvault is not affected. Here is the response. The development has provided the following information:- Regarding CVE-2025-48989: Commvault does not enable HTTP/2 on our Tomcat instance, so this is not applicable which means that commvault servers are not affected with this vulnerability.

Hi all,I received an alert about the index cache of a media agent that will be full in less than 30 days, this for the first time with this server.This media agent is only used to backup VMware VMs, around 220 machines per night (2 storage policies).A Treesize report shows clearly the origin of this phenomena (1.png):More details indicates that there are huge VMware logs (2.png):Yesterday, disk was almost filled up to 90 % (3.png), I ran the load balance process from the “ Index server load” report, it freed 20 GB.The “Index cache space usage details” report for this MA, on a monthly basis this time (4.png) shows that before May, 2025, the legacy index (v1) size was neglectable.As far as I know, the only modifications on the infrastructure over the lasts months are deployment of updates, from 11.32.76 to 96, then 112.I had a look at Index log files on MA, nothing relevant. My questions are: 

Are Exchange server SE supported from CV Agent version  2023E ( 11.32 )

Hello,The customer would like to change the HCL Domino (AIX 7.2) production operating system to Windows Server 2022.I see in the documentation that there is support up to a maximum of WS2019.I would like to enquire if perhaps the manufacturer has not updated the documentation or if indeed WS2022 is not supported.https://documentation.commvault.com/2022e/expert/notes_database_system_requirements.html Regards,Michał 

Hi, We’ve upgrade from v 11.36.49 to 11.36.68.The upgrade appeared to complete successfully on the Commserve, however I noticed the MongoDB service was failing to start and kept retrying.From the logs I can see the error “featurecompatibilityversion 4.2 expected 6.0 or 6.3 or 7.0”. On further investigation I can see the mongod.exe has been upgraded to v7 however the featurecompatibility has been left as 4.2.  Replacing the .exe with a version 4.2 has resolved the issue, services start and all ok.My questions are, I’ve seen the kb about manually upgrading minor versions, but how is it possible to upgrade to v7? CV doesn’t support manually upgrading major version.Will running v4.2 cause any problems, it appears to have been fine for the last few days since I’ve done this.Will this resolve in the next upgrade?  Is this a known issue for 11.36.68?

Hi, We are currently running Commvault 11.32.102 and we are affected by the following CVE's:CVE-2025-48988CVE-2024-54677CVE-2025-49124CVE-2025-46701CVE-2024-50379CVE-2024-56337CVE-2025-31651CVE-2025-49125CVE-2025-24813CVE-2025-53506CVE-2024-52318CVE-2025-52520CVE-2025-31650Support mentioned that the vulnerabilities does NOT affect Commvault.But this version of Tomcat (10.1.31.0) is still vulnerable and is solved in version 10.1.42 which requires 11.42 (which is not a LTS version). How to solve it in current LTS versions (11.32, 11.36 or 11.40)?