Definition of each field in bpflist command output. 
http://seer.support.veritas.com/docs/271392.htm

Details:
* When running the bpflist command, there are several cryptic fields
that return in the output. There are 17 fields
and are defined in this TechNote, 1 through 17.

* This example applies to standard backups. There may be exceptions
with AFS file systems due to the differences in mode bit rights.

Example of the output from an execution of the bpflist command:

/usr/openv/netbackup/bin/admincmd/bpflist

9 0 9 49 47 1 0 0 35651584 /test/ddd 33188 root other 20 958143374
958143227 959788518

1. file sequence number in the backup image (starts at 1, a zero means
this file is NOT in the image)
2. compressed size in bytes, plus 7 as safety margin (0=not
compressed)
3. number of characters in the path name 
4. number of characters in the files file line from the field *after*
the path name to the end of the line
5. starting block of this file's data in the backup image
6. in_image flag (0=not in image, 1=in image)
7. raw partition size in bytes (0=not a raw partition)
8. size of the file in GBytes (only set if the file is bigger than 2
GBytes, otherwise zero)
9. file system physical device number
10. path name
11. mode bits in decimal (convert to octal - see below)
12. owner 
13. group
14. real size in bytes (as in on-disk inode)
15. last access time
16. last modification time
17. last inode modification time

The 11th field on each line is the file/directory permissions in
DECIMAL.
To see the file permission bits more clearly, convert the value into
OCTAL.
E.g.: if the value in the file is 16877 decimal, this is actually 40755
in octal, which indicates that it is a directory (040000) with
permissions rwxr-xr-x (00755).
A full list of the meanings of all the mode bits can be found on a
Solaris system in /usr/include/sys/stat.h towards the bottom of the file
(or in the equivalent header file on other UNIX platforms).
It can be confusing because the permission bits are listed in octal,
but the rest of the bits are listed in hexadecimal - it often requires
writing out the value in binary to be clear about which bit positions
are set. 
VERITAS
"Ain't it the truth? Ain't it the truth?" Bert Lahr, Wizard of Oz 1939

 


>>> "Jeff Lightner" <jlightner at water.com> 3/29/2007 11:01 AM >>>

bpflist -backupid <id> -d <start> -e <end>

No man page for bpflist (in 5.1 MP4 at least).  Even though you
specify
the backupid you have to specify the start and end for some reason or
it
will say "no entity".

bpflist -j will make it produce help/usage display so you can see all
the options.

-----Original Message-----
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of
Chris.Romano at Lazard.com
Sent: Thursday, March 29, 2007 10:38 AM
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] How can I retrieve files backed up from backup
id
(from command line)

The bpimagelist command gives me the following for images created on a
specific
day for a particular policy:

   IMAGE nydux-25k106 0 0 7 nydux-25k106_1171691274 nydux-25k106 0
*NULL* root
   database

Does anyone know if there is a command to retrieve the actual files
backed up
(or even better, the list of directories passed to the bpbackup
command
to be
backed up)?
I would like to input the backup id (nydux-25k106_1171691274) and get
more info
on what was being backed up (but on the command line, not the GUI).



Thanks,
Chris.


_______________________________________________
Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

_______________________________________________
Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20070329/054f22a0/attachment.html