Please enter search query.
Search <product_name> all support & community content...
STATUS CODE 49: 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: 100016886
Last Published: 2007-01-02
Ratings: 5 2
Product(s): NetBackup
Problem
STATUS CODE 49: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:
Bbackup job fails the with error message Client did not start (49) when the
Troubleshooting:
This can be verified by running the
Resolution:
If running the
check the size of the
Bbackup 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.
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.