This sounds like it might be APAR IC20712. Try the latest
client version, 3.1.0.5, which should fix this.

Regards,

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com

>we are running adsm client Version 3, Release 1, Level 0.3, on Solaris
>5.6, and server Version 3, Release 1, Level 1.5, on AIX-RS/6000.
>
>adsm does not back up in any way filesystems that are of type "lofs"
>(that is, loopback mounts).  to give a specific example, we have a
>partition mounted as "/disk/2/eos".  this is loopbacked to a mount
>point called "/projects/eos".  adsm does not back up any files in this
>partition.  we have checked under both the non-loopbacked name
>(/disk/2/eos/*) and the loopbacked name (/projects/eos/*); and in both
>cases, the adsm client tells us "No files matching search criteria
>were found".  lofs partitions are treated as if they don't exist.
>
>our questions are:  is there a version of the client/server that will
>back up loopback mounted filesystems; or is it possible to force adsm
>to back them up?
>
>we did try doing a selective backup, specifying our loopbacked
>filesystems, but after the next incremental ran, those selective
>backups disappeared from adsm's filespace; it was as if it had never
>been backed up at all.
>