Getting exit status 252 and error message "NBEMM returned an extended error status: invalid error number (4005006)" on client backups.

Article:TECH56312  |  Created: 2007-01-19  |  Updated: 2008-01-21  |  Article URL http://www.symantec.com/docs/TECH56312
Article Type
Technical Solution


Environment

Issue



Getting exit status 252 and error message "NBEMM returned an extended error status: invalid error number (4005006)" on client backups.

Error



<16> send_MDS_msg: NBEMM returned an extended error status: invalid error number (4005006)

<16> send_MDS_msg: Error from emmlib_handleMessage, Master master.mymaster.com, type 8, returned error 4005006

Solution



Question: What is status 252?

Question: What is "error number 4005006" or "status 4005006"?

Exact Error Message:

<16> send_MDS_msg: NBEMM returned an extended error status: invalid error number (4005006)
<2> send_brm_msg: ERROR 252
<2> mpx_terminate_exit: EXITING with status 4005006
<2> cleanup: Detached from BPBRM shared memory
<16> send_MDS_msg: Error from emmlib_handleMessage, Master master.mymaster.com, type 8, returned error 4005006
<2> set_job_details: Sending Tfile jobid (1641)
<2> set_job_details: LOG 1197884047 16 bptm 13538 NBEMM returned an extended error status: invalid error number (4005006)

Reference: VERITAS NetBackup 6.0 Troubleshooting Guide, Page 250:
"NetBackup Status Code: 252
Message: An extended error status has been encountered, check detailed status
Explanation: If a process was unable to report the extended error status as the final job
status, the job exits with status 252. (The extended error status has a number greater than 255.)
Recommended Action: To determine the actual error, examine the job details display."

Reference: emmlib source:
#define EMM_ERROR_DBServerDown                              4005006

Environment: Standard NetBackup backup for clients.

Change: Upgraded from NetBackup version 5.0 or 5.1 to 6.0 or 6.5.

Cause: EMM Database Server is stopped or offline.

Cause: Volume where EMM Database or NetBackup resides is full.

Cause: NetBackup and EMM services are stopped.

Cause: Offline Catalog backup is running.  While running it stops the EMM Database Server.

Cause: Another process has return a exit code that is not recognized.  

Solution:
1) See the appropriate process reporting error.

2) Enable logging for that process (such as bptm) at maximum verbosity to capture and confirm the error code from that process, 4005006.

3) Once confirm, error code 4005006 indicates that the EMM Database Server is down or offline.

4) Verify whether or not this is true.

5) If true, confirm if (A) an offline catalog backup was running at that time, (B) filesystem is Full, and/or (C) NetBackup services is stopped.

6) Rectify the root cause by (A) do not schedule and run backup jobs while offline catalog backup is running, (B) clean up filesystem, and/or add more space, and/or (C) ensure NetBackup processes are running and you can query and verify EMM connections via nbemmcmd commands.

NOTE: The nbemmcmd command can be found at the default path /usr/openv/netbackup/bin/admincmd/ for UNIX/Linux or c:\program files\veritas\netbackup\bin\admincmd\ for Windows. Easiest way to confirm EMM connectivity is by running on master and EMM server: nbemmcmd -listhosts -verbose

NOTE: If the root cause is scheduling conflict between scheduled backup jobs and offline catalog backup, consider (a) using online hot catalog backup instead, or (b) re-schedule jobs around the length of time an offline catalog backup needs to run until completion.


Legacy ID



295143


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


Terms of use for this information are found in Legal Notices