Search <book_title>...

Veritas NetBackup™ Appliance High Availability Reference Guide

Last Published: 2020-12-19

Product(s): Appliances (3.3.0.1)

Platform: NetBackup Appliance OS

Overview of NetBackup Appliance high availability
Deployment of a high availability configuration
Configuration and performance guidelines
1. Configuration requirements for features and options in NetBackup appliance high availability setups
2. Performance tuning for the failover scenarios
  1. Performance tuning for the node failure
  2. Performance tuning for the FC disconnection
Disaster recovery
1. Disaster recovery in a NetBackup 53xx high availability configuration
  1. Disaster recovery for one-node failure
  2. Disaster recovery for two-node failure
Appendix A. HA Deployment Checklist
1. Checklist for NetBackup Appliance high availability deployment
Index

Disaster recovery for two-node failure

If the two-node failure occurs in your high availability (HA) configuration, Veritas recommends that you recover the system and the data as follows:

Change the two-node failure disaster to the regular appliance disaster.
Note:
Numerous situations can cause fatal conditions and result in the need for disaster recovery. In a disaster recovery situation, it is critical to determine the cause of the disaster and recover as much data from the system as possible. Therefore, before you attempt to recover your HA configuration, contact Veritas Technical Support.
Recover the appliance.
Create the HA configuration again.

In the recovery procedures, use the following system settings as the example:

The host name of the master server: host-master
The original host name of the node that you used to set up the HA configuration: host-origin
The new host name of the node that you used to set up the HA configuration: host-setup
The host name of the node that you add as the partner node: host-partner

To change the two-node failure disaster to the regular appliance disaster

On the master server, log on to the administration console.
Check the status of the NetBackup objects as follows:
- Check the status of the media servers in your working system with the following command:
  host-master:/opt/IMAppliance/nbaha-media/server/bin # vmoprcmd
  The following is an output example:
```
HOST STATUS
Host Name                                  Version   Host Status
=========================================  =======   ===========
host-master                                801000    ACTIVE-DISK
host-setup                                 810000    OFFLINE
host-partner                               810000    OFFLINE
```
- Check the storage servers information with the following command:
  host-master:/opt/IMAppliance/nbaha-media/server/bin # nbdevquery -liststs
  The following is an output example:
```
V7.5 host-setup   AdvancedDisk 5
V7.5 host-partner AdvancedDisk 5
V7.5 host-master  PureDisk 9
```
- Check the status of the AdvancedDisk Pool with the following command:
  host-master:/opt/IMAppliance/nbaha-media/server/bin # nbdevquery -listdp -U -stype AdvancedDisk
  The following is an output example:
```
Disk Pool Name   : dp_adv_host-origin
Disk Pool Id     : dp_adv_host-origin
Disk Type        : AdvancedDisk
Status           : UP
…
Storage Server   : host-setup (UP)
Storage Server   : host-partner (UP)
```
- Check the status of the MSDP Disk Pool with the following command:
  host-master:/opt/IMAppliance/nbaha-media/server/bin # nbdevquery -listdp -U -stype PureDisk
  The following is an output example:
```
Disk Pool Name   : dp_disk_host-origin
Disk Pool Id     : dp_disk_host-origin
Disk Type        : PureDisk
Status           : UP
…
Storage Server   : host-origin (UP)
```
Make sure that all the existing storage units can use any available media server after the recovery procedures with the following commands:
/usr/openv/netbackup/bin/admincmd/bpsturep -label AdvanceDisk-storage-unit -nodevhost
/usr/openv/netbackup/bin/admincmd/bpsturep -label MSDP-storage-unit -nodevhost
Rename the media server on the node that you used to set up the HA configuration with the following command:
/usr/openv/netbackup/bin/admincmd/nbemmcmd -renamehost -machinename host-setup -machinetype media -newmachinename [host-origin]
Check the status of the NetBackup objects again as follows:
- Check the status of the media servers in your working system with the following command:
  host-master:/opt/IMAppliance/nbaha-media/server/bin # vmoprcmd
  The following is an output example:
```
HOST STATUS
Host Name                                  Version   Host Status
=========================================  =======   ===========
host-master                                801000    ACTIVE-DISK
host-origin                                810000    OFFLINE
host-partner                               810000    OFFLINE
```
- Check the storage servers information with the following command:
  host-master:/opt/IMAppliance/nbaha-media/server/bin # nbdevquery -liststs
  The following is an output example:
```
V7.5 host-origin  AdvancedDisk 5
V7.5 host-partner AdvancedDisk 5
V7.5 host-origin  PureDisk 9
```
- Check the status of the AdvancedDisk Pool with the following command:
  host-master:/opt/IMAppliance/nbaha-media/server/bin # nbdevquery -listdp -U -stype AdvancedDisk
  The following is an output example:
```
Disk Pool Name   : dp_adv_host-origin
Disk Pool Id     : dp_adv_host-origin
Disk Type        : AdvancedDisk
Status           : UP
…
Storage Server   : host-origin (UP)
Storage Server   : host-partner (UP)
```
- Check the status of the MSDP Disk Pool with the following command:
  host-master:/opt/IMAppliance/nbaha-media/server/bin # nbdevquery -listdp -U -stype PureDisk
  The following is an output example:
```
Disk Pool Name   : dp_disk_host-origin
Disk Pool Id     : dp_disk_host-origin
Disk Type        : PureDisk
Status           : UP
…
Storage Server   : host-origin (UP)
```
Remove the AdvancedDisk storage servers on the partner node from the existing AdvancedDisk pool with the following command:
/usr/openv/netbackup/bin/admincmd/nbdevconfig -changedp -stype AdvancedDisk -dp AdvancedDisk-pool -del_storage_servers host-partner
Note:
The AdvancedDisk storage servers to be removed are created in previous HA configuration creation procedures.
Delete the removed AdvancedDisk storage servers from your working system with the following command:
/usr/openv/netbackup/bin/admincmd/nbdevconfig -deletests -storage_server host-partner -stype AdvancedDisk
Move the backup data from the media servers from the partner node to the media server on the node that you use to set up the HA configuration:
/usr/openv/netbackup/bin/admincmd/bpmedia -movedb -allvolumes -oldserver host-partner -newserver host-origin
Delete the media servers on the partner node:
/usr/openv/netbackup/bin/admincmd/nbemmcmd -deletehost -machinename host-partner -machinetype media
Revoke the host ID-based security certificate for the node that you used to set up the HA configuration with the following command:
/usr/openv/netbackup/bin/nbcertcmd -revokeCertificate -host host-setup

When the procedures are complete, the two-node failure disaster is changed to a regular appliance disaster. For the recovery procedures for a regular appliance disaster, refer to the section About disaster recovery in the document NetBackup Appliance Administrator's Guide.

After the regular appliance disaster is recovered, perform the following procedures to recovery the HA configuration:

To recover the HA configuration

Perform the initial configuration on the appliance you recovered.
During the initial configuration procedure, you need to input the reissue token for the appliance.
When the following message appears, input no:
>> Do you want to clean up existing storage objects? [yes,no]
Set up the HA configuration with the node that you performed the initial configuration.
Perform the initial configuration on the partner node.
Add the configured partner node to complete the HA configuration.
Note:
During the procedure, you need to input the reissue token for the partner node.

For detailed instructions, refer to NetBackup 53xx Appliance Initial Configuration Guide.