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
Troubleshooting network interface card performance
If backup or restore jobs are running slowly, verify that the network interface cards (NIC) are set to full duplex. Half duplex often causes poor performance.
If the NIC in a NetBackup master or media server is changed, or if the server IP address changes, CORBA communications may be interrupted. To address this situation, stop and restart NetBackup.
For help on how to view and reset duplex mode for a particular host or device, consult the manufacturer's documentation. If the documentation is not helpful, perform the following procedure.
To troubleshoot network interface card performance
- Log onto the host that contains the network interface card whose duplex mode you want to check.
- Enter the following command to view the current duplex setting.
On some operating systems, this command is ipconfig.
The following is an example output from a NAS filer:
e0: flags=1948043<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 inet 10.80.90.91 netmask 0xfffff800 broadcast 10.80.95.255 ether 00:a0:98:01:3c:61 (100tx-fd-up) flowcontrol full e9a: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 00:07:e9:3e:ca:b4 (auto-unknown-cfg_down) flowcontrol full e9b: flags=108042<BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500 ether 00:07:e9:3e:ca:b5 (auto-unknown-cfg_down) flowcontrol full
In this example, the network interface that shows "100tx-fd-up" is running in full duplex. Only interface e0 (the first in the list) is at full duplex.
A setting of "auto" is not recommended, because devices can auto-negotiate to half duplex.
- The duplex mode can be reset by using the ifconfig (or ipconfig) command. For example:
ifconfig e0 mediatype 100tx-fd
- For most hosts, you can set full-duplex mode permanently, such as in the host's /etc/rc files. Refer to the host's documentation for more information.