Basic Troubleshooting Tips for Veritas 4.

5fp6 on
Windows platform.

Note : Registry settings for veritas are located in HKEY_LOCAL_MACHINE - Software

- Veritas - Netbackup - CurrentVersion – Config, After every registry change Do
remember to restart the netbackup client services for the changes to take effect.

Note 2: Logs files of the clients are located at <installation path>\veritas\netbackup\logs.

Important logs files of interest
• Bpcd : It has the detailed information on how the connectivity of the backup
client and media server completed/dropped over the Veritas Ports
• Bpbkar : It has the details on , How the file backup happens and at which files or
drives it got hung/dropped.

Note 3: To get the detailed Logs and all registry settings of veritas, set the verbose level
to 5 on the backup client server. How to do it :
• Start program files veritas netbackup backup client
• File  client properties
• Troubleshooting  verbose set it value to 5.

Few Important-troubleshooting Tips, to be always remembered:

• The connectivity between the media server and the backup client server needs to be there
at bpcd Port for the veritas backup to Work properly.
• The connectivity between the Master server and backup client server is not required.
• The host files of the Windows client is saved in c:\winnt\system32drivers\etc\hosts
• To verify the bpcd and bprd ports on the backup client servers check the file
c:\winnt\system32\drivers\etc\services.
bpcd 13782/tcp
bprd 13720/tcp
• The Required Interface Registry value is must for the Clients using the backup LAN for
backup and follow the nomenclature of backup client servers naming for VLANs
• Example based on Dupont clients If backup client name is XXX and has IP 192.168.2.3
Its backup client servername would be XXXe, The backup client server name is defined
in the following registry parameters,
o Browser
o Client_name
o Required_Interface
Based on the client name in Dupont we give the Media Master servername, Like in above
example it should be ndcbk02e, ndcvcnb02e, ndcvnb03e,ndcvnb04e, ndcvnb04e,
ndcvnb05e.
 Fyi.. Below is backup LAN IP Schema used for the Dupont Backup VLAN.

192.168.1.0 to 63 VLAN A
192.168.1.65 to 126 VLAN B
192.168.1.128 to 191 VLAN C
192.168.1.193 to 254 VLAN D
192.168.2.0 to 63 VLAN E
192.168.2.65 to 126 VLAN F
192.168.2.128 to 191 VLAN G
192.168.2.193 to 254 VLAN H

Few Important status codes and the detailed interpretations.

Error Code 11, System call failed

This error code is related to the OTM/VSP. We have two alternatives for these problems,

1. Easy way out Turn Off the OTM/VSP by going to registry and setting value of
OTM_USE=NO and VSP_USE=NO, We seldom use this as a Last resort for solving the
Error 11 tickets.
2. Secondly, If we need to troubleshoot, then we will start with setting following registry
Key values

· OTM_Cache_Size_Max · specifies the maximum cache size (in megabytes) of the cache file. :
Set Max cache size to 0MB. With the Max Cache Size set to 0MB, OTM will calculate 10
percent of the used disk space as its maximum

· OTM_Cache_Size_Init · Netbackup Properties Specifies the initial size of the cache file (in
megabytes). If a specific value is not set, Netbackup sets it to 10 megabytes. Set Initial cache size
to 100MB. OTM will create the initial cache file before the backup starts.

Error Code 13, File Read Failed

Error Code 14, File Write failed

These error codes mostly occur because of slow network or slow response time from the
backup client server. To resolve this mostly we re-queue the backups and it works
correctly.

In rare cases these errors, point to the hardware issues on the client server, which may be
related the Hard disk drive issues or network card, to find the details one has to go
through the event log of the Windows NT/2000 server and check the NIC statistics.
Error Code 41, Network connection timed out

This error generally occurs if the client server does not exist on the network at all
Probably a Server IP change, Or mostly in the case when the backup client server get
rebooted while backing up.

Error code 54, Timed out connecting to client

This is most peculiar type of error, which explains that the TCP connectivity never got
completed on the backup client server. Remedies for this error
• Study the bpcd logs of the backup client server in detail for any errors.
• Lookout for the backup client connectivity to the media server by start  run
telnet <mediaserver> Bpcd
• Check the client registry settings, they need to be as per the installation guide for
Dupont and other clients
• If all settings and registry parameters seems correct, and connectivity seems
working. Then as a Last resort got for the machine reboot. It resolve the problem
in most of error 54 cases.

Error code 56, client network is unreachable

This error occurs commonly when the backup client machine is unreachable from the
media server. The following needs to be checked
• The backup client host name should be there in the host file of the media server.
• The media server should able to make connectivity to the backup client server on
bpcd port
• The netbackup services should be running at the client machine.
• The client connectivity can be checked by giving the command at the media
server
#telnet <client servername> bpcd

If the client connectivity doesn’t work then work on with network team to resolve any
firewall or probable network routing problem
Error code 57, Client connection refused

This error is most simplest of errors to resolve as it occurs because at the backup client
server machine the NETBACKUP Client services are not running. Start/ReStart the
services and the problem will resolve.

Error code 58, Can’t connect to the client

This error means that the media server is unable to connect to the client. Check the
following
• Is correct IP address and hostname mapping is done for the client Servername in
the media server
• In case of separate backup LAN is the backup interface on the client is connected
and working
• The client connectivity can be checked by giving the command at the media
server
#telnet <client servername> bpcd
• The error may occur, as connectivity from client to media server is not working.

Error Code 59, Access to client was not allowed

This error means that the media and master server named at the backup client server are
wrongly defined. One can check the name of the media and master servers at registry
parameter Server value. The backup client server must have the host file entries for the
media and master server.

Error code 84, Media write error

This error indicates that there is problem in the I/O operations of the Media. The Media
needs to be changed or checked. This may be because of a defective drive.
Error code 155, Disk is full

This error indicates that the client is using the VSP and the VSP cache disk is full. The
alternatives to solve this problem are
• Free up some disk space at backup client server
• Check if the backup client server has *.vsp caches exist, which ideally needs to be
deleted automatically except few exceptions, If *.VSP files exist follow the Doc
posted in the Database for deleting these locked files having extension VSP.
• The easy remedy is disable the VSP use, by setting value of VSP_USE=NO.

Error code 196, Client backup not attempted because window closed

This error is self explanatory, It occur if a client backup is not attempted and it got exit
from the queue status directly because the permissible period for the backup of the client
is already expired. The Veritas policy needs to be checked for any slow client and needs
to troubleshoot if it’s a daily occurrence.

Error code 219, the required storage is unavailable

This error occurs because of the Storage drive unavailability problem on the requested
media server. This problem if occurring for all the clients active at a certain time, then it
needs to be looked at the Media server end.