You not only need separate opt files, you need 2 node names.
If one backup runs with an include for .pst and the next backup has an
exclude for .pst, all the .pst files will be expired.



On Wed, Feb 4, 2009 at 11:48 AM, Shawn Drew <
shawn.drew AT americas.bnpparibas DOT com> wrote:

> Unfortunately, you can't use wildcards in the "objects" field.  You need
> to specify exactly what you are backing up.
> For what you want, I would recommend using include/exclude options in
> separate .opt files
>
> Another option is to do some hacking in a preschedcmd script.
>
>
>
> Regards,
> Shawn
> ________________________________________________
> Shawn Drew
>
>
>
>
>
> Internet
> brett.whitlock AT COUNTRYFINANCIAL DOT COM
>
> Sent by: ADSM-L AT VM.MARIST DOT EDU
> 02/04/2009 11:29 AM
> Please respond to
> ADSM-L AT VM.MARIST DOT EDU
>
>
> To
> ADSM-L
> cc
>
> Subject
> [ADSM-L] syntax question
>
>
>
>
>
> Hi List,
>
> Server TSM 5.4 on Windows
> Client 5.5 on Windows
>
> Here's what I'm trying to do.  Run 1 incremental on a file server with
> all .pst files excluded.  Then, run a separate incremental with only the
> .pst files.
> I have  c: e: and f: drives
>
> Description      ONLY for backing up .PST's on file server
> Action   INCREMENTAL
> Options  -subdir=yes -include *:\...\*.pst
> Objects  C:\*.pst E:\*.pst F:\*.pst
>
>
> sched.log reports:
>
> 02/03/2009 23:51:27 ANS1389W Invalid option (-INCLUDE) for the scheduled
> INCREMENTAL command
> 02/03/2009 23:51:27 --- SCHEDULEREC OBJECT BEGIN MMA_DAILY_PST_BACKUP
> 02/03/2009 23:00:00
> 02/03/2009 23:51:27 ANS1149E No domain is available for incremental
> backup. The domain may be empty or all file systems in the domain are
> excluded.
> 02/03/2009 23:51:27 ANS5083E Drive specification contains wildcard
> character.
>
> Can someone point me in the right direction?
>
> Thanks,
> Brett
>
>
> This message and any attachments (the "message") is intended solely for
> the addressees and is confidential. If you receive this message in error,
> please delete it and immediately notify the sender. Any use not in accord
> with its purpose, any dissemination or disclosure, either whole or partial,
> is prohibited except formal approval. The internet can not guarantee the
> integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
> not therefore be liable for the message if modified. Please note that
> certain
> functions and services for BNP Paribas may be performed by BNP Paribas RCC,
> Inc.
>