Skip to main content
Solved

CommCell environment upgrade with HSX Clusters

  • February 3, 2025
  • 1 reply
  • 48 views

Forum|alt.badge.img+4

Hello Team,

 

Hello,

I have good experience on Commvault environment upgrade 

but I want some advices about HSX environment where I a not very familiar

CommCell version is 11.34.47 End of life target version is latest 11.36

Current HSX Clusters info :

whichCommit.sh
Branch: QBD[v-5.0.8.2]

rpm
hedvig-common-5.0.8.2_3820_f13a4ee0db-1.el8.x86_64
hedvig-cluster-5.0.8.2_3820_f13a4ee0db-1.el8.x86_64

In a standard environment, I update :


1 - Commserve Linux PROD
2 - Commserve Linux DR
3 - Media agents one by one, and I connect to each media agent to perform the update locally not push
4 - Access nodes
5 - Index cache Servers
4 - update clients 

I thing for HSX environment it is the same order :


1 - Commserve Linux  PROD
2 - Commserve Linux  DR
3 - HSX Cluster 1 
3 - HSX Cluster 2
4 - Access nodes
5 - Index cache Servers
4 - update clients 

My question is about HSX Clusters update. I am confused about OS upgrade, CVFS update, which order, service disruption during update, anyone can clarify please ?

Thanks for the help !
 

Best answer by R Anwar

Hi ​@BloopaAgain 

CvFS upgrade is done first and then OS RPM’s. However, you are already on latest CvFS version.
I would suggest to plan for migration https://documentation.commvault.com/v11/expert/migrating_hyperscale_x_version_on_existing_nodes.html

Regards,

View original
Did this answer your question?

1 reply

R Anwar
Vaulter
Forum|alt.badge.img+10
  • Vaulter
  • 115 replies
  • Answer
  • February 3, 2025

Hi ​@BloopaAgain 

CvFS upgrade is done first and then OS RPM’s. However, you are already on latest CvFS version.
I would suggest to plan for migration https://documentation.commvault.com/v11/expert/migrating_hyperscale_x_version_on_existing_nodes.html

Regards,


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings