Re: include/exclude list
You are correct in that putting a file into the exclude list has the same
effect as if the file was deleted from the client. We took a similar
approach to Tom, but instead of excluding the oracle files and archiving
them, we dynamically build dsm.opt file for the daily backups that only
include filesystems that are NOT oracle table space filesystems. For our
approach to work, we have to be pretty rigid in our filesystem structure:
The filesystems that contain oracle table spaces can ONLY contain oracle
table spaces and control files. We have a naming policy that requires
those filesystems to be "/.../oracle/.../data/.../". In fact, since we
implemented it we have tightened it even more and all oracle table spaces
are under the /oracle/data filesystem. Each instance has its own directory
under that filesystem. This approach allows us to use backup for
everything rather than archive.
"Thomas A. La Porte"
WORKS.COM> To: ADSM-L AT VM.MARIST DOT EDU
cc: (bcc: Robin Sharpe/WA/USR/SHG)
11/16/01 11:23 AM Subject:
Please respond to Re: include/exclude list
"ADSM: Dist Stor
What we do is exclude the Oracle database files from backups,
then our nightly hot and weekly cold Oracle "backups" use the
archive function of TSM. We set up a separate Oracle management
class and that archive copy group has very different retention
policies than the rest of the management classes (30 versions
retained for 30 days). As part of our TSM bootstrap process on
the clients, we log in to any local Oracle databases and
dynamically build a list of files to be excluded for that node.
Thomas A. La Porte
tlaporte AT anim.dreamworks DOT com
On Fri, 16 Nov 2001, Gill, Geoffrey L. wrote:
>Will someone please explain the pitfalls of changing the include/exclude
>list as it relates to this issue. We have a server that is running Oracle.
>There is no TDP for True64 so we're stuck with what we have, the client.
>Backing up open Oracle files is a waste of time because we know from
>restores they are no good. I've suggested to the admins to exclude those
>open files from nightly backups because of this. We're talking about
>60-70GB. This times 21, the number of versions they have for me is a lot
>I'd like to know if my understanding is correct. If a file is not in the
>exclude list then it's backed up, that's an easy one. If it's changed
>nightly and been backed up for 3 weeks I have 21 copies. If I now exclude
>the file it's not backed up any longer, however what happens to the 21
>copies I have in place? Are they all expired immediately except the last
>and removed from the system?
>The problem is we "would" be stopping the database on weekends and getting
>good backups. If editing the exclude list would force the good copies to
>away then we could not live with that. If there is a way to exclude them
>some days and then include them other days and still keep 21 good copies
>then would someone please help me to accomplish this. I'm to the point I
>use all the free space I can, got about 20 clients that need backups but I
>don't have the space yet.
>Thanks for the help.
>NT Systems Support Engineer
>E-Mail: gillg AT saic DOT com
>Phone: (858) 826-4062
>Pager: (888) 997-9614