Thanks for the heads up.  I'll look into this tomorrow.

Sent from my HTC on the Now Network from Sprint!



----- Reply message -----
From: "Girish Jorapurkar" <giris...@yahoo.com>
Date: Wed, Feb 23, 2011 18:24
Subject: [Veritas-bu] using *.dbf in exclude lists
To: "Mark Glazerman" <mark.glazer...@spartech.com>, "Stafford, Geoff" 
<gstaff...@barclaycardus.com>, "veritas-bu@mailman.eng.auburn.edu" 
<veritas-bu@mailman.eng.auburn.edu>

Beware of the following bug in NB 7.0:

http://www.symantec.com/business/support/index?page=content&id=TECH135929



________________________________
From: Mark Glazerman <mark.glazer...@spartech.com>
To: "Stafford, Geoff" <gstaff...@barclaycardus.com>; 
veritas-bu@mailman.eng.auburn.edu
Sent: Wed, February 23, 2011 4:30:57 PM
Subject: Re: [Veritas-bu] using *.dbf in exclude lists

 
We exclude .dbf, .DBF, .arc and .redo files from our OS backups because RMAN 
handles all of those during the database backups.  No point in backing them up 
when they won’t be part of any OS restore.
 
Mark Glazerman
Desk: 314-889-8282
Cell: 618-520-3401
Pplease don't print this e-mail unless you really need to
 
From:veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Stafford, Geoff
Sent: Wednesday, February 23, 2011 3:59 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] using *.dbf in exclude lists
 
I’m hoping I can get a few peoples opinions on using *.dbf (or *.whatever) in 
exclude lists to avoid backing up Oracle (or whatever) database files.  I’ve 
always been of the opinion that excluding the directory where the database 
files 
are is a better method as it doesn’t require NBU to evaluate each and every 
file 
that it attempts to backup so you have less of a load on the client and, in 
theory, there might be an every so slight increase in backup speeds.  Our 
database environment, especially on the development/QA side, is very 
active/transient and new databases are popping up all the time on existing 
hosts 
resulting in backing up tons of tons of hot database files which are absolutely 
worthless.  Putting procedures around creating new databases requiring them to 
notify us when they create a new database is The Right Way to Do It™ but that’s 
easier said than done in a dev/qa world.  I’m starting to think that the time 
required to maintain the exclude lists is becoming more expensive than any 
performance benefits.
 
So, all ye great NBU minds, what are your experiences with using *.dbf and have 
you noticed any ill effects on the client?
 
 



_______________________________________________________

Barclays
www.barclaycardus.com
_______________________________________________________

This e-mail and any files transmitted with it may contain confidential and/or 
proprietary information. It is intended solely for the use of the individual or 
entity who is the intended recipient. Unauthorized use of this information is 
prohibited. If you have received this in error, please contact the sender by 
replying to this message and delete this material from any system it may be on. 



      
_______________________________________________
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Reply via email to