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 testing
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 of
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 one
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 go
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 can
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
|<Prev in Thread]
||[Next in Thread>
- include/exclude list,
Gill, Geoffrey L. <=