For me ... the nice thing with DataGuard is customisable latency.
Because its rarely hardware etc nowadays that causes a "disaster"....its
that errant installation script that did
drop table THE_MOST_IMPORTANT_TABLE_IN_MY_COMPANY;
and it doesn't matter how many VM's you have floating around if you only
have 1 database :-)
So I can have 1 DG with 'zero' latency, 1 DG with 2hours latency, 1 with a
day etc etc etc...
On Wed, Jun 29, 2016 at 6:23 AM, Mark W. Farnham <mwf@xxxxxxxx> wrote:
365.25 * .01 = 3.6525 days. I think you're quoting for a few more 9's.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Stefan Koehler
Sent: Tuesday, June 28, 2016 4:11 PM
To: woody.mckay@xxxxxxxxx; ORACLE-L
Subject: Re: VM vs Data Guard for DB redundancy
Hey Woody,
well before going into any technical details, you need to define clearly
what your RPO and RTO is about. I mean you already mentioned an uptime of
99% and max downtime of 45 minutes, but in what scale? Per month? Per year?
Per week? Per day? With system maintenance windows or not? For example a
downtime of 99% per year is 5.256 minutes which does not really fit to your
45 minutes, but a downtime of 99% per day is 14,4 minutes which does not
really fit to your 45 minutes as well.
After you got these detailed requirements from the business owner, you
need to clarify RPO in detail ("You would lose in-flight, but that appears
to be acceptable" is not enough definition at all).
There may be also legal statements (e.g. like from BSI in Germany -
https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Hochverfuegbarkeit/BandB/B8_Datenbanken.pdf),
which clearly state that only a virtualization solution is not sufficient
for RDBMS HA, but this is country/environment dependent of course. You
should check this with your state and planned systems.
Be also aware that virtualization only catch host failures. You still have
to deal with logical and physical corruption (and detection) on RDBMS
level, which has to be set in relation to your defined RPO / RTO and
database size, etc..
Best Regards
Stefan Koehler
Freelance Oracle performance consultant and researcher
Homepage: http://www.soocs.de
Twitter: @OracleSK
Woody McKay <woody.mckay@xxxxxxxxx> hat am 28. Juni 2016 um 17:47geschrieben:
for a DB redundancy solution for 2,700 Oracle 12.1.0.2 databases on Linux.
Hi,
In a few days, I need to start investigating maintenance and viability
Currently, the 2,700 customers are in individual instances, but will belooking to put them into PDB's later this year.
thought is to bring up another VM and mount the original storage (san).
Leadership has told me that RAC is not an option to be considered.
Only Data Guard and VM with external storage. If the VM goes down, the
It's obvious what to do with Data Guard.
are doing.
I thought I'd check with the pros here to see what the rest of the best
is limited to 45 minutes or less.
What are the best options for DB redundancy? Considering
maintenance, cost and overall viability. Want to be up 99% and downtime
and mount the same storage - viola. No app fail-over or DNS change, etc.
The VM option sounds interesting. Just bring up a new VM on the same IP
Got just one DB cost. You would lose in-flight, but that appears to beacceptable.
--
Thoughts, pros/cons ? Other better solutions?
--
Sincerely,
WoodyMcKay
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
