Commvault Upgrade Rollback Scenarios – Is It Ever Possible?

Possible?  If you have the DR backup and 11.36 media, maybe -- but I would not recommend going that route.  (Note: You do lose any successful backups made before you revert.)  It’s best to open a Critical TR and work through the issue so can move forward.  Let’s say you were to revert back to 11.36.  How do you confirm the issue gets resolved?  What if it’s environmental specific and Commvault cannot confirm or resolve the issue without you reproducing?

My recommendation is to stand up a lab CommServe where you can apply updates and verify any mission critical workloads.

Thanks,
Scott
 

I recently had to do this in my long running lab after some issues in an upgrade.  I uninstalled the upgraded version from my CommServe, and reinstalled with the old version.  I then did a CSREcoveryAssistant restore of the pre-upgrade CSDB which brought the CommServe back to good.  I then logged in remotely to each MA, uninstalled the current version and reinstalled the pre-upgrade version.  I had no issues with all coming back online properly.  That being said, I would recommend staying with the current version and letting Support (and Dev if needed) work out the issue.  My environment is a non production lab, somewhat basic, very little to go wrong.

In our case involving Oracle-to-OCI environments, I can confirm that reverting the client level (from 11.40 back to 11.36) resolved our issue!

To do this, we had to uninstall the 11.40 agent and perform a clean install of 11.36. So, a rollback at the client level looks to be definitely a possible and effective for bypassing some version-specific bugs.