>From a recent pmr I had, here's the response from TSM support:
"I suspect that the
exclude.dir /xx/home
exclude.dir /xx/perflogs
are interpreted as to exclude the /xx/home and /xx/perflogs directories
from the root "/" file system. This is different than to exclude the
file systems themselves. If you want to exclude file systems /xx/home
and /xx/perflogs then use the exclude.fs. For example :
exclude.fs /xx/home
exclude.fs /xx/perflogs
It is better to use the exclude.fs when you want to exclude the whole
file system because the client will not scan the filesystem for matching
directory file specification as it does for an exclude.dir. In other
words, it offers better performance. So, try the exclude.fs and let me
know how it goes. Remember to re-start your client scheduler so that
change takes effect."
--so: My understanding is that if the thing we want to exclude is
a mountpoint for a file system, we should use:
exclude.fs /xx/yy (note no wildcarding)
If it's NOT a mountpoint, then we should use:
exclude.dir /xx/yy/.../* (wildcard at will)
This seems to be working for me now, as long as I keep an accurate
inventory of my client's filesystems (and periodically audit this and compare
it to the tsm file spaces!).
fun and games.....JRS
---------------------- Forwarded by John Snyder/CTF on 11/16/2000 10:15 AM
---------------------------
Palmadesso Jack<[EMAIL PROTECTED]>@[EMAIL PROTECTED]> on
11/16/2000 09:01:28 AM
Please respond to ADSM: Dist Stor Manager<[EMAIL PROTECTED]>@INTERNET
Sent by: ADSM: Dist Stor Manager<[EMAIL PROTECTED]>
To: ADSM-L<[EMAIL PROTECTED]>@INTERNET
cc:
Subject: Re: Anything wrong with this picture?
If you would like to exclude directories then use
exclude.dir
Jack
-----Original Message-----
From: Christo Heu?r [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 16, 2000 8:07 AM
To: [EMAIL PROTECTED]
Subject: Anything wrong with this picture?
Hi All,
I'm running the Tsm3.7.2.0 code on a Solaris machine and can not seem to get
certain files excluded from the backup process.
Here is the complete inclexcl file and the resultant backup - obviously only
the parts where it is actually sending the excluded files.
Does anyones excludes work on Solaris on this level?
Can anyone see what we are doing wrong here?
BTW the scheduler process was stopped and started...
Thanks
Christo
# more /etc/adsm/inclexcl.list
exclude /orabin/*
include /orabin/tet.txt
include /orabin/.kshrc
include /orabin/.profile
exclude /fsps01/*
exclude /fsps02/*
exclude /fsps03/*
exclude /gtps01/*
exclude /gtps02/*
exclude /gtps03/*
exclude /wcps01/*
exclude /wcps02/*
exclude /wcps03/*
exclude /usr/*
exclude /proc/*
exclude /dev/*
exclude /devices/*
exclude /etc/*
exclude /var/*
include /var/adm/*
exclude /tmp/*
exclude /opt/*
exclude /usr/openwin/*
#
---------------------
Normal File--> 20,463,616 /fsps02/control/ctrl02.dbf [Sent]
ANS1898I ***** Processed 93,000 files *****
Normal File--> 268,435,968 /fsps02/redolog1/fsps_redo_g2_p.dbf [Sent]
Normal File--> 525,352,960 /fsps02/sbslog/sbslog_01.dbf [Sent]
Normal File--> 525,352,960 /fsps02/sbslog/sbslog_02.dbf [Sent]
Normal File--> 525,352,960 /fsps02/sbslog/sbslog_03.dbf [Sent]
Normal File--> 525,352,960 /fsps02/sbstbl/sbstbl_01.dbf [Sent]
< 712.76 MB> [ - ]
