Michal, Are you using partitioning, and if so, are there tablespaces you can set to read only?
If so, then you only need to back up the read only tablespaces often enough that your backup software retention time doesn't cause the RO TBS's to all be aged out. This could eliminate a lot of backup time/tape. Jared On Fri, 2003-10-24 at 16:34, Michael Kline wrote: > I'm working at a Data Warehouse and they are looking for backup > possibilities... > > This is almost a TB, a baby, and it may be that RMAN with incremental could > be a good solution. > > If say for instance there is a single tablespace of some 100 gig and they > add 200,000,000 records to one of the tables and we do an incremental > backup. Is the whole tablespace slated for backup? > > Also if this tablespace was lost, and we recover.. What happens during that > process? Does RMAN basically have to filter through two complete copies of > that tablespace or just once and then get changed blocks? > > What solutions have some doing this found to be "best practice"? > > Thanks. > > Michael Kline, Principal Consultant > Business To Business Solutions, LLC > Richmond, VA > 804-744-1545 > -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Jared Still INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
