How to analyze Netbackup Unified Logs

For legacy Netbackup logs which is located under /usr/openv/netbackup/logs , below numbers can indicate to you the severity when troubleshooting. Usually look at number 16 for error or 32 for fatal error which means you need to focus and google that error to look for answer:

Severity:
1 = Unknown
2 = Debug
4 = Info
8 = Warning
16 = Error
32 = Critical

Example:
bash-3.00# pwd
/usr/openv/netbackup/logs/dbclient
bash-3.00# grep -i "<16>" log.032211
01:01:47.985 [19945] <16> readCommFile: ERR - timed out after 900 seconds while reading from /usr/openv/netbackup/logs/user_ops/dbext/logs/19945.0.1300767393
01:01:47.985 [19945] <16> VxBSAEndTxn: ERR - bsa_close() failed.
01:01:47.986 [19945] <16> xbsa_EndTransaction: ERR - VxBSAEndTxn: Failed with error:
02:27:59.607 [944] <16> readCommFile: ERR - timed out after 900 seconds while reading from /usr/openv/netbackup/logs/user_ops/dbext/logs/944.0.1300772039

The following directories can be created for administrative command logging.
/usr/openv/netbackup/logs/admin - Log used as a central logging repository for all the commands located in the /usr/openv/netbackup/bin/admincmd directory.
• /usr/openv/netbackup/logs/bp - Log for the curses-based bp interface program (client-side).
• /usr/openv/netbackup/logs/bpadm - Log for the curses-based bpadm interface program (server-side).
• /usr/openv/netbackup/logs/bparchive - High-level logging of the bparchive command.
• /usr/openv/netbackup/logs/bpbackup - High-level logging of the bpbackup command.
• /usr/openv/netbackup/logs/bpdbjobs - High-level logging of the backup and restore job reporter command.
• /usr/openv/netbackup/logs/bplist - High-level logging of the detailed image list reporting command.
• /usr/openv/netbackup/logs/bpmount - High-level logging for the drive-listing command, used for ALL_LOCAL_DRIVES on the client.
• /usr/openv/netbackup/logs/bprestore - High-level logging of the restore command.

Logs for NetBackup daemons and other automatically-run commands:
• /usr/openv/netbackup/logs/bpbkar - Logs for the backup and archive daemon on the client (backup and archive operations).
• /usr/openv/netbackup/logs/bpbrm - Logs for the backup and restore manager on the media server.
• /usr/openv/netbackup/logs/bpbrmds - Logs for the backup and restore manager on the media server (for disk staging operations).
• /usr/openv/netbackup/logs/bpcd - Logs for the communications daemon on media servers and clients.
• /usr/openv/netbackup/logs/bpcoord - (For NetBackup 5.x) Logs for the bpcoord daemon started by bpsynth on the master server.
• /usr/openv/netbackup/logs/bpdbm - Logs for the database manager daemon on the master server.
• /usr/openv/netbackup/logs/bpdm - Logs for the disk manager daemon on the media server (disk storage units only).
• /usr/openv/netbackup/logs/bpjava-msvc - Java GUI authentication service on the master server.
• /usr/openv/netbackup/logs/bpjava-susvc - (For NetBackup 4.5 and 5.x) Java GUI login service on the master server.
• /usr/openv/netbackup/logs/bpjava-usvc - Java GUI "user" service on the master server.
• /usr/openv/netbackup/logs/bprd - Logs for the request daemon on the master server.
• /usr/openv/netbackup/logs/bpsched - Logs for the scheduler daemon on the master server.
• /usr/openv/netbackup/logs/bpsynth - (For NetBackup 5.x) Logs for the bpsynth process for synthetic backups on the master server.
• /usr/openv/netbackup/logs/bptm - Logs for the tape manager daemon on the media server (media manager storage units only).
• /usr/openv/netbackup/logs/mtfrd - (For NetBackup 5.x) Logs for phase 2 import of Backup Exec media on the master server.
• /usr/openv/netbackup/logs/tar - Logs for the restore daemon on the client (restore operations).
• /usr/openv/netbackup/logs/user_ops - Contains directories and files used by Java and database agents on servers and clients.
• /usr/openv/netbackup/logs/bphdb - Logs for the program that starts scripts to backup the database on servers and clients.
• /usr/openv/netbackup/logs/dbclient - log for the DB Extension clients

Daemons that use Unified Logging
A listing of processes and originators that use Unified logging include, but are not limited to:
  • NetBackup Policy Execution Manager (nbpem)
  • NetBackup Job Manager (nbjm)
  • NetBackup Resource Broker (nbrb)
  • NetBackup Enterprise Media Manager (nbemm)
  • NetBackup Service Layer (nbsl)
  • NetBackup Generic Job (nbgenjob)
  • NetBackup Notification Service (nbnos)
  • NetBackup for NDMP and ndmpagent
  • NetBackup avrd and robotic processes
  • NetBackup Operations Monitor (NOMTRS, NOMClient and NOMServer)
  • Bare Metal Restore daemons (bmrd, bmbbd, bmrc, bmrs, bmrconfig, bmrsavecfg, bmrsrtadm, bmrprep, bmrsetupmaster, bmrsetupboot, bmrpkg, bmrcreatepkg, bmrcreatefloppy.exe, bmrrst.exe and bmrmap.exe)
  • VERITAS Private Branch Exchange (VxPBX)

Daemons that continue to use Legacy logging
A listing of daemons that use Legacy logging include, but are not limited to:
  • NetBackup Master Server daemons (bprd, bpdbm, bpjobd, bpdbjobs, admin)
  • NetBackup Media Server daemons (bpbrm, bptm, bpdm)
  • NetBackup Robotic daemons (vmd, avrd, ltid and robotic daemons)
  • NetBackup Client daemons (bpcd, bpbkar, tar)


5 comments:

Noise Figure said...

Thanks for this informative post which made me so delighted. Really, great job....


network analyzer calibration

Razali Shoib said...

Sorry Syed, wrong typo. at the beginning of the comment

Razali Shoib said...

Hi Syed,

May I have your kind advise regarding jnbSA?

This is regarding status code 505 in Solaris 9. This machine was relocated from site A to site B. I’ve changed the IP’s. But when I want to launch the jnbSA below error occured :

Error
Unable to login, status: 505
Can not connect to the NB-Java authentication service on on the configured port – 13722.

Exception: java.lang.NullPointerException
Exception message: null

Action Taken :
Follow from Symantec Web.
*http://www.symantec.com/business/support/index?page=content&id=TECH47405&actp=search&viewlocale=en_US&searchid=1333019069849
*http://www.symantec.com/business/support/index?page=content&id=HOWTO51123&actp=search&viewlocale=en_US&searchid=1333019069849
*http://www.symantec.com/business/support/index?page=content&id=TECH66075&actp=search&viewlocale=en_US&searchid=1333019069849
*http://www.symantec.com/business/support/index?page=content&id=TECH35899&actp=search&viewlocale=en_US&searchid=1333019069849

Perhaps you can direct me to where should i look.

Warmest Regards,
Razali Shoib

Syed .Z said...

Hi Razali,

from site A to B, i assume its a different server. Can you paste /usr/openv/java/auth.conf files

Razali Shoib said...

Hi Syed,

Thanks for replied. Actually the server hardware still the same. Just move the equipment to new buildings.

Hardware Equipments :
Sun V440, StorEdge 3210 and SL500

Here as per requested :
auth.conf
root ADMIN=ALL JBP=ALL
* ADMIN=JBP JBP=ENDUSER+BU+ARC

Version :
NetBackup-Solaris9 5.1MP6

Below are the logs I run the ./jnbSA & :
Character encoding = ISO8859_1
HostConnectionsMgr:updateHostConnectionCount:HostConnection nonexistent:root