Skip to main content
commvault.com commvault.com
Solved

HyperScale 1.5 Reference Architecture Upgrade

  • February 28, 2022
  • 3 replies
  • 166 views
M
Byte
Forum|alt.badge.img+7

Hi All,

We are running the HyperScale 1.5 Reference Architecture with RHEL on top of HP Apollo 4200 Gen9 servers. Now we planning to upgrade the OS to 7.9 through CV FR upgrade.

 

I have few quries and would like to hear from people who did the upgrade already. 

 

  1. As per CV, the upgrade takes around 60-90 min. What would be expected duration per node in real world.
  2. Is there any firmware pre-request required for this upgrade?
  3. Does anyone reverted the change successfully ? If yes, how long it takes per node
  4. Do we have any check point to validate the upgradation once completed for first node? instaed waiting till 6th Node upgrade. 

 

Thanks in Advance 

Mani 

Best answer by R Anwar

Hi @Manikandn 

As per CV, the upgrade takes around 60-90 min. What would be expected duration per node in real world.
30-40 mins

 

Is there any firmware pre-request required for this upgrade?
No

 

Does anyone reverted the change successfully ? If yes, how long it takes per node
Revert hasn't been required for any upgrade. First a transaction check is run on the rpm's that will be upgraded. If we find any issues, we don't proceed with upgrade until it's fix. Once transaction check is done, there are very minimal chance of upgrade failing mid-way.

 

Do we have any check point to validate the upgradation once completed for first node? instaed waiting till 6th Node upgrade.
For overall status, check the log /var/log/commvault/Log_Files/cvupgradeos.log on the node.

Detailed progress of yum update can be monitored in yum.log and yum.err.log available in <commvault_logs>/hsupgradedbg folder.

View original
Did this answer your question?
If you have a question or comment, please create a topic

3 replies

R Anwar
Vaulter
Forum|alt.badge.img+10
  • R AnwarVaulter
  • Vaulter
  • 114 replies
  • Answer
  • February 28, 2022

Hi @Manikandn 

As per CV, the upgrade takes around 60-90 min. What would be expected duration per node in real world.
30-40 mins

 

Is there any firmware pre-request required for this upgrade?
No

 

Does anyone reverted the change successfully ? If yes, how long it takes per node
Revert hasn't been required for any upgrade. First a transaction check is run on the rpm's that will be upgraded. If we find any issues, we don't proceed with upgrade until it's fix. Once transaction check is done, there are very minimal chance of upgrade failing mid-way.

 

Do we have any check point to validate the upgradation once completed for first node? instaed waiting till 6th Node upgrade.
For overall status, check the log /var/log/commvault/Log_Files/cvupgradeos.log on the node.

Detailed progress of yum update can be monitored in yum.log and yum.err.log available in <commvault_logs>/hsupgradedbg folder.

MichaelCapon
1 person likes this
  • MichaelCapon
    MichaelCapon
M
Byte
Forum|alt.badge.img+7
  • Manikandn
  • Author
  • Byte
  • 35 replies
  • February 28, 2022

Hi Anwar,

Thabks for your response. 

Can we run the transaction check well in advance seperately, to validate my environment?

 

Mani

 

R Anwar
Vaulter
Forum|alt.badge.img+10
  • R AnwarVaulter
  • Vaulter
  • 114 replies
  • February 28, 2022

Hi @Manikandn 

No, that’s ran before the node is upgraded.

M
1 person likes this
  • M
    Manikandn

Most helpful members this week

Terms & ConditionsCookie settings

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