That is not my understanding of a selective backup.

You can set up a client schedule something like  below and it will back up the
filespaces specified,
and it will honour your includes/excludes in the dsm.opt

           Action
                                              SELECTIVE
                     Options
                                              -subdir=yes
                     Objects
                                              SYS:* DATA:*

From the Netware client manual and I believe other clients will behave in the
same way the following may prove useful

Understanding Which Files Are Backed Up:  When you request a selective
backup, TSM backs up a file if all of the following requirements are met:

   The file is not specified on an exclude statement in your
    include-exclude list. If you do not have an include-exclude list, all
    files are considered for backup.

   The selected management class contains a backup copy group.

   The file meets the serialization requirements defined in the backup
    copy group. If serialization is static or shared static, and the file
    is in use each timeTSM attempts to back it up, the file is not backed
    up.


For selective backups, TSM does not check frequency or mode, and does not
check to see whether a file has changed since it was last backed up. The
only criteria for selective backups are that the file is not excluded from
backup services and the management class associated with it has a backup
copy group.





"MC Matt Cooper (2838)" <matt.cooper AT amgreetings DOT com> on 03/13/2002 
12:28:16 PM

Please respond to "ADSM: Dist Stor Manager" <adsm-l AT vm.marist DOT edu>

To:   adsm-l AT vm.marist DOT edu
cc:    (bcc: John Naylor/HAV/SSE)
Subject:  Re: Monthly full backup



Robert,
             There really isn't a 'FULL' backup option in the client
scheduler.  There is the option of saying SELECTIVE and then you have to
list all the files that are to be backed up.  Meaning it isn't reading
through the INCLUDE/EXCLUDE list that you so painstakingly put together.
So what I do is I have my client backups spread out a little by POLICY and
start time.  Then every 2 weeks for some and monthly for others,  I run an
administrative schedule that updates the COPYMODE on the particular
POLICY/MANAGEMENT CLASS/COPYGROUP,  and ACTIVE the updated POLICY SET.  Then
when the backup runs the copygroup is set to ABSOLUTE.  This causes the FULL
backup to occur.  It is kind of a round about way of doing things but I
found no better way of getting the FULL backups to happen.  I run another
administrative schedule that sets the COPYMODE to MODIFIED an hour after the
backup starts.  The backup reads through this information when it starts so
you don't have to wait till all the backups in the schedule have finished to
switch it back.  This way I can have a portion of the servers in 1 POILICY
doing a FULL backup while other servers are doing an INCREMENTAL.
              I spread the client backups into different POLICYs and start
times so I can better control the amount of data that is going to the server
when I am doing the FULL backups.  I try to keep the client backup schedules
pretty much the same.  I have week day schedules and week end schedules.
But the administrative schedules are controlling whether or not any
particular schedule is doing a FULL.
Matt