Did you check the schedule to see if something's being specified in the
overriding client options or the objects fields???

Tim Pittson
tpittson AT himail.hcc DOT com

>----------
>From:  Jerry Lawson[SMTP:jlawson AT ITTHARTFORD DOT COM]
>Sent:  Friday, May 10, 1996 2:16 PM
>To:    Multiple recipients of list ADSM-L
>Subject:       OS/2 Client Backup
>
>---------------------------- Forwarded with Changes
>---------------------------
>From: INTERNET.OWNERAD at SNADGATE
>Priority: Low
>Date: 5/10/96 10:20AM
>To: Jerry Lawson at TISDMAIL
>*To: *Multiple recipients of list ADSM-L at SNADGATE
>Subject: OS/2 Client Backup
>------------------------------------------------------------------------
>-------
>
>Todd -
>
>Your configuration sounds like my personal setup - a Thinkpad and Dock,
>each
>with a harddrive, although I have a total of 5 logical drives defined.
>I am
>running the same level of code, and it backs up all of the machine just
>fine.
>We also have many Notes servers, with 4 4G drives, and they also have
>no
>problems.  (I believe the drives are SCSI attached.)
>
>The only noticeable difference is the domain statement - we don't code
>it
>unless absolutely necessary - and it isn't here.  What you described
>should
>work - unless someone else has an idea, I'd suggest a call to the
>support
>center.
>
>Jerry Lawson
>jlawson AT itthartford DOT com
>________________________Forward Header________________________
>Author: INTERNET.OWNERAD
>Subject: OS/2 Client Backup
>05-10-96 10:20 AM
>
>Is there a problem running a scheduled backup for an OS/2 client with
>multiple
>fixed disks?  I have a Lotus Notes server that has an
> internal C and D fixed disk.  The DOMAIN C: D: is defined in the
>DSM.OPT file
>and when I manually run the DSMC Incremental process,
> both drives are backed up sucessfully, however, when the DSMC Schedule
>is
>used,
>
>only the C drive is backed-up.  The client in quest ion is running
>version 2
>release 1 level 0.3 code.  The server is still at version 1 level.
>
>Todd Mitchell
>Wagner & Brown, Ltd.
>