RE: Some Dataguard is good, lots more must be better?

  • From: "Laimutis Nedzinskas" <Laimutis.Nedzinskas@xxxxxxxxxxxxx>
  • To: <oracle-l@xxxxxxxxxxxxx>
  • Date: Tue, 19 Sep 2006 17:54:54 -0000

>One of our accounts has over 80 databases that need DR and I must say
that in my mind chewing on crushed glass would bring more pleasure than
trying to deal with 80 primary/standby DG relationships... It just seems
to me that at some number of databases, the only humanly possible way to
get DR would be at the storage level... thoughts ?

Well, once standby is set then it just runs provided stupid things are
not beeing done. One thing to watch however is to upgrade archive log
deletion procedures so that archive logs are deleted only when they are
no longer needed by *both* backup procedures and standby. I am not
really sure if Oracle 10g finally automated this task. 

To sum up:
- the biggest work you have to do is to create standby for each one of
80 primaries. This can be automated to some level but even if you are
going to use OEM it is going to be at least 80xN mouse clicks.
- you have to rebuild standby after primary is upgraded/patched. This is
not a big work work compared to the upgrade process itself, some extra
10% may be. 
- rebuilding standby after failover: this can be mostly automated. Even
DG should be able to do this actually.

What you get: 
- the posibility to lag behind the primary (which violates data
protection however)
- independancy from the System Administrator and platform he
administrates




 

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Kevin Closson
Sent: 19. september 2006 17:36
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: Some Dataguard is good, lots more must be better?

 >>>alternative DR solutions. For people that do care about near 
>>>continuous availability DG is really quite cheap - even if you didn't

>>>buy EE and is (reasonably) easy to manage. It helps that it is a 
>>>somewhat old and reliable technology as well.

...the thread I started was about the practicality of using DG for a lot
of databases.  Maybe there is nobody on list that has more than, say, 10
database that need DR, but does the comment "(reasonably) easy to
manage" hold fast if we are talking about providing DR for, say, 10 or
20 databases?

One of our accounts has over 80 databases that need DR and I must say
that in my mind chewing on crushed glass would bring more pleasure than
trying to deal with 80 primary/standby DG relationships... It just seems
to me that at some number of databases, the only humanly possible way to
get DR would be at the storage level... thoughts ?

--
//www.freelists.org/webpage/oracle-l


Fyrirvari/Disclaimer
http://www.landsbanki.is/disclaimer
--
//www.freelists.org/webpage/oracle-l


Other related posts: