As with any issue like this, it would help to see the detail, such as the specific logs you are looking at, options file, server-side client option set (if you have it), etc.
One thing that stands out is that, in and of itself, your exclude.dir statement does not prevent the backup of files that reside in the root of the drive. If you want to exclude all files on a Windows drive with exclude.dir, here is what I recommend: exclude e:\* exclude.dir e:\* (note that you don't need the \... syntax). Alternatively, you can use: domain -e: This alternative is relatively simple, although this only affects domain incremental backups, i.e.: dsmc i Thus you can still do backups that explicitly target this drive, like this: dsmc i e: dsmc i e:\mydir\* -subdir=yes Using the excludes above will prevent *any* backup of the drive. Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 2006-04-27 16:19:17: > I have "exclude.dir e:\...\*" in a client config to prevent it from > backing up the e: drive. When I run BA client, select backup and local > filesystems and run estimate, it looks reasonable (the total cannot be > including e: drive). I am not now completely sure but I also think I did > run it by hand and it didn't backup e:. The backup started by the > existing association on the server seems to ignore at least this setting > in dsm.opt. What can be wrong? > > Thanks > > Michal
