STATUS CODE 49: When using Veritas NetBackup (tm) 5.x, the backup job fails with the error message "Client did not start (49)", but all the services/daemons are running fine, and it can communicate with other NetBackup systems without any issues.

Article:TECH37845  |  Created: 2005-01-15  |  Updated: 2007-01-02  |  Article URL http://www.symantec.com/docs/TECH37845
Article Type
Technical Solution

Product(s)

Environment

Issue



STATUS CODE 49: When using Veritas NetBackup (tm) 5.x, the backup job fails with the error message "Client did not start (49)", but all the services/daemons are running fine, and it can communicate with other NetBackup systems without any issues.

Error



Client did not start (49) Filesize limit exceeded (core dumped)

Solution



Overview:
It was observed that a NetBackup 5.x backup job fails the with error message Client did not start (49) when the bpbkar log file size is near 2GByte (2147483647Byte)

Troubleshooting:
This can be verified by running the bpbkar command, from the command line prompt as follows:

nbuserver# /usr/openv/netbackup/bin/bpbkar

Resolution:
If running the bpbkar commands results in a core-dumps and comes back to the command prompt with the following error message:,

Filesize limit exceeded (core dumped)

check the size of the bpbkar log in /usr/openv/netbackup/logs/bpbkar directory. If the size of the log file (log.mmddyy) is near 2GByte, renaming and/or deleting the log file may resolve the issue.

Supplemental Materials

SourceError Code
Value49
DescriptionNetBackup status code 49: client did not start

Legacy ID



275756


Article URL http://www.symantec.com/docs/TECH37845


Terms of use for this information are found in Legal Notices