More Related Content Similar to From HA to Maximum Availability - A Holistic Historical Discussion (20) More from Markus Michalewicz (18) From HA to Maximum Availability - A Holistic Historical Discussion9. Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Fewest Layer Principle
• Each layer while perhaps helping to achieve HA has its own
potential for failure. Hence, the more layers, the more likely
a system can fail. Examples include, but are not limited to:
– Multipathing, (C)VM, OS (or vice versa), clusters, replication (if used)
• The problem gets worse in virtualized and cloud environments
in which “software defined”-hardware is used, especially when
allowing for dynamic re-configuration of these components, as
those also allow for human errors during (re-)configuration.
• Testing the system including all layers
as well as a good operations manual is mandatory therefore.
HA is best achieved using as little layers as possible
17. Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Edition-based Redefinition,
Online Redefinition, Data Guard, GoldenGate
– Minimal downtime maintenance, upgrades, migrations
Active Data Guard
– Data Protection, DR
– Query Offload
GoldenGate
– Active-active replication
– Heterogeneous
Active Standby Site
RMAN, Oracle Secure Backup,
Zero Data Loss Recovery Appliance
– Backup to disk, tape or cloud
Enterprise Manager Cloud Control
– Site Guard, Coordinated Site Failover
RAC / RAC One
– Scalability
– Server HA
ASM
– Local storage protection
Production Site
Flashback
– Human error
correction
Oracle Maximum Availability Architecture (MAA)
Application
Continuity
– Application HA
Global Data Services
– Service Failover / Load Balancing
Sharding
– Horizontal Partitioning,
Scalability, Shared Nothing
architecture
24. Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |
Online Patching Improvements
• OJVM patching will be RAC rolling
– Non-Java service available all time (at least one instance)
– Java service available all time, except ~10 sec brown-out
• No error reported during brown-out
• Zero Downtime GI Patching
– Patch Oracle Grid Infrastructure without interrupting database operations.
– Patches applied out-of-place and in a rolling fashion with one node being patched
at a time while the database instance(s) on that node remain up and running.
– Supported on clusters with two or more nodes.