Skip to main content

Approvals to apply hotfixes

  • November 12, 2025
  • 1 reply
  • 42 views

Forum|alt.badge.img+2

Just curious.  

What is the policy where you work when it comes to applying hotfixes? 

Do you treat hotfixes differently than release version upgrades?

I’m asking because my predecessors would apply hotfixes (if they addressed a specific issue) without really telling anyone other than maybe an immediate supervisor and an email to the engineering team (and maybe the NOC I’m not sure on that one).  They'd take a DR backup, SNAP the Commserver VM and let it fly and roll it back if there was a problem.

I’m more of a formal process kinda guy.  I assume most of you will tell me, “what’s the problem?  Just follow a formal process.”, but I there will be people in my organization that will push back because of the successes of the past.  I lack the real experiences that come with issues related to applying hotfixes (if any).  

Anyone have any experiences they can share?

How do you folks treat hotfixes?  

1 reply

Jos Meijer
Commvault Certified Expert
Forum|alt.badge.img+17
  • Commvault Certified Expert
  • November 12, 2025

I always follow the agreed upon change process.

For regular Maintenance Release installations we use a monthly patch window in which we patch Commvault, SQL and the OS. Everyone in our team can perform this task and it is defined in a recurring task of our ticket system.

As where a Feature Release is being installed, this takes some more effort.
I first validate if there are blocking issues by installing the new version and check all information regarding patches and new functionality. I keep track of information regarding these topics in a form, which I finally approve or decline for deployment and share with my colleagues.
A follow up is required by creating a change in our ticket system, which included a plan of action and a roll back scenario. We plan a maintenance window and install it during that window. If all is succesfull we continue operation, if not then we roll back.