Hi, my name is Tammy Bednar from Oracle, over the next few minutes we will focus on Oracle Database Cloud Service the maximum availability architecture. In this lesson, we will take a look at the maximum availability architecture solutions for DV System, bare metal and virtual machines availability of data and applications is an important element of every IT strategy. At oracle we've used our decades of enterprise experience to develop an all encompassing framework that we call oracle MAA for maximum availability architecture. Oracle MAA starts with customer insights and expert recommendations these have been collected from our huge pool of customers and community of database architects, software engineers and database strategists. Over the years, this has helped the or MAA development team to develop a deep and complete understanding of various kinds of events that can affect availability through this, they have developed an array of availability reference architectures. These reference architecture acknowledged that not all data or applications require the same protection and that there are trade offs in terms of cost and effort. Whatever your availability gilles maybe for a database or related applications, Oracle has the product functionality and guidance to ensure you can make the right decision with full knowledge of the trade offs in terms of downtime and potential data loss and cost. These reference architectures use a wide variety of AJ features, configurations and operational practices, they help our end customers primarily achieve four goals. Data protection, that's reducing data laws through flashback and back up, active replication which allows customers to connect their applications to replicated sites and an active active HA solution through active data guard and golden gate. Scale out, which allows customers the ability to scale compute notes, lean early through rack and ASM and finally continuous availability which allows transparent fail over of services across distributed locally or remote through active data guard and global data services. These features and solutions allow customers to mitigate not only planned events such as software upgrades, data schema changes in patching but also unplanned events such as hardware failures and software crashes due to bugs. The insights recommendations Reference architecture is features configurations, best practices and deployment choices combined to form a holistic blueprint which allows customers to successfully achieve their high availability goals. Over the next few minutes we will take a look at the MAA options that can be used with the Oracle database Cloud services, bare metal and virtual machine. Database cloud services, bare metal uses standard intel compute with AVMA with storage management of ASM using normal or high redundancy. Since bare metal is a single mode, there is no local HA without rap therefore, data guard is strongly recommended. Let's take a look at MAA architecture for bare metal. This chart is an overview of the MAA products and features that can be used with database Cloud services Bare metal. Flashback can be used with flashback query which allows the content of a table to be queried with references to a specific point in time, backup and recovery is a standard solution that all databases should implement if you have the need to recover data. Data guard and activate data guard can be implemented for DR solution as well as the ability to offload reporting processing or fail over in case there is a primary database failure. Finally, application continuity can be used with enterprise edition, extreme performance edition since it does require the active data guard license. A single instance in cell already contains good protection from some failures, if's acid compliance the redo log protection, it's intrinsic robustness is basic protection, online reorganization allows online table redefinition without impact to the application. Resource management protects against runaway statements or host resource saturation. For example, instance caging, flashback query, transaction table and database protect against wrong transactions from users, developers or DBAAs. RMAN is the recommended backup tool which gives high manageability and protection against data loss, storage failures etc. A list of guidance is to use data guard with bare metal in the OCI console. One note on data guard set up data OCI console is that you must select another bare metal service and they must be in the same compartment. Any changes made with manual management accept changes in the protection mode may break the synchronization with the OCI console. If you would like to set up a data guard stand by on a different type of service. For example, bare metal production with virtual machines stand by you can accomplish this using the oracle tools for data guard you use on premise or we refer to this as manual setup. Any changes made in manual management, accept changes in the protection mode break the synchronization with the control playing. In summary, here are a list of best practices to set up data guard with database called services Bare metal. You should always use grid infrastructure storage management ASM for data guard environments and always use custom application services. From a network perspective, you should only use VCN connectivity and not a public network and finally put the FSFO observer with the applications or in a third region. The DVBs cloud service version machines use standard intel compute with block storage the block storage is triple mirrored automatically and you can use either LVM or ASM or grid infrastructure for storage management, rack nodes use different fault domains per node. This table is a quick reference to the MAA components and the availability on the VM services which include flashback that govern recovery, multi tenant rack and data guard. Application continuity can be used but it is an enterprise edition enterprise performance feature because it does require active data guard or and or rap for single no VM out of the box protection includes RMAN or backups. Backups can be enabled in the OCI console for your DB system out of the box with backups you can achieve MAA level bronze, active DA Guard can be set up in the OCI console or you can use DBaas API golden gate can also be manually configured. For out of the box MAA level, silver and gold you can provision a to know BM and enable rack an active data guard. If you take a look at the out of the box outage matrix, you will see for planned maintenance it's zero database downtime, rack provides for rolling applications of patches. For upgrades the RTO is currently hours as data guard does not roll the upgrades with this MAA implementation recoverable and unrecoverable failures can be resolved in minutes. This chart is a quick overview on how to set up data guard via the OCI console, Asynchronous protection mode provides MAX performance between the primary and standby databases. To keep the databases in sync during role changes use the OCI console if a fail over was used in a role change, you can use a reinstate option to rebuild the standby database. You can almost configure data guard manually with virtual machines or other services types such as bare metal or exudated data, cloud service. This chart guide you on the task that should be executed during each phase as a best practice you should always use great infrastructure storage management or ASM for data guard environments. Data Guard is supported on LVN, but it lacks ONS server control and requires static listener entries, to keep product and standby databases stacks the same, it is recommended to use the custom DB software images also, you should put the FSFO observer with the applications or in a third region. In this lesson, we have covered the maximum availability reference architecture for database, cloud service, bare metal and virtual machines.
