Michael,
 
I hope you have the tables partitioned on some date column. You can make some of the older partitions read only and back them up only once.
 
Another solution is to exchange the partitions with a table to convert your old partitions to tables, transporting them to a tape and keep it on the tape. If the database crashed, you will plug these TSs back to the DB and exchange the partitions with the tables created earlier.
 
I presented a session at Oracle World this year describing a case study of a datawarehouse where I have described the backup and recovery approach. You can download it from OTN or from my website (www.proligence.com/downloads.html). Be sure to download both the paper and the presentation.
 
HTH.
 
Arup Nanda
----- Original Message -----
Sent: Friday, October 24, 2003 7:34 PM
Subject: RMAN Incremental

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

Reply via email to