Thanks Bertaut,

Both approached are valid and possible, but both have shortcomings.
In first case, if I choose to handpick the databases for backup, I
then need to be in constatnt check regarding introduction of new
production databases. This is like using 'DOMAIN C: D:' statement
instead of DOMAIN ALL-LOCAL in BA client.

In the second case, the exclude will be valid only limited  period of
time till the SQL admin removes old Test_XXX DB and creates another
one named Test_YYY.

I'm looking to wildcard exclude of all Test_* databases.

As I've mentioned,
exclude "\...\Test*\...\"
 doesn't seem to work.
--
Warm regards,
Michael Green



On Wed, Jul 29, 2009 at 3:59 PM, Tchuise,
Bertaut<BTchuise AT lmus.leggmason DOT com> wrote:
> Michael,
>
> You could try explicitly specifying the databases to backup on your sql
> server by listing them in your tdpfull and/or tdpincr/tdpdiff command
> files: tdpsqlc backup DB1,DB2,DB3 FULL /tsmoptfile=***.opt
> /logfile=*****.log; that way the test databases won't be included.
> Another option is to use of the /excludedb parameter: tdpsql backup *
> incr /excludedb=test1,test2,test3
>
> BERTAUT TCHUISE
> Storage Support Administrator
> Legg Mason Technology Services
> *410-580-7032
> BTchuise AT leggmason DOT com
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Michael Green
> Sent: Wednesday, July 29, 2009 2:20 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] TDP MSSQL excludes
>
> I've been requested by our MSSQL admin to exclude from backup any
> database with name that starts with 'Test' or 'TEST'. The admin often
> creates and removes databases with such names.
> I've tried to exclude using:
> exclude "\...\Test*\...\"
> exclude "\...\TEST*\...\"
>
> But it doesn't seem to do the job. Instead of ignoring these DBs like if
> they were not there, TDP skips over them producing errors along the way.
>
> How should such an exclude be formulated?
> --
> Warm regards,
> Michael Green
>
> IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason 
> therefore recommends that you do not send any confidential or sensitive 
> information to us via electronic mail, including social security numbers, 
> account numbers, or personal identification numbers. Delivery, and or timely 
> delivery of Internet mail is not guaranteed. Legg Mason therefore recommends 
> that you do not send time sensitive
> or action-oriented messages to us via electronic mail.
>
> This message is intended for the addressee only and may contain privileged or 
> confidential information. Unless you are the intended recipient, you may not 
> use, copy or disclose to anyone any information contained in this message. If 
> you have received this message in error, please notify the author by replying 
> to this message and then kindly delete the message. Thank you.
>