Veritas NetBackup™ Troubleshooting Guide
- Troubleshooting procedures
- Troubleshooting NetBackup problems
- Troubleshooting vnetd proxy connections
- Troubleshooting security certificate revocation
- Verifying host name and service entries in NetBackup
- Frozen media troubleshooting considerations
- Troubleshooting problems with the NetBackup web services
- Resolving PBX problems
- Troubleshooting problems with validation of the remote host
- Troubleshooting Auto Image Replication
- Using NetBackup utilities
- About the NetBackup support utility (nbsu)
- About the NetBackup consistency check utility (NBCC)
- About the robotic test utilities
- Disaster recovery
- About disk recovery procedures for UNIX and Linux
- About clustered NetBackup server recovery for UNIX and Linux
- About disk recovery procedures for Windows
- About clustered NetBackup server recovery for Windows
- About recovering the NetBackup catalog
- About NetBackup catalog recovery and OpsCenter
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup relational database
Replacing a failed node on a UNIX or Linux cluster
Cluster technology-specific information is available about how to bring the NetBackup resource group online and offline. Also, information about how to freeze and unfreeze (that is, disable and enable monitoring for) the NetBackup Resource group.
Refer to topics about configuring NetBackup in the NetBackup High Availability Guide:
The following procedure applies when the shared disk and at least one configured cluster node remain available.
To replace a failed node on a UNIX or Linux cluster
- Configure the hardware, system software, and cluster environment on the replacement node.
- Verify that the device configuration matches that of the surviving nodes.
- Ensure that the NetBackup Resource group is offline on all nodes before installing NetBackup on the replacement node.
- Ensure that the NetBackup shared disks are not mounted on the node on which NetBackup is to be installed.
- Freeze the NetBackup service.
- Reinstall NetBackup on the new node or replacement node. Be sure to use the NetBackup Virtual Name as the name of the NetBackup server. Follow the instructions for installing the NetBackup server software.
Refer to the NetBackup Installation Guide:
For the NetBackup Web Services, you must use the same user account and credentials that are used on the other nodes of the cluster. More information is available:
- Install any Maintenance Packs and patches that are required to bring the newly installed node to the same patch level as the other cluster nodes.
- Bring the NetBackup Resource group online on a node other than the freshly installed node.
- Log onto the node on which the NetBackup resource group is online and run the following command:
/usr/openv/netbackup/bin/cluster/cluster_config -s nbu -o add_node -n node_name
node_name is the name of the freshly installed node.
- Switch the NetBackup resource group to the replacement node.
- Freeze the NetBackup group.
- Ensure that the appropriate low-level tape device and robotic control device configuration necessary for your operating system has been performed. Information is available for your operating system.
Refer to the NetBackup Device Configuration Guide:
- Run the Device Configuration Wizard to configure the devices. You do not have to rerun the device configuration on the pre-existing nodes. Configuration information on your particular cluster is available.
See the NetBackup Administrator's Guide, Volume I:
- Check that the robot numbers and robot drive numbers for each robot are consistent across all nodes of the cluster. Repeat for any other servers that are connected to that robot and correct if necessary.
See the NetBackup Administrator's Guide , Volume 1:
- Test the ability of NetBackup to perform restores using the configured devices on the replacement node.
- Unfreeze the NetBackup resource group.