That's exactly what we use to backup our 2.5TB ERP database. Yes, you do
have to put all tablespaces in backup mode for the split (couple of
minutes?).
It's a neat solution and keeps your database up all the time. But, your
pocket book is probably going to suffer with 3 copies of the 5TB database...
Other solution will be to use RMAN and do incremental backup.
Ying Gu
TDS Information Services
Senior Database Administrator
ying.[Email address protected]
Life is 10% what happen to you and 90% how you react to it
-----Original Message-----
From: Patterson Joel
[mailto:oracledba-ezmlmshield-x23437854.[Email address protected]
Sent: Wednesday, August 31, 2005 3:22 PM
To: LazyDBA Discussion
Subject: RE: Backup strategy....
Well, I'll pipe in in order to get some feedback also.
Spliting storage mirrors has always intriqued me. If money is not an
object, (and storage devices have come down a lot). (like a good SAN).
If you have a 3 way mirror. -- scenario.
You can break a mirror, and you still have redundancy. You backup up the
mirror, and take your time, hehe. Put the mirror back on and the OS
synchronizes it again. Cool.
Don't know the exact steps. You might have to put the tablespaces all in
backup mode first for as long as it takes to break the mirror, but the DB is
never down.
Comments?
-----Original Message-----
From: Kevin Hrim [mailto:oracledba-ezmlmshield-x63988291.[Email address
protected]
Sent: Wednesday, August 31, 2005 4:14 PM
To: LazyDBA Discussion
Subject: Re: Backup strategy....
The answer is going to depend on your application.
After the data is collected, is it updated?
If there are no updates, then a mix of partitioning
and read-only tablespaces could save on backups. This
also saves on recovery time as well because the
application can be made available quickly while the
read-only information is being restored in parallel.
Hot backups with RMAN and a good media management
layer are almost a necessity with the size and
complexity of this type of implementation.
Cold backups with a product that can split your
storage mirrors are a solution, but I wouldn't want to
do a 5TB cold backup unless I absolutely had to.
Kevin
--- Yves
<oracledba-ezmlmshield-x29164736.[Email address protected]
wrote:
> Gurus, we are planning the storage and backup
> requirement for a new system.
>
> The system will accumulate 5TB of data over a 4-5
> months period. Now my question is : What kind of
> backup strategy should we implement? The system can
> not be down for more than 1 day if
> Something happens. Should we do a mix of cold and
> hot backups or rely only of hot backup or something
> else?
>
> I've never been in charge of supporting such a large
> system, so any help would be appreciated.
>
> Merci / Thanks
> Yves Leonard,
> Chef de Projet / Project Leader,
> DDS / SDD,
> RH Coats, 13-I
> Téléphone / phone : 613-951-3233,
> couriel / email : yves.[Email address protected]
>
>
>
>
> --------
> website: http://www.LazyDBA.com
> Please don't reply to RTFM questions
> Oracle documentation is here:
> http://tahiti.oracle.com
> To unsubscribe: see
> http://www.lazydba.com/unsubscribe.html
> To subscribe: see http://www.lazydba.com
> By using this list you agree to these
> terms:http://www.lazydba.com/legal.html
>
>
--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html
--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html
Oracle LazyDBA home page