Re: How are you backing up your V,VLDB????

I think the most significant strategic point is that a database of this sort is almost always susceptible to partitioning, with a date-based partition. So a large fraction of the database can be put into read-only tablespaces.

if you are in this position, the backup
strategy consists of making sure you have a library of the read-only components, and the daily/weekly backup of changing data turns back into a large but viable volume.

--
Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

Coming soon a new one-day tutorial:
Cost Based Optimisation
(see http://www.jlcomp.demon.co.uk/tutorial.html )

____UK_______March 19th
____USA_(FL)_May 2nd


Next Seminar dates:
(see http://www.jlcomp.demon.co.uk/seminar.html )

____USA_(CA, TX)_August


The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html


Brian Peasland wrote in message <3E385635.98F2E945_at_peasland.com>...


>I am looking to see what solutions people are employing to backup

their


>very, very large database. We have a 1TB database (Oracle 9.2.0 on

Sun


>Solaris 8) that will grow to 6TB in the next five to six months. Our

>current backup solution uses RMAN, Legato, the Legato Oracle Module,

and


>a StorageTek automated tape library system. My real problem comes in

the


>next year or two. While I can envision our current architecture

handling


>the 6TB database, I am concerned with the next step of our growth. In

>the next year or two, we will be looking at growing to around 50TB. I

>don't think that our current architecture can handle that kind of

volume


>on a regular basis. So I'm wondering what others are doing to backup

>their V,VLDB. A 1-6TB db is no problem. But what about 30TB? 40TB? or

>even 100TB?

>

>Any thoughts that you'd like to share?

>

>Thanks in advance,

>Brian

>oracle_dba_at_peasland.com

>