08-25-2012 02:42 AM
C:\Program Files\VERITAS\NetBackup\bin> vxlogview -p 51216 -d all >d:\logging\out.txt
V-1-1-13 NOTE: There were 1,198 corrupted log records.
What this vxlogview basically does
Solved! Go to Solution.
08-26-2012 11:15 PM
The command to delete the vx logs is ...
vxlogmgr -F
I don't think this is in the TN, as deleting logs wasn't something I covered - the TN was getting too complex.
This will delete the unified logs, aprt from the ones that are in use. These MUST NOT be deleted as it will probably break NBU until it is restarted.
The legacy logs (in /usr/openv/netbackup/bin and /usr/openv/volmgr/debug ) can be delete with the operating system delete/ rm commands, but again, you must not delete ayny log files in use (so just avoid deleting 'todays').
The logs under /usr/openv/logs are the unified logs.
The commands to view them are in http://www.symantec.com/docs/TECH75805 under the section "Reading VX logs".
The paths to the commands are :
As far as where is the commands are, look in the post
https://www-secure.symantec.com/connect/forums/netbackup-basics-and-how-make-your-life-easier
Under section A
Martin
08-25-2012 03:20 AM
It is doing nothing , you did not supply the command with "-o" which is to indicate what process you want the logs for.
Example:
vxlogview -p 51216 -o 111 -d all > d:\out.txt
That means you want to get "nbemm" process (its OID is 111) for Netbackup (its ProdID is 51216).
you can also do this for similar purpose
vxlogview -p NB -o nbemm -d all > d:\out.txt
08-25-2012 03:22 AM
So this is basically used for seeing the logs of the services/daemons?
08-25-2012 03:59 AM
No, it is used to convert the logs of the processes that log in these 'unifed' logs to a readable format.
Logs such as bptm are ,legacy' - just straight text files that can be opened and read.
THis TN explains everything you need to know about unified logs.
http://www.symantec.com/docs/TECH75805
NOTE. The TN talks about copying unifed logs - this is all correct, but it is much much easier to use the nbcplogs command
http://www.symantec.com/docs/TECH126223
This is only needed if you are sending in logs to symantec, and the symantec TSE will be able to send you the correct version of the command you need to run.
The unifed logs (vx) logs are created in a raw format. Each log line contains many numbers.
When you run vxlogview it causes NBU to look up these numbers in 'library' files and replace the numbers with 'readable' words.
raw log files are therefore samller than when they have been processed. Generally raw log files should be sent in to symantec, not processed.
When I run vxlogview I usually use these options :
vxlogview -p 51216 -i <oid number> -d all
Some logs don't accept -i, but most do.
EG.
EMM (111) is a NBU process. The EMM log will contain MDS (143) log lines also. So the 'MDS' log is not a separate log file it is part of the EMM log. If I run -o 111 I will only see the EMM lines, if I use -i 111, then I will see the EMM lines and the MDS lines ...
Martin
08-25-2012 04:17 AM
so we use vxlogview for studing the logs in human understandable format?
08-25-2012 04:17 AM
Just to finish the story ...
Here is a raw log line (the last line in the file)
0,51216,219,111,1066955,1345892654820,20454,42,0:,4:Exit,21:RemTimer::doDPSUpdate,5
I will prove this by running the vxlog command using -o and not -i.
(I copied the log to a separate directly, so it is not being updated)
Now we see that the last line displayed is a 'real' '111' line, shown by "NBEMM 111" as opposed to the other line that was "rsrcevtmgr 219".
25/08/2012 12:04:13.343 [Debug] NB 51216 nbemm 111 PID:20454 TID:6 File ID:111 [No context] 1 [DeviceAllocatorImpl::updateMachineState] retval - <0>
08-25-2012 04:36 AM
08-25-2012 07:38 AM
On which path i find vxlogview command?
08-25-2012 08:10 AM
cd /usr/openv/logs/nbpem
$ ls
51216-116-3708150285-120721-0000000000.log
How to view this log?The path where to go and the command to run?
08-25-2012 10:14 AM
Look at the TN I posted the answers are all in that
http://www.symantec.com/docs/TECH75805
Why do you not read what I post - I said that this TN contains all you need to know about the logs.
See the section Reading VX logs
(You will need to use the correct oid number, the examples in the TN show 111 logs, so you will need to use 116).
As far as where is the commands are, look in the post
https://www-secure.symantec.com/connect/forums/netbackup-basics-and-how-make-your-life-easier
Under section A
You should know by now where the NBU binaries are, there are only loacted in 3 different directories, so I am unsure why you are unable to just look for them. Further, you should have the paths set in the your profiles PATH variable so that you don't have to keep entering the full path.
08-26-2012 07:05 PM
08-26-2012 09:13 PM
PLEASE read through Martin's post once again that you have marked as solution:
Then read through the two TechNotes in Martin's post.
You will find the answers to your questions.
If you still need more information, read through Chapter 3 (Using Logs) of Troubleshooting Guide.
vxlogview and vxlogcfg commands are covered in detail in the NBU Commands manual.
This NBU 6 Unified Logging Quick Reference is still valid: http://www.symantec.com/docs/TECH50950
08-26-2012 11:15 PM
The command to delete the vx logs is ...
vxlogmgr -F
I don't think this is in the TN, as deleting logs wasn't something I covered - the TN was getting too complex.
This will delete the unified logs, aprt from the ones that are in use. These MUST NOT be deleted as it will probably break NBU until it is restarted.
The legacy logs (in /usr/openv/netbackup/bin and /usr/openv/volmgr/debug ) can be delete with the operating system delete/ rm commands, but again, you must not delete ayny log files in use (so just avoid deleting 'todays').
The logs under /usr/openv/logs are the unified logs.
The commands to view them are in http://www.symantec.com/docs/TECH75805 under the section "Reading VX logs".
The paths to the commands are :
As far as where is the commands are, look in the post
https://www-secure.symantec.com/connect/forums/netbackup-basics-and-how-make-your-life-easier
Under section A
Martin