Re: set servername

2003-02-13 Thread Steve Roder
> >I am now wondering if TSM is confused, as /home used to be a filesystem, > >and now, /home/staff/tks/lps is on root. > > Get into the habit of putting braces {} around the filespace portion of > the path to make that unambiguous to TSM in servicing the query. Cool. That works. I looked around

Re: set servername

2003-02-13 Thread Halvorsen Geirr Gulbrand
bject: Re: set servername Hi, be carefull, we got severe password issues doing a servername change, we had to re-initialise all password on all clients (NT at least), René LAMBELET NESTEC SA GLOBE - Global Business Excellence Ce

Re: set servername

2003-02-13 Thread Richard Sims
>I am now wondering if TSM is confused, as /home used to be a filesystem, >and now, /home/staff/tks/lps is on root. Get into the habit of putting braces {} around the filespace portion of the path to make that unambiguous to TSM in servicing the query.

Re: set servername

2003-02-13 Thread Lambelet,Rene,VEVEY,GL-CSC
addressee and may contain information that is privileged and confidential. -Original Message- From: Steve Roder [mailto:[EMAIL PROTECTED]] Sent: Thursday,13. February 2003 02:26 To: [EMAIL PROTECTED] Subject: set servername Hi All, Can any damage be caused by changing this value

Re: set servername

2003-02-13 Thread Steve Roder
> >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 do

Re: set servername

2003-02-12 Thread Richard Sims
>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. ;

set servername

2003-02-12 Thread Steve Roder
Hi All, Can any damage be caused by changing this value? In other words, could it make a client unable to restore older versions of files? I have situtaion under solaris 2.9, TSM 5.1.5.0, where I can see the inactive versions in the DB via show version, but the client only shows a really ol