I don't know why you are having the overall problem, but there is also a
problem in your specification.
Periods are treated just like any other character, not a wild card.
So when you specify:
INCLUDE DATA:\USERS\...\*.*
you are telling TSM to match filenames that have at least one . in the name.
If you want to include everything, you need:
INCLUDE DATA:\USERS\...\*
-----Original Message-----
From: Mahesh Tailor [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 22, 2001 10:30 AM
To: [EMAIL PROTECTED]
Subject: Include/Exclude
I had posted this a few days ago, but I am not sure if anyone got it (my
Internet email gateway has not been behaving) . . .
Hello, all!
I have a clarification question about include/exclude statements. One of
our Netware guru's pointed this out to me. Here's what I have (NetWare 5)
in my dsm.opt file:
EXCLUDE *:\...\*.*
INCLUDE DATA:\USERS\...\*.*
When I perform an incremental backup of the node, the system backs up
everything on the system. If on the other had I do the following:
INCLUDE DATA:\USERS\...\*.*
EXCLUDE *:\...\*.*
The system does not backup anything except the files in the
data:\users\...\*.* directories.
It seems the system is doing just the opposite of what it's supposed to
since these statements are supposed to the processed from the bottom
statement up. [See excerpt from Tivoli Storage Manager for NetWare Using
the Backup-Archive Client manual.]
Excerpt:
These options are checked from the bottom of the include-exclude list up,
until a match is found. If a match is found, the processing stops and
checks whether the option is include or exclude. If the option is include,
the file is backed up. If the option is exclude, the file is not backed
up.
Has something changed? Can someone explain this?
TIA
Mahesh
