Exclude "\...\*" in tdp sql gives warning/fails

[Geirr]

Hi everyone

I have a problem with TDP for SQL v. 5.5.5.1 (although same error in previous versions).

I have a SQL 2005 server, with quite a few databases on it, and would like to be able to include only two databases, and exclude the rest.
Incl/excl like this;

EXCLUDE "\...\*"
INCLUDE "\...\DB1\...\*"
INCLUDE "\...\DB2\...\*"

And then in my cmd file, use the command
tdpsqlc backup * log ---blahblah

When I do this, I get the following error (dsmerror.log for tdp), multiple times;
ANS1115W File '' excluded by Include/Exclude list

I have checked that the dsm.opt is correct (no funny characters, or runaway quotes etc), and that backups for the two wanted dbs finishes correct, but tsm reports schedule as failed. No other errors in dsmerror.log or windows event log.

The point of doing it this way, instead of, say, naming databases on the commandline (in .cmd), or using the /EXCLUDEDB option, is to avoid having to correct this every time a new database is added to the server. It wouldn't be so big a problem, if there wasn't 60+ databases on the server, and I only want to backup a handful. (However both workarounds do work.)

Has anyone seen this/corrected it? Any help will be much appreciated.

Thanks
Geirr G.

[tariq.kaifi]

Any include/exlude statements being forced from TSM server?

[Geirr]

Hi Tariq -
no optionsets or excludes from serverside.
I am thinking this could be a windows/mssql configuration issue, as there are som incl/excl in the OS (registry), that perhaps messes things up. (But I can't find it)
G

[tariq.kaifi]

Try in this order.

INCLUDE "\...\DB1\...\*"
INCLUDE "\...\DB2\...\*"
EXCLUDE "\...\*"

[Geirr]

Sorry, I've been out of the office tha last couple of days
Tried that, and nothing is backed up, and the warnings still appears in the error log.

I have had a PMR with IBM/Tivoli on this, and they suggest using one of the workarounds - looks like we are stuck with that. Oh well, it is not a disaster, just less automatic than we could hope.

Thanks for your time Tariq - much appreciated. I just don't think we should spend more time on this, as it is more a small annoyance, rather than a serious bug/error.

Regards
G

[tariq.kaifi]

I would like to hear IBM's say on this. Are they accepting it as a minor bug or something?

And yes, please do post the workarounds.

[tvbe39]

Same situation, with TDP SQL 5.5.5.1 and BA CLIENT 6.2.4.3.

Is there any workaround or patch?

thanks!