Forum Discussion

Zahid_Haseeb's avatar
Zahid_Haseeb
Moderator
14 years ago

What LOGS should be enable to troubleshoot the connectivity/communication issues

NBU Server = 6.5.x OR 7

What LOGS should be enable to troubleshoot the connectivity/communication issues while doing the activity of Backup and Restore ?

  • Connectivity logs all depend on where the comms is initiated from...

    From master to media server (normal filesystem backup via media server STU):

    bpcd on media server

     

    From Master to client (e.g. ALL_LOCAL_DRIVES backup)

    bpcd on client

     

    From media server to client (normal filesystem backup):

    bpcd on client

    bpbrm media server

     

    From client to master (any client-initiated process, e.g. database backup, client-initiated backup/restore):

    bprd on master

     

    Best is to study the process flow diagram. You need to understand where the comms is initiated and in which direction.

    See Troubleshooting Guide, Appendix A.

    NBU 6.5: http://www.symantec.com/business/support/index?page=content&id=TECH128469&locale=en_us

    NBU 7: http://www.symantec.com/business/support/index?page=content&id=TECH127065&locale=en_us

10 Replies

  • Troubleshooting Guide - PG.104

    NetBackup server legacy debug logs

    generally you would use the following

    bpbkar

    bpbrm

    bpcd

    bprd

    tar

     

  • The issue could also show itself in the IRM logs so I would enable the vx logs also :

    111

    116

    117

    118

    This Technote covers how to do that :

    http://www.symantec.com/docs/TECH75805

     

    Additionally, to get addition Network related info in the above logs and bptm, enable 156 and 137.  Note that these two will significantly increase the log size, however, they do not create separate logs, just add information into some of those above.  You will probably need to use -i not -o when using vxlogview.

     

    Martin

  • i suppose it depends what the problem is -

    Are you just being pro-active - if so, then as Martin said, enable Unified logging as required, and just have enough disk space available - depending on how much logging you require.

     

    Mo

  • Patel

    As you said that bpbkar, bpbrm, bpcd,bprd and tar LOGS record the communication related issue. Why too many LOGS we have to enable just for communication ? second does different LOGS record errors of different stages ?

  • Connectivity logs all depend on where the comms is initiated from...

    From master to media server (normal filesystem backup via media server STU):

    bpcd on media server

     

    From Master to client (e.g. ALL_LOCAL_DRIVES backup)

    bpcd on client

     

    From media server to client (normal filesystem backup):

    bpcd on client

    bpbrm media server

     

    From client to master (any client-initiated process, e.g. database backup, client-initiated backup/restore):

    bprd on master

     

    Best is to study the process flow diagram. You need to understand where the comms is initiated and in which direction.

    See Troubleshooting Guide, Appendix A.

    NBU 6.5: http://www.symantec.com/business/support/index?page=content&id=TECH128469&locale=en_us

    NBU 7: http://www.symantec.com/business/support/index?page=content&id=TECH127065&locale=en_us

  • Zahid, hope Mariannes's post answers your question more easily.

    Thanks Marianne!!

     

  • As from 6.0, all NBU comms are channelled via vnetd. So, add vnetd log dir to clients/servers. I have been able to troubleshoot most comms problems with logs mentioned in my previous post. vnetd will probably help with the more 'tricky' ones.

    For media manager comms, add pbx to the mix. pbx logs are written logs /opt/VRTSpbx/log (UNIX) and install_path\VxPBX\log (Windows). Use 'vxlogview -o 103 .....' to view these logs on master and media servers. (vxlogview usage in Troubleshooting Guide and Commands manual.)

  • Yes Patel. I got alot but you guys did nt throw light on bpbkar,bpbrm  and tar LOGS :(

  • If you go through the process flow diagram, you will see that:

    bpbkar is the backup and archive process on the client. Once the handshake between media server bpbrm (backup and restore manager) and client bpcd completed (i.e. connectivity established), bpcd on client starts bpbkar. Media server has in the meantime started bptm (tape management). bpbkar sends data to bptm and metadata to bpbrm. tar is the process on the client that receives data from bptm during a restore.

    You asked for logs to be enabled to troubleshoot Connectivity/COMMS problems, not the entire data process flow.

    The above is a simplistic description of media <-> client comms/data flow. Full process flow diagram and description in Appendix A of Troubleshooting Guide.