Friday, July 15, 2005

NetBackup Error codes

Hi!

Status Code: 50
client process aborted
The client backup aborted. One instance when this code appears is if a
NetBackup master or media server is shut down or rebooted when a backup
or restore is in process.

Try the following:

1. Enable detailed debug logging:
* Create a bpbkar debug log directory (UNIX or Windows only).
* Create a bpcd debug log directory (this log is created automatically
on Macintosh clients.)
* On UNIX clients, add the VERBOSE option to the
/usr/openv/netbackup/bp.conf file.
* On PC clients, increase the debug or log level as explained in the
debug log topics in Chapter 3 of the Troubleshooting Guide.
2. Retry the operation and examine the resulting logs.
3. On UNIX clients, check for core files in the / directory.
4. On UNIX clients, check the system log (/usr/adm/messages on Solaris)
for system problems.
5. This problem can sometimes be due to a corrupt binary.
On UNIX clients, use the UNIX sum command to check the bpcd, bpbkar,
and tar binaries, located in /usr/openv/netbackup/bin on the client.
Reinstall them if they are not the same as in the client directory
under /usr/openv/netbackup/client on the server.
Run the NetBackup Configuration Validation Utility (NCVU) for the
associated NetBackup clients. Note the client software checks in
section two.
On a Windows client, check the bpinetd.exe, bpcd.exe, bpbkar32.exe, and
tar32.exe executables located in the install_pathNetBackupbin folder on
the client. Reinstall the client if these executables are not the same
size as on other Windows clients or are not at the same release level
or do not have the same NetBackup patches applied as other Windows
clients.

Status Code: 57
client connection refused
The client refused a connection on the port number for bpcd. This can
occur because there is no process listening on the bpcd port or there
are more connections to the bpcd port than the network subsystem can
handle with the listen() call.

Try the following:

1. For Windows NetBackup servers:
a. Make sure the NetBackup client software is installed.
b. Verify that the bpcd and bprd port numbers in the
%SystemRoot%system32driversetcservices file on the server matches the
setting on the client.
c. Verify that the NetBackup Client Service Port number and NetBackup
Request Service Port number on the Network tab in the NetBackup Client
Properties dialog match the bpcd and bprd settings in the services
file. To display this dialog, start the Backup, Archive, and Restore
interface on the server and click NetBackup Client Properties on the
File menu.
The values on the Network tab are written to the services file when the
NetBackup Client service starts.
d. Verify that the NetBackup client service is running.
e. Use the following command to see if the master server returns
correct information for the client:
install_pathVERITASNetBackupbinbpclntcmd -pn
2. For UNIX servers:
a. Make sure the NetBackup client software is installed.
b. Verify that the bpcd port number on the server (either NIS services
map or in /etc/services) matches the number in the client's services
file.
c. Run the NetBackup Configuration Validation Utility (NCVU) for the
associated NetBackup nodes. Note the NetBackup services port number
checks in section one.
3. For a Macintosh or NetWare target client, verify that the server is
not trying to connect when a backup or restore is already in progress
on the client. These clients can handle only one NetBackup job at a
time.
4. Perform "Resolving Network Communication Problems" in the
Troubleshooting Guide.

May I know what version of Netbackup you are using? You might also want
to check if the /kernel/drv/st.conf and /kernel/drv/sd.conf
overwritten. Thanks.

0 Comments:

Post a Comment

<< Home