Many thanks,

it works!!!

        Michael


On 22-Oct-98 Price, Robert R. wrote:
> There is an undocumented option to put into the dsm.sys file on 3.1.0.5 to
> skip one copy of the files.  Worked for me.
>
> Try:
>
>    TEST    SKIPLOFS
>
>> ----------
>> From:         Michael Stahlberg[SMTP:Michael.Stahlberg AT de.uu DOT net]
>> Sent:         Thursday, October 22, 1998 7:47 AM
>> To:   ADSM-L AT VM.MARIST DOT EDU
>> Subject:      Re: Fwd: adsm and loopback mounts
>>
>> Hi,
>>
>> On 21-Oct-98 Andrew Raibeck wrote:
>> > This sounds like it might be APAR IC20712. Try the latest
>> > client version, 3.1.0.5, which should fix this.
>>
>> That's right. We had the same problem a month ago. But now the directories
>> are
>> backuped two times!!! -((
>>
>> Regards,
>>
>>         Michael
>>
>> >
>> > 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.
>> >>
>>