One of my users lost 6 months of work because the adsm backups
(version 3) was not working correctly on his linux redhat 7.1
system but not giving any errors.  Since that happened, I
have discovered at least 3 other systems, configured exactly
the same way, that are not working correctly.

What I have observed is

1.  install backup software and initially back up system - everything
works.
2.  next backup - directory in /home gets marked inactive.
3.  never backed up again.

Similarities - all machines are set up as follows

/boot
/
/home

And under /home is a machine_name directory.  For example if the machine
is yyy, then there is /home/yyy/ and /home/yyy/user.  All machines run NIS and
automount.  In /etc/auto.master are the lines

/misc   /etc/auto.misc  --timeout=60
/n      yp:auto.map     -rw,intr

And in the master auto.map file is the line

yyy     options         yyy:/home/yyy

and then the user's home dir in /etc/passwd is /n/yyy

I set this up on solaris, hpux, irix, redhat6.2 and everything
works fine.  Now on 7.1 (a supposedly supported system), the
client machine backs up the filesystem once and then marks it
inactive and never backs it up again.  Hence 6 months of work
down the tubes.

The only difference I can find on my 7.1 machines is an extra line
in /etc/mtab that looks like

/home/yyy /n/yyy none rw,bind 0 0

Is this the culprit?  Is adsm/tivoli unable to deal with this?
Or have I missed something?  If this really is a bug, how do I
get a fix?

Thanks in advance

Patricia Max
Los Alamos National Laboratory