Exclude processing operates on files only, so the D: drive will still be
processed to back up the directory structure (minus the files). If you are
still seeing *files* getting backed up and this is a scheduled backup, you need
to stop and restart the client scheduler in order for the change to dsm.opt to
take effect.

As an alternative, if you want ADSM to ignore the D: drive altogether, then you
can add a domain statement to your dsm.opt file that includes all drives except
for D:. For instance, if you have a C:, D:, E:, and F: drive, the default
domain of ALL-LOCAL encompasses all four drives. But to exclude D:, you can add
this to dsm.opt:

DOMAIN C: E: F:

This will make ADSM look only at the C:, E:, and F: drives. The drawback with
this approach is that you have to remember to modify the domain list every time
you add or remove a drive to ensure that you are backing up the drives you
want. And don't forget to restart the scheduler after chaning dsm.opt.

Hope this helps,

Andy

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



ADSM-L AT VM.MARIST DOT EDU on 07/09/98 12:49:49 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Exclude of Drive D:


Most of our customers are still using the version 2 client, so I'm not real
familiar with the version 3 differences.  This customer wants to exclude
their D: drive from any backups.  We tried adding the following exclude
statement to the optiosn file:

EXCLUDE D:\...\*.*

But the D: drive is still backed up.  Do I have the format wrong or do we
have to do something different in version 3 to exclude this drive from
incremental backups?

Thanks for your help.