Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Deduplication Guide
  3. MSDP volume group (MVG)
  4. About the node failure management
NetBackup™ Deduplication Guide

About the node failure management

The following table lists the node failure scenarios and how they can be managed.

Table:

Node failure

Description

Planned node failure

In a routine node maintenance, we recommend that you reduce the impact on deduplication ratio or a job failure.

Set the node in a maintenance mode on an MVG server. The client policy assignments on the node are not automatically changed if the node is in maintenance mode.

Run the following MSDP command to change them manually:

cacontrol --mvg set-maintenance-mode <msdp-server>
cacontrol --mvg unset-maintenance-mode <msdp-server>
cacontrol --mvg get-maintenance-mode

On the NetBackup web UI, go to the Disk Pool webpage of an MVG volume, select and edit a disk volume of an MVG volume, then switch the mode between "Maintenance" and "Normal".

Unplanned node failure

The MVG server uses a rebalance freezing timeout to control when it reassigns disk volumes. If the default disk volume becomes unavailable, the MVG server will not select another volume for the same client-policy until the default volume remains unavailable beyond the configured timeout during the next backup.

This setting is configurable using the tuning parameter asmt_rb_freezing_timeout through the MVG tuning API or the command line.

See Specifications and default values of the MVG tuning parameters.

See CLI for tuning MVG parameters.

The node is operational again after the failure

If a node stays down for long, the client policy assignments are moved out when NetBackup run backup jobs with the backup policies.

When the node is back, most of the original client policy combinations are moved back to keep the system balanced again.

The node is full

If a disk volume is full, a client policy is moved to another node. It is not moved back unless the new node becomes inactive or full and the original node has space available again.

The setting can be disabled using the tuning parameter asmt_rb_freezing_on_disk_full through the MVG tuning API or the command line.

See Specifications and default values of the MVG tuning parameters.

See CLI for tuning MVG parameters.

Feedback

Was this page helpful?
Previous

Limitations of the MSDP volume group

Next

MSDP volume group best practices

Feedback

Was this page helpful?