Skip to main content
commvault.com commvault.com
Solved

Workflow to put Hyperscale cluster media agents into maintenance mode

A
Bit
Forum|alt.badge.img+1

We have multiple Hyperscale \ ScaleProtect implementations some with six bricks in the cluster. It is very tedious to right click, check the box, say ok every time you need to do an OS upgrade (soon to be monthly) or some other maintenance that requires the cluster to be in maintenance mode. Does anyone have a script or a workflow they can share?

Best answer by Stuart Painter

Hi @Andrew Madsen 

Thanks for the question.

I’ve been checking documentation: 

Installing Operating System Updates on Existing Nodes  suggests to Put Media Agent into Maintenance Mode, but using the GUI.

 

There is a script to Set Media Agent Properties, one of which is marking MA offline/online:

  • To mark MediaAgent as offline for maintenance
    qoperation execscript -sn setMediaAgentProperty -si sample_ma -si 8 -si 1

 

  • To unmark MediaAgent as offline for maintenance
    qoperation execscript -sn setMediaAgentProperty -si sample_ma -si 8 -si 0

 

But from what I can see we don’t have a specific script or workflow to set HS cluster status.

Thanks,

Stuart

View original
Did this answer your question?

2 replies

S
Vaulter
Forum|alt.badge.img+15

Hi @Andrew Madsen 

Thanks for the question.

I’ve been checking documentation: 

Installing Operating System Updates on Existing Nodes  suggests to Put Media Agent into Maintenance Mode, but using the GUI.

 

There is a script to Set Media Agent Properties, one of which is marking MA offline/online:

  • To mark MediaAgent as offline for maintenance
    qoperation execscript -sn setMediaAgentProperty -si sample_ma -si 8 -si 1

 

  • To unmark MediaAgent as offline for maintenance
    qoperation execscript -sn setMediaAgentProperty -si sample_ma -si 8 -si 0

 

But from what I can see we don’t have a specific script or workflow to set HS cluster status.

Thanks,

Stuart

Customer Support
A
1 person likes this
  • A
    Andrew Madsen
A
Bit
Forum|alt.badge.img+1

As far as I can tell the entire cluster needs to be placed in maintenance mode one node at at time. This is why it is so tedious especially if you have six or twelve nodes in the cluster. Now to figure out a workflow.  

Reply


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