Software Upgrades and Updates

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

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.

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.   SQL Server 2022 Standard Edition: When I install SQL Server 2022 Standard Edition, everything appears to complete successfully, but afterwards I am unable to upgrade Commvault to in any way.     Q1: Can Commvault version 11.40.26 run reliably with SQL Server 2022 Express Edition without any limitations or known issues? Additionally, are there any specific prerequisites or considerations for using SQL Server 2022 Standard Edition with Commvau

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.2196  7     12/10 14:17:53 ### ### ### - Err

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 is physically present in my source package (in the ...\ThirdParty\MSSQL\SQL_Standard_Edition directory). My CommServe is a "dark site" and has no internet connectivity.  Problem 2: Software Cache Corruption (The Root Cause) I suspect the validation is faili

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 physically present in my source package (in the ...\ThirdParty\MSSQL\SQL_Standard_Edition directory). My CommServe is a "dark site" and has no internet connectivity.  Problem 2: Software Cache Corruption (The Root Cause) I suspect the validation is failing b

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: Why the VMware logs consumed so much disk space ?Why the legacy index (v1) size increased recent

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)? 

Hi Team, We got one MS SQL Management studio(ODBC) Vulnerability on Commserve. Plugin Output:Path : C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Mashup\ODBC Drivers\Simba Spark ODBC Driver\LibCurl32.DllA\libcurl.dllInstalled version : 7.66.0.0Fixed version : 8.9.1As per commvault case 250807-187(this case is closed),This is not a SQL core vulnerability but a SSMS vulnerability.You can either ignore it or upgrade your SSMS and ODBC drives to remediate that.Commvault is not affected by this vulnerability. We are upgrading from 11.32 to 11.36 for production before that we did upgrade of test commserve to 11.36. .I see the SQL version there is also upgraded from sql 2019 to sql2022.SS Management studio is still 18.x.If I upgrade SSMS to 20.x(as per Support advise) will there be any impact on Commserve operations.I am reaching here since SQL server is used by Commvault stack and want to know if it works for SSMS 20.x also.Do I need to uninstall SSMS 18.x firs

In the List of Updates for the various Maintenance Release versions, there is now a section at the top of the site there is a new table section showing Security Updates. For example, for Feature Release 32 the latest Maintenance Release is 11.32.106 and this site shows the updates:https://documentation.commvault.com/2024e/essential/files/service_pack/updates/11_32_106.htmWhich shows this new table with three new security updates:Security UpdatesIssue Hotfix Made changes to use v7 encryption instead of v3 encryption. 12324 PSIRT fixes for REST API Qcommand and QAPI login. 12323 Restricted public user access to APIs. 12321  But what is confusing is whether these three Security Updates are only contained in release 11.32.106 or are they contained in any earlier maintenance releases? For example, the updates for 11.32.102 contains the same three security updates:https://documentation.commvault.com/2024e/essential/files/service_pack/updates/11_32_102.htm While

Hello Team,Can we enable archive_mode=always for our current environment (which is on 11.32.96) to ensure PITR between log backups and failover? Also, below KB article confirms that starting SP34 onwards the backed up logs will be cleaned up from all the participating clients. Does that mean it is still missing in SP32? Can it be backported? Restore to a time between log only backup and failover may not restore the records inserted after log backupThank you for your time. Kamal

After I upgraded CommCell from 11.28 to 11.32, I encountered this error. I have checked and confirmed that the account for accessing vCenter is still working (I can see the VMs in vCenter when I try to create a new subclient). However, the new subclient I created for testing also failed with the same error.

Does anyone know if Commvault is going to include the ability to backup Jira and Confluence (Atlassian) any time soon?

It looks like the version on libcurl.dll in the base commvault path needs to be upgraded in general:/opt/commvault/commvault/Base64/VMware/vddk/VDDK602/lib64/libcurl.Has anyone done this yet? Or will an upgrade of CV resolve the issue?

We see that the Group Policy Object (GPO) backup feature is enabled by default on Active Directory clients. We would appreciate an explanation as to why this decision was made, particularly given that the feature appears to require an additional license for full functionality.The automatic activation of this feature has led to complications:Some environments are now reporting backup jobs as “Completed with errors” due to attempts to back up GPOs without meeting the necessary prerequisites. In cases where the customer does not wish to back up GPOs, there is no straightforward option to disable this functionality. Instead, we need to add an “Additional Setting” in the Properties. If the customer does wish to use GPO backup, they must ensure that the service account has the appropriate permissions, modify registry settings to support long paths, or create specific folders. Should the customer later require a GPO restore, it appears that an additional license is necessary. This requirement