Mark,

I have seen a similar behavior on my Sun 2.5.1 systems, too.  If yours are
like mine, there are some automounted NFS filesystems defined to local
drives.  Seems like ADSM will treat these as separate filesystems and
therefore back them up and expire the original file and all of the inactive
versions.  During subsequent backups, if the filesystem is not mounted, the
original files are backed up again.  Later, if the filesystem is mounted,
...  You get the idea.

I have gone around and around with IBM on this.  First they said that this
is how it should work, then they were convinced it was a bug.  It was
supposed to have been fixed in 3.1.0.7.  It wasn't.  The latest is that they
say that it cannot be fixed without breaking remote automounted filesystems.
It was working just fine with the Version 2 client.  What is an ADSM
Administrator to do?


> ----------
> From:         Mark Kimelheim[SMTP:Mark_Kimelheim AT SBPHRD DOT COM]
> Sent:         Tuesday, June 29, 1999 10:05 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      ADSM refusing to backup Solaris 2.5.1 filesystem
>
> We have ADSM client running on a Solaris 2.5.1 system.  There are a couple
> of file systems that ADSM refuses to backup.  If we try to back them up
> explicitly with "dsmc incr filesystemname", there are no errors logged, we
> get a "Successsful increment backup..." message, but no files are actually
> copied.
>
> If we backup a particular file within the file system using "dsmc incr
> pathname", the file does get copied.  However, if we then run a backup on
> the filesystem as a whole, the file just backed up gets expired, as if we
> had done an exclude on the path.
>
> Any ideas???
>
> Mark.
>