Software Upgrades and Updates

 Good day to you All, I am encounter the Maintenance release upgrade failed on only single client rest of the linux and win was success. Upon check the autoinstaller.log found below error. 104656 1ef58 10/10 16:33:54 113928 ProcessNewCacheRequest Cache operation type in request is [GetCacheInfoNew]104656 1ef58 10/10 16:33:54 113928 ProcessNewGetCacheInfoReq() - Getting cache information for client [host*8400] from [C:\Program Files\Commvault\ContentStore\CVMedia\11.0.0\Windows] for the requested release and OS104656 1ef58 10/10 16:33:55 113928 [CalculateCheckSumForCacheFiles] Computing file-checksum information for release [11.0.0] os [WinX64] cache directory [C:\Program Files\Commvault\ContentStore\\CVMedia\11.0.0\Windows]104656 1ef58 10/10 16:33:55 113928 [CalculateFileCheckSumForOS] Calculating checksum information for V11 binary files from directory [C:\Program Files\Commvault\ContentStore\\CVMedia\11.0.0\Windows]104656 1ef58 10/10 16:33:57 113928 [CalculateFileCksumForDir] Success

Hi CV Forum. Hopefully someone can advise here. I couldn’t find these exact questions in the forum. I am going to upgrade from 11.20.172 to 11.28.(latest) and just have a few things I can’t seem to find in the masses of documentation.Great walkthrough here by Jos on the upgrade procedure to 11.26 and going to be pretty much the same procedure. We are running SQL 2016 and just wondering if anyone has come across the need to update.. I doubt it but couldn’t find it in the reams of documentation. Upgrade from version 11.20 to 11.26 (Latest release) | Community (commvault.com) Also, we are having to maintain some older EOL OS which require v9 and v10 client versions. Has anyone upgraded to 11.28.x and can they confirm they still work?  Thanks for any advice. Alan

Hello everyone! I have commcell version 11.23.42. What version can I upgrade to so as not to re-issue the license?

failed main upgrade phase commvault while performing upgrade 

Hi,We are currently running Commvault in a VM 11.20.168 on Windows Server 2019, and also using a FREL.As the title states, I would like to upgrade the Commvault release from 11.20.168 to the latest version 11.32, and also the Windows Server version. We have 4 instances that I maintain, and it is a closed network (I have to download the update files and transfer them over).This VM was previously running Windows Server 2012R2 but I upgraded our instances to Windows 2019. I could just do an in place upgrade again to 2022, but maybe it is best to make a new VMs. Please share your thoughts and recommendations.

Hello everyone, We are running Commvault 11.28.72.Now we want to upgrade to 2023E. I'm trying to download the software via Commcell Console:Tools tab, Add/Remove Software > Download SoftwareThe download starts and then changes to pending with the following error: If I try to download 11.30 the same thing happens.When I upgraded the commcell console from 11.24 to 11.28 it al worked great.Anyone an idea of what to do?

Hello, Yesterday I upgraded the Commserve serve from FR28 to FR32. Unfortunately replication process for Commserve DB between the server is not working properly after upgrade. The issue which appeared is: Query Result [Microsoft.SqlServer.Management.Common.ExecutionFailureException:The database was backed up on a server running version 15.00.4280. That version is incompatible with this server, which is running version 13.00.5216. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server. RESTORE LOG is terminated. Please let me know me probability  solution. Regards, Michal

I’m looking to upgrade :-)Upgrade 11.22.66 to 2022E or 2023E any gotchas, to be focused on please. Is it a direct upgrade option? thanks 

Hello everyone,I'm planning to upgrade my Windows Server 2012 to Windows Server 2016, which currently has Commvault 11.24 installed. It also hosts SQL Server 2012. Could anyone provide guidance on the compatibility of Commvault with Windows Server 2016 and whether it's necessary to update SQL Server before the upgrade? I appreciate any advice or experiences you can share.Thank you.

Hello,  We plan to perform a CommServe hardware refresh from Windows Server 2012 to Windows Server 2019. Commserve is on Feature Release 28, and the SQL server version is 2012. What is the upgrade path for the Commserve with SQL running in 2012? Do we need to first upgrade the SQL to 2014/2016 and then perform the Hardware refresh? Or is it possible to perform a hardware refresh without upgrading the SQL? The documentation doesn’t mention about SQL upgrade path.  CommServe Upgrade with Hardware Refresh: Overview (commvault.com)

Hello fellow Commvault users,I have a question regarding the upgrade of Commvault from v10 to v11 while also migrating from Windows Server 2012 to Windows Server 2016. I am seeking to determine the best course of action for this process.Option 1:Start by formatting the server and upgrading it to Windows Server 2016. Perform a Disaster Recovery to restore Commvault v10 after the OS upgrade. Finally, proceed with the upgrade to Commvault v11.Option 2:First, update Commvault v10 to v11 while the server is still running on Windows Server 2012. Once the Commvault upgrade is complete, format the server and update it to Windows Server 2016. After the OS migration, recover Commvault using the Disaster Recovery process.I would greatly appreciate your input and feedback on which option you believe is the most efficient and reliable for upgrading Commvault and migrating the OS. If any of you have faced a similar situation or have alternative suggestions, please share your thoughts.Thank you all i

need to know the step or provide me the documentation here. also provide me the latest release note  N-1 version

Hello there,We’ve tried to upgrade our commserv from 11.24 to 11.28, but it failed ob the database upgradewith this error :Cannot create more than one clustered index on table 'JMJobOptions'. Drop the existing clustered index 'JMJobOptions_jobId_commCellId_attributeId_idx' before creating anotherour commserv is a Microsoft Server 2022, SQL version 2019.Does anybody has already met with a similar issue?