As far as I'm told by IBM, it is fixed with client 3.1.0.6, I will check
this the next days (It has to go thru sw distribution...)
Regards
Roger
Joseph A Faracchio schrieb:
> A user of mine has discovered this problem as well and wants to know if
> its fixed and in what lever/update.
>
> ... joe.f.
>
> On Thu, 8 Apr 1999 16:02:50 +0200 you said:
> >Does anyone know if this problem is fixed with client 3.1.0.6? I have
> >similar problems with Client 3.1.0.3
> >
> >Regards
> >
> >Roger Hohmann
> >
> >====================================================
> >>Tom,
> >
> >> I too, have seen something similar to what you describe. I too am
> >using
> >> a V3 server and backup a Solaris 2.5.1 system. In my context, I am
> >> using the VIRTUALMOUNTPOINT option to limit ADSM backups to just
> >> /export/home. I see the same results of your tests with selective
> >and
> >> incremental. All directories of /export/home get backed up EXCEPT
> >> /export/home/joe. I went back to the Version 2 client level and
> >> everything works okay. I have a PMR open with IBM on this and am
> >> waiting for their response.
> >
> > > ----------
> > > From: Fluker, Tom R[SMTP:Tom.Fluker AT viasystems DOT com]
> > > Sent: Tuesday, February 10, 1998 2:25 PM
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Subject: Strange ADSM behavior with Solaris
> > >
> > > I'm running V3 ADSM client on a Solaris 2.5.1 machine. I have a
> > > number
> > > of file systems mounted on this machine that are also auto-mapped
> > > (using
> > > auto.direct files) as "home" directories for users. As a result a
> > > directory in the original file system (/export/home/joe) may also
> >get
> > > "automounted" as /home/joe for user joe.
> > >
> > > I have added a entry to the exclude file to exclude backup of
> > > "/home/.../*" to eliminate two backups of the same file.
> > > There are no excludes for the /export/home directories.
> > >
> > > My problem, and it seems related to this automounter thing, is that
> > > /export/home/joe is not backed up by ADSM incremental backups.
> > >
> > > Further....
> > > dsmc selective '/export/home/joe/*' -subdir=yes -verbose -- seems
> > > to
> > > work
> > > dsmc incr /export/home -verbose -- seems
> > > to
> > > expire all the files
> > > backed
> > > up
> > > with selective backup
> > >
> > > dsmc incr '/export/home/joe/*' -verbose -- seems to work
> > > dsmc incr /export/home -verbose -- seems to expire files
> > >
> > > It's my understanding that the scheduled backup is like the "dsmc
> > > incr"
> > > and it seems to result only in the expiration of anything I have
> > > managed
> > > to backup using the command line..
> > >
> > > Any ideas??
> > >
> > > Tom Fluker
> > > tom.fluker AT viasystems DOT com
--
Roger Hohmann
Roger Hohmann
WestLB
Division: 009 Services
Abteilung 001-80622
Herzogstra_e 15
D - 40217 D|sseldorf
Tel.: +49 211 826 8155
Fax : +49 211 826 5393
mailto: Roger_Hohmann AT westlb DOT de
|
