Hi George,

 
The output you show on your message contains the savetime in  both numeric and 
date format.

+----------------------
 scanning client `client1' for savetime 1297121469(Mon Feb  7 18:31:09
 2011) from the backup namespace on server server1
-------------------------------------+

what exact command did you execute and what other savetime did you expect but 
couldn't get?

If you ran something like
  nsrinfo -t 1297121469 client1
or
   nsrinfo  -v -t  "02/07/2011  18:31:09" client1

then you should not expect any other savetime, just the one associated to the 
whole bunch of entries that belong to that particular saveset.



jee



On Wednesday 09 February 2011 01:03:41 George Sinclair wrote:
> The man page for nsrinfo says:
>
> "-v     Verbose mode.  In addition to the filename, it prints the type
> of the file, the internal file index identifier (if any), the size (if a
> UNIX file), and the savetime.  This option may be combined with the -V
> option."
>
> When I use this option, I don't see a savetime for the entries. I see a
> bunch of entries that look like:
>
> ndirentry->3571821    somefname
>
> UNIX ASDF v2 file `/path/dir/fname1, NSR size=143209364, fid =
> 64818.49155, file size=143182949
>
> Are the numbers after the 'ndirentry' lines dates? If so, they seem
> wayyyy too short to be nsavetime or epoch values. Otherwise, nothing
> that looks like a date except the very top of the output:
>
> scanning client `client1' for savetime 1297121469(Mon Feb  7 18:31:09
> 2011) from the backup namespace on server server1
>
> We're running 7.5.1 on RH Linux. I don't recall seeing dates in older
> releases either. Anyone else able to get a savetime out of this command?
>
> Thanks.
>
> George

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER