> >Can any damage be caused by changing this value?  In other words,
> >could it make a client unable to restore older versions of files? ...
> ...
> >sudo dsmc restore -se=lorenz -pick "/home/staff/tks/lps/Mail/myub" "/tmp/"
>
> No - the absence of the -INActive operand on the dsmc command line does that. 
>  ;-)
> Also, make sure your server date/time is correct and verify that the 
> -SErvername
> is selecting the right stanza in the client options file.

Sorry.  I cut-n-pasted the wrong line.  Even with -inactive, it is not
showing the other versions.  And yes, -se= is picking the correct stanza,
otherwise I sould not see anything.  The server time is fine, and the
machine is running ntp.

I am now wondering if TSM is confused, as /home used to be a filesystem,
and now, /home/staff/tks/lps is on root.

what I really find strange is that the file is brings up with a backup
date/time of 1/14/02 is not referenced at all in the "show version"
output.

...ah...now using the GUI, sure enough, dsmc is going after that path on
/home, rather than in root.  I don't know if this is a bug, or a
limitation of dsmc.  Pretty scary if collapsing filesystems back into root
can cause dsmc to give the wrong answer.

renaming the /home filespace to /home.old within TSM allows dsmc to find
the correct, active path to this data.

sudo dsmc restore -se=lorenz -pick -inactive "/home/staff/tks/lps/Mail/myub" 
"/tmp/"

TSM Scrollable PICK Window - Restore

     #    Backup Date/Time        File Size A/I  File

-----------------------------------------------------------------------
     1. | 02/12/03   21:14:49       6.35 MB  A //home/staff/tks/lps/Mail/my
     2. | 02/11/03   21:12:09       6.33 MB  I //home/staff/tks/lps/Mail/my
     3. | 02/10/03   21:14:45       6.30 MB  I //home/staff/tks/lps/Mail/my
     4. | 02/09/03   21:19:05       6.29 MB  I //home/staff/tks/lps/Mail/my
     5. | 02/07/03   21:13:32       6.28 MB  I //home/staff/tks/lps/Mail/my
     6. | 02/06/03   21:19:10       6.25 MB  I //home/staff/tks/lps/Mail/my
     7. | 02/05/03   21:11:28       6.25 MB  I //home/staff/tks/lps/Mail/my
     8. | 02/04/03   21:19:00       6.24 MB  I //home/staff/tks/lps/Mail/my
     9. | 02/03/03   21:10:58       6.24 MB  I //home/staff/tks/lps/Mail/my
    10. | 01/29/03   21:14:12       6.22 MB  I //home/staff/tks/lps/Mail/my
    11. | 01/28/03   21:10:40       6.22 MB  I //home/staff/tks/lps/Mail/my
    12. | 01/27/03   21:13:30       6.21 MB  I //home/staff/tks/lps/Mail/my
    13. | 01/24/03   21:19:50       6.18 MB  I //home/staff/tks/lps/Mail/my
    14. | 01/23/03   21:18:42       6.08 MB  I //home/staff/tks/lps/Mail/my

Ok...so now what is the significance of the "//"?

Renaming the filesystem back, and specifiying a filespec of
"//home/staff/tks/lps/Mail/myub"

Steve Roder, University at Buffalo
HOD Service Coordinator
VM Systems Programmer
UNIX Systems Administrator (Solaris and AIX)
TSM/ADSM Administrator
(spr AT buffalo DOT edu | (716)645-3564)