Scribd
Upload
15K views

Code 49

Three Linux client issues can cause NetBackup backups to fail with Status Code 49: 1. Missing compatibility libraries can prevent bpcd from starting. Installing compat-libstdc++ provides the needed symbols. 2. The bpbkar log file reaching 2GB in size can cause it to core dump, failing backups. Renaming or deleting the log file resolves it. 3. Not having the bpbkar binary on the client prevents backups. Reinstalling the client software or renaming a misnamed bpbkar fixes it.

Uploaded by

subhrajitm47
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
15K views

Code 49

Three Linux client issues can cause NetBackup backups to fail with Status Code 49: 1. Missing compatibility libraries can prevent bpcd from starting. Installing compat-libstdc++ provides the needed symbols. 2. The bpbkar log file reaching 2GB in size can cause it to core dump, failing backups. Renaming or deleting the log file resolves it. 3. Not having the bpbkar binary on the client prevents backups. Reinstalling the client software or renaming a misnamed bpbkar fixes it.

Uploaded by

subhrajitm47
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Problem

STATUS CODE 49: A Telnet to the bpcd port on a Linux client results in the error "bpcd: relocation error: bpcd: undefined symbol: __vt_9exception". Bpcd is not starting.

Error
bpcd: relocation error: bpcd: undefined symbol: __vt_9exception

Solution
Overview: If a Linux client is missing the Red hat 7.3 compat-libstdc++ compatibility libraries, then bpcd may fail to start. This is listed as a required operating system patch in the NetBackup 5.1 Release notes. If the libstdc++ RedHat Package Manager (RPM) package is installed, the library files needed for bpcd to start will be available, but they will be missing the needed symbol "__vt_9exception". Without compat-libstdc++, a backup may fail with a Status Code 49. Troubleshooting: To duplicate the problem, telnet to the bpcd port on the client. The telnet should fail immediately with the following error:
# telnet client 13782 Trying x.x.x.x... Connected to <client>. Escape character is '^]' bpcd: relocation error: bpcd: undefined symbol: __vt_9exception

Log Files: n/a Resolution: To correct this problem, install the following (or newer) RPM: compat-libstdc++-7.3-2.96.122 "Standard C++ libraries for Red Hat 7.3 backwards compatibility compiler" This RPM contains the libraries with the required symbols needed for bpcd to run. The TechNote referenced below lists the required RPM's needed for the different versions of Linux.

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
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.

Problem
STATUS CODE 49: Backup attempts will fail reporting status 49 if the bpbkar binary does not exist on the client.

Solution

Overview: Backup of a Netbackup client computer fails with a status code 49. Troubleshooting The master/media server connects to the client's bpcd daemon without issue. Log Files: Reviewing the /usr/openv/netbackup/logs/bpcd log file on the client, the following error was found:
13:38:01.782 [29872] <16> bpcd main: couldn't execute command - status = -1. Errno = 2: No such file or directory

There was also no bpbkar log written, indicating that its process had never started. Resolution: Review the client binaries located in the directory /usr/openv/netbackup/bin and check for the existence of bpbkar in particular. In one case, the NetBackup client binary bpbkar had been accidentally renamed to _bpbkar. Renaming it back to bpbkar allowed backups to succeed. Note: If the bpbkar binary does not exist on the client, reinstalling the client software would also resolve this issue

Problem
NDMP backups and restores end with status 49

Solution
The NDMP option on Unix requires the NDMP patch level to be the same as the server patch level. If this patch level is different then the main patch level many different errors may occur. Sometimes backups and/or restores will work in some cases, but not consistently. The following are possible status codes or messages that may be seen: Status Code 49: client did not start Program terminated with signal 11 Patching the server to the same patch level as NetBackup will resolve the issue.

You might also like