The MSDP server maintenance
In a routine node maintenance such as upgrade, EEB installation, OS patching, and system restart we recommend that you intervene to reduce the impact on deduplication ratio or a job failure.
Use MSDP command-line of the MVG server or NetBackup web UI to set the node in the maintenance mode before the routine maintenance and reset afterwards. The MVG server does not move the client policy assignment from the node in maintenance to another node. The new backup jobs may fail temporarily if the node is not stable or functional during the maintenance.
Run the following MSDP commands on the MVG server:
cacontrol --mvg set-mvg-maintenance <msdp-server>
cacontrol --mvg unset-mvg-maintenance <msdp-server>
cacontrol --mvg get-mvg-maintenance
Example:
PATH=$PATH:/usr/openv/pdde/pdcr/bin cacontrol --mvg set-maintenance-mode vramvg037340.rsv.ven.veritas.com Updated virtual volumes: mvg-local cacontrol --mvg get-maintenance-mode MSDP servers in maintenance mode: vramvg037340.rsv.ven.veritas.com Virtual volumes which have the MSDP servers in maintenance mode: mvg-local cacontrol --mvg unset-maintenance-mode vramvg037340.rsv.ven.veritas.com Updated virtual volumes: mvg-local cacontrol --mvg get-maintenance-mode No MSDP servers found in 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".
Alternatively, you can deactivate the corresponding backup policies temporally during the node maintenance.
Alternatively, if the maintenance cycle is short, you can use or tune out the MVG rebalance freezing time on the MVG server, so that the MVG server does not move the client policy assignment out if the node can be back to stable within the MVG rebalance freezing time. By default, the value is 0.5 hour. It can be tuned by MVG Controller API:
curl -K /uss/config/certificates/controller/.curl_config https://localhost:10100/v1/agent/mvg/loadbalance/config -d '{"asmt_rb_freezing_timeout": 3600 }' -X PATCHCheck the tuning parameters:
curl -K /uss/config/certificates/controller/.curl_config https://localhost:10100/v1/agent/mvg/loadbalance/config