> Two questions here on save sets:
>
> 1. Is there a way to determine which volume a specific path name is on
> if the parent file system is split across multiple tapes? I'm assuming
> we're still in the browse policy for the affected client.
>
> For example, let's say I have a client named fred with 2 file systems
> (/, /0) and saveset recover shows that the last full for /0 is contained
> on volumes: vol001, 002 and 003. Is there a way I can determine which
> tape contains a specific path under /0, e.g. /0/data/dir or say a
> specific file?
I've never tried to do so in anger, but presumably this is possible.
Use nsrinfo -V to get the file offset within the saveset. Then do a
'mminfo' with a report to show fragment boundaries. That will give you
the volume and file position on the volume for that offset.
> Obviously, I can run 'nsrinfo -s server client | grep path_name', but
> that will only tell me the nsavetime, not the volume. The nsavetime will
> be the same for all pieces of the saveset (/0) for the full, so I don't
> see how using nsrinfo with the nsavetime will be able to help because it
> will show all the volumes with that nsavetime value, not the one volume
> that actually contains the path?
$ nsrinfo -V -N /etc/passwd -t 1075927189 jumpy
scanning client `jumpy' for savetime 1075927189(Wed Feb 4 12:39:49
2004) from the backup namespace
/etc/passwd, size=912, off=1167092432, app=backup(1)
1 objects found
So it's 1167092432 into it...
$ mminfo -aV -q 'savetime=1075927189'
volume client size level name
ssid save time date time browse retent
first last file rec volid total fl
DLT.001 jumpy 610 MB full /
559752705 1075927189 02/04/04 12:39:49 PM 03/06/04 02/03/05
0 625372715 2 0 559748097 3897729916 hE
DLT.001 jumpy 1221 MB full /
559752705 1075927189 02/04/04 12:39:49 PM 03/06/04 02/03/05
625372716 1250906195 3 0 559748097 3897729916 mE
DLT.001 jumpy 1832 MB full /
559752705 1075927189 02/04/04 12:39:49 PM 03/06/04 02/03/05
1250906196 1876280955 4 0 559748097 3897729916 mE
DLT.001 jumpy 2443 MB full /
559752705 1075927189 02/04/04 12:39:49 PM 03/06/04 02/03/05
1876280956 2501890863 5 0 559748097 3897729916 mE
DLT.001 jumpy 3054 MB full /
559752705 1075927189 02/04/04 12:39:49 PM 03/06/04 02/03/05
2501890864 3127483339 6 0 559748097 3897729916 mE
DLT.001 jumpy 3665 MB full /
559752705 1075927189 02/04/04 12:39:49 PM 03/06/04 02/03/05
3127483340 3753229087 7 0 559748097 3897729916 mE
DLT.001 jumpy 3806 MB full /
559752705 1075927189 02/04/04 12:39:49 PM 03/06/04 02/03/05
3753229088 3897729915 8 0 559748097 3897729916 tE
So I presume this file is on DLT.001 (duh in this case), in the fragment
beginning at file offset 3 on the volume.
> 2. Guess this is the converse of question 1. Is there a way to see all
> the files (pathnames) on a given volume that are still within the browse
> policy? mminfo shows only saveset names, and nsrinfo won't show you the
> volumes.
Not directly. I'd parse 'mminfo' output to learn the offsets that are
on the volume. Then I'd have a script read the 'nsrinfo -V' output,
printing only the names that have offsets that appeared valid.
--
Darren Dunham ddunham AT taos DOT com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
