AIX handles automounts similarly but with the temporary mount point
/tmp_mnt/home/fred for Fred's home file system that looks (to Fred) like
/home/fred.  Since the /tmp_mnt/home/fred must exist for Fred to see his
home directory, it makes sense that ADSM is backing up both, though is
not productive in this case.  Probably no way around it until ADSM is
scripted to handle the automount "staging area", unless you just exlude
that directory.  Should be a one-liner in the opt file (exclude
/home/.../*, or just exclude /home if your subdir option is set to yes).

Have you condsidered backing up the automounted directories on only the
boxes that hold the local data and excluding these directories on the
automount clients?

Just my $0.02.

Hilary Whitehead
IBM Global Services

> -----Original Message-----
> From: Gavin Ring [SMTP:Gavin.Ring AT ALCATEL.COM DOT AU]
> Sent: Wednesday, June 17, 1998 9:40 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      ADSM backing up the same data twice
>
> There was a thread a while back where the Solaris ADSM v3 client was
> skipping directories during incremental backups.
>
> The problem is described in APAR IC20712 and APAR IC20907. A new
> version of
> the client code (IP21297T2) was made available for download from the
> IBM
> FTP server.
>
> I have installed the new code and it does fix the problem of ADSM
> skipping
> directories, however I have found a significant change in the way the
> V3
> client works compared with the way the V2 client works.
>
> In summary the ADSM v3 client can backup the same data TWICE.
>
> For example.... we are using the automounter to mount home directories
> onto
> the /home mount point.
>
> I am seeing ADSM backup the /export/home1/x directory AND the /home/x
> directory.
>
> I was expecting ADSM to backup only /export/home1/ not the mount point
> /home/x
>
> This is the response from IBM......quote
>
>  -----FS-------+dir++-file-
>  /export/home1/uXXXX/fileXX
>  .
>  -----FS-----+file+
>  /home/uXXXX/fileXX
>  .
>  /home/uXXXX is pointing to /export/home1/uXXXX similar to a symbolic
>  link (without the option FOLLOWSYMBOLIC=NO) as a filesystem of type
>  LOFS. Now when ADSM is doing it's incremental it doesn't detect the
>  LOFS filesystem type and thus is backing up the files from both
> filesystems it finds. This is a known restriction with this situation
> (since version 2 already) and there are plans by another customer to
> open a DCR on that.
>
> .....unquote
>
> I do not know if this problem is a SUN solaris problem only or if it
> works
> in this way on other unix platforms. IBM are saying that it is working
> as
> designed and to open a data change request (DCR)
>
> Our environment is
>
> ADSM server O/S:    OS/390 2.4
> ADSM server:        ADSM for MVS 2.1.0.13
> ADSM client O/S:    Sun Solaris 2.5.1
> ADSM client:        3.1.0.3
>
> Regards
>
> Gavin