Video Screencast Help

logs

Created: 12 Sep 2012 • Updated: 13 Sep 2012 | 7 comments
This issue has been solved. See solution.

What/where  logs to see when:

  1. My drives are down
  2. My robot/library is down
  3. my master server is down
  4. my disk pool is down
  5. media is freeze/suspended

 

Comments 7 CommentsJump to latest comment

Yasuhisa Ishikawa's picture

1. syslog / event log

2. syslog / event log

3. various logs. determine wich process goes down and look into relevant logs. if OS goes down, ask OS/HW admins and vendors

4. depends on root cause. for first, bpdm, OST vendor specific logs

5. netbackup log(bperror) and syslog / event log

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

Marianne's picture

Seems like another 'lets suppose' question..........

Have you tried to read through  'Using logs' (chapter 3) in the Troubleshooting Guide as we have suggested many times before?

There are also many TNs out there that we regularly share on this forum (please take time to read through other posts on this forum - we all learn something new every day while doing this), e.g.
http://www.symantec.com/docs/TECH169477 
OLD but still valid TN for legacy logs as well as system logs: http://www.symantec.com/docs/TECH18012 
Another OLD TN (still valid for legacy logs): http://www.symantec.com/docs/TECH31097 
Unified logs: http://www.symantec.com/docs/TECH43251

etc... etc... Google will help you find more...
(Hint: start Google search with: 
site:symantec.com netbackup  ...........  )

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Stuart Green's picture

Its OK Marianne I got this one covered.

http://lmgtfy.com/?q=site:symantec.com+netbackup+N...

>16,000 results Waoh.

NIKHIL you could just look in your Connect profile at what you have already posted.

 

Its interesting that sometimes I come across a problem I have, not even in NetBackup (per.se) and I use Google to research. And staring me in the face is a result describing the SAME problem.

What a let down when I realise its was me posting it previously! smiley

Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.

• If this provides help, please vote or mark appropriate solution.

NIKHIL2346565959's picture

@Yasuhisa

When we see the bptm logs then?We dont see bptm logs when there is a drive issue?

Stuart Green's picture

There are the legacy debug log directories like ../logs/bptm/ but you could use bperror command to see some event output of netbackup. Here is the syntax: that could answer all your questions above

 

USAGE: bperror {-S|-statuscode status_code}
           [-r|-recommendation] [-v]
       bperror  [-all|-problems|-media|-tape]
           [-disk|-BasicDisk|-NearStore|-SnapVault|
            -DiskPool]
           [{-backstat [-by_statcode]}-L|-l|-U] [-columns ncols]
           [-d mm/dd/yyyy HH:MM:SS|-hoursago hours] [-e mm/dd/yyyy HH:MM:SS]
           [-client client_name] [-server server_name]
           [-jobid job_id] [-jobgroupid job_group_id]
           [-M master_server,...] [-v]
       bperror  [-s {severity[+]}|severity ...] [-t type ...]
           [-dt disk type ...]
           [-L|-l|-U] [-columns ncols]
           [-d mm/dd/yyyy HH:MM:SS|-hoursago hours] [-e mm/dd/yyyy HH:MM:SS]
           [-client client_name] [-server server_name]
           [-jobid job_id] [-jobgroupid job_group_id]
           [-M master_server,...] [-v]

       -by_statcode is used only with both -U and -backstat

       Valid values for ncols:
           40 or more

       Valid values for severity:
           ALL, DEBUG, INFO, WARNING, ERROR, CRITICAL

       Valid values for type:
           ALL, ARCHIVE, BACKSTAT, BACKUP, GENERAL,
           MEDIADEV, DISK, BASICDISK, NEARSTORE, DISKPOOL,
           SNAPVAULT, TAPE, RETRIEVE, SECURITY

       Valid values for disk type:
           0 = ALL, 1 = BASICDISK, 2 = NEARSTORE, 3 = SNAPVAULT,
           6 = DISKPOOL

 

 

Want to see drive\tape issues? You can also see here:

On the respective master/media server look at the file
{install_path}Veritas\netbackup\db\media\errors

 

Or issue command:

bperror -tape

OR

bperror -t TAPE -s ERROR

shows a lot of bptm activity, with this just only shows TAPE type entries with ERROR severity.

So if you see none. You aint got to worry 'bout a thing.

 

These are all good tips. Want a big tip. Got these all from running nbsu on my system and looking through the output. {Sssh dont share with anyone. Just between you and me. OK!}

Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.

• If this provides help, please vote or mark appropriate solution.

Marianne's picture

Have you opened any of the TNs that I have posted above?

Have you opened TN: http://www.symantec.com/docs/TECH169477 

Troubleshooting Robot or Drive Issues in NetBackup

The TN's are meant to help you understand which OS and which NBU logs to have a look at....

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
CRZ's picture

Guys, I know it's tough to pass up on easy points, but I really think it's time to stop answering "what if" questions from this user for a while.  Presented with evidence of a REAL issue, sure, jump right in - that's what this community is all about, but our collective courtesy regarding the theoretical stuff has been reallllllllly overextended past the breaking point.