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.

Problem

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 Message

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.

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)