Anyone upgrade from 11.32 to 11.40?

Just did one and no issues.

Patch cv and ma's with latest Maintenance.32 release and take a few dr backups.

Make sure AV scanning is disabled as this can give you issues while upgrading.

That’s great to hear. Appreciate the input. Was there any particular reason to go to the latest maint release first or just best practice recommendation?

We are planning the upgrade from FR36 to FR40 on our production environment. On our BETA setup we only ran into some minor issues who have been solved and an issue related to our setup. 

11.36 comes with a sql server upgrade along side the ordinary upgrade of the commserve.

sql server 2022 is the new requirement.

I got a reccomendation from our sql dba’s to not upgrade the sql server ( we ran on 2016)  and instead do a clean install on the new version. 

So when we upgraded from 11.32 to 11.36, we did a clean install of 11.36 (where sql 2022 also get a clean install)  and ran a dr recovery based on a dr backupset from 11.32.

Dear ​@atitagain,

Please can you provide the action plan you followed during the upgrade ?

Best Regards,

Ahmed

Just to close this thread off, we did the jump to 11.40.34. The upgrade completed ok. I would recommend not failing over if running a standby livesync setup. We had issues doing that and rolled out and had to start over just upgrading each side manually without failover. Post upgrade, we have had some issues crop up (communication pipe/tunnel failures for no apparent reason, issues with the software cache, odd version information upon upgrading client agents (some show 11.40.34 others show 11.40.6 especially on Linux servers using the same media kit). So yes the upgrade was successful but seems it still has kinks to work out 😔

We had upgraded from 11.36 to 11.40.38 last week.   Initially we had an issue with Command Center GUI not loading(java GUI still worked!).  Working with support, 24 hours later found an issue with Tomcat and SSL certificate issue.   IIS SSL cert was good, just Tomcat issue.

Second issue we had some Azure Storage accounts that started failing.  Turns out the Commvault Azure account does not have access to those storage accounts… but on 11.38 the backups were successful, so it claimed.   The 11.38 successful backups had zero bytes backed up, but the Storage account did have data in it.  Turns out these were part of Data Bricks as temp storage and do not need to be backed up.   If you are currently on 11.38 and backup Azure storage accounts, you may want to upgrade to 11.40 soon to ensure your accounts are all being backed up.

This past weekend we also ran into an issue where lots of our Backup Copies were all ‘waiting’ when there were plenty of streams available in the storage policies.   Suspended and resumed the jobs, and they started up again.   We are continuing to monitor this one.

Interesting. We also are seeing weird not enough streams issues on some of our Aux copy jobs. Haven’t figured that one out yet.

SCI85_BJC,
   Have you opened a ticket with support on this?   It may help if we let support know that there is more than one customer with stream issues after the upgrade.

Thank you

Not yet but it’s on my list

Support has found the issue.

a bug in an 11.40 CSDB stored procedure that was not properly rechecking for free available resources for Backup Copy jobs that were in a Waiting status

I am now waiting for the patch.

I recently upgraded my Commvault server and had no issues. Very straightforward 

Have done multiple….. Main issue I’ve seen is that sub client polices might no longer be honored.  Had a backend storage almost running full due to MS SQL .mdf files were now picked up by the Filesystem agent although filtered by a subclient policy..   Support is currently working on this:  Ticket 260302-355

/RubeckDK

I carried out the upgrade from 11.32.118 to 11.40.38 about a month ago, here is what we found…

The upgrade itself went pretty smooth, no errors so off to a good start….then the fun began.

Like some, we had some issues with communication pipe/tunnel failures for no apparent reason, we had to put in 1-way firewalls and/or DIPs to resolve, no big issue here.

We also had instances where SQL jobs would start and not progress and update time would not update. Suspending the jobs and resuming would kick the jobs into life and complete. We had to reboot all the Media Agents (they were all rebooted post upgrade) which seemed to clear this issue.

We were also backing up NetApp SVMs over NDMP, all these started to fail. due to the upgrade jump, REST is now used to communicate and send commands to initiate Snapshot and backup copy’s. We had to enable and configure REST roles at both the Cluster and SVM level and assign HTTP permissions and volume snapshot creation permission on the role.

For CIF backups, SnapDiff v2 and v3 needed to be setup as per FAQ:Frequently Asked Questions for the NetApp Storage Array

Hopefully this will help anyone else preparing for the upgrade and saves some pain points 😁

Rich

Update: Dev FormID=2465. Will be resolved in a MR and will be included in 11.40.44

/RubeckDK

Hi buddy,

It is generally recommended to be at the latest version of patch while performing a jump upgrade. We have also done the same from 11.32 to 11.40. We faced an workflow issue in 11.40 post upgrade. There is a workflow that keeps on requesting to delete the clients with no job run in last 7 days. Our situation was, we had couple of workloads which were scheduled to run monthly, so we faced this issue. For security, a third person authentication was enabled before deleting the client/subclient in our environment, so we were on the safer side.

Hope your upgrade goes good.

Best Regards.