I've tested a setup like the one Tim is describing.
We tested backuping with RMAN using incremental and
doing conventional hot backup. We were partitionned by
month and each partition was in its own tablespace.
Only the current month was active so the rest was in
read only mode.
Since volume was not too big , we were still able to
do a nice clean full backup during the weekends.
- Tim Gorman <Tim_at_SageLogix.com> a écrit : > The
short answer is that it becomes important to
> make use of the features of 1) range-partitioning,
> 2) read-only tablespaces, and 3) incremental backups
> with RMAN, and 4) a honking big tape library using
> media-management software.
>
> Range-partitioning allows tables and indexes to be
> spread across multiple tablespaces, usually by time.
> As data ages, inserts/updates/deletes tends to
> cease; it is usually the newest data that has
> insert/update/delete activity upon it.
>
> Therefore, as data ages, you can set the tablespace
> in which the partitions are located to read-only.
> As tablespaces are set to read-only, you can remove
> them from the regular backup list. It is important
> to take 2-3 additional backups for archival
> retention after setting to read-only, but the
> regularly scheduled backups can now ignore those
> tablespaces. Generally, I recommend partitioning
> according to your loading scheme (i.e. daily loads,
> thus daily partitions) and storing those partitions
> in tablespaces according to your scheme for setting
> them read-only (i.e. if setting read-only on a
> quarterly basis after aged 6 months, then create
> "quarterly" tablespaces to house all of the
> partitions from all partitioned objects in that
> quarter).
>
> The advantages of RMAN's incremental backup
> mechanisms should be obvious, but its usefulness
> depends on the nature of the application. At the
> very least, incremental backups will "supplement"
> the effects of the partitioning/read-only-tablespace
> scheme illustrated above. Using RMAN's incremental
> backup mechanism, at worst you would be getting the
> equivalent of a level-0 or "full" backup, if every
> block was modified during every backup cycle. I
> hope that would be an unlikely scenario, though...
> ----- Original Message -----
> From: Terrian, Tom
> To: Multiple recipients of list ORACLE-L
> Sent: Wednesday, May 08, 2002 9:38 AM
> Subject: How to backup a data warehouse?
>
>
> How do you guys backup your data warehouses? Our
> warehouse is suppose to top out around 3.5TB. It
> seems that the traditional hot/cold backup methods
> will not be able to keep up. How do you guys do it?
>
>
>
> Thanks,
>
> Tom Terrian
>
>
>
>
>
>
Stéphane Paquette
DBA Oracle, consultant entrepôt de données
Oracle DBA, datawarehouse consultant
stephane_paquette_at_yahoo.com
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
Yahoo! Mail :
http://fr.mail.yahoo.com
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: =?iso-8859-1?q?paquette=20stephane?=
INET: stephane_paquette_at_yahoo.com
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (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).
Received on Wed May 08 2002 - 13:49:20 CDT
