每个裸金属解决方案集群均使用 Oracle Real Application Clusters (RAC) 选项实现高可用性。
每个裸金属解决方案集群均使用 Oracle 存储空间自动管理 (ASM) 功能实现存储空间共享。
Oracle ASM 磁盘组名称在集群之间保持一致。
TCP 端口 1521 用于主数据库和备用数据库之间的通信。
第一个裸金属解决方案集群用于托管 Data Guard 主数据库，第二个裸金属解决方案集群用于托管备用数据库。本指南使用 Data Guard 代理来管理配置。本指南还包括有关如何在 Compute Engine 上选择性地配置 Data Guard 观测器的说明。通过配置观测器，您便可以在主数据库和备用数据库之间配置数据库自动故障切换。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[[["\u003cp\u003eOracle Data Guard, a high availability and disaster recovery solution for Oracle databases, can be deployed on Bare Metal Solution using the same best practices as other deployments.\u003c/p\u003e\n"],["\u003cp\u003eThis guide outlines how to configure Oracle Data Guard across two Bare Metal Solution clusters in separate regional extensions, communicating via a Google Virtual Private Cloud (VPC) and Partner Cloud Interconnect.\u003c/p\u003e\n"],["\u003cp\u003eThe setup assumes that Oracle Grid Infrastructure, Oracle database, and specific network configurations, like TCP port 1521, are already in place, along with consistent Oracle ASM diskgroup names.\u003c/p\u003e\n"],["\u003cp\u003eThe guide utilizes the Data Guard broker for configuration management and includes optional steps for configuring a Data Guard observer on Compute Engine to enable automatic database failover.\u003c/p\u003e\n"],["\u003cp\u003eCustomers are responsible for the licenses of the Oracle workloads that are being run and for their application's disaster recovery service level objectives.\u003c/p\u003e\n"]]],[],null,["# Deploy Oracle Data Guard on Bare Metal Solution\n===============================================\n\n[Oracle® Data Guard](https://www.oracle.com/database/technologies/high-availability/dataguard.html)\nis a high availability and disaster recovery solution for Oracle databases.\nSetting it up on Bare Metal Solution follows the same [best practices](https://www.oracle.com/database/technologies/active-data-guard-12c-best-practice.html)\nas on-premises or any other Oracle Data Guard deployment.\n| **Note:** Customers are responsible for procuring licenses for the Oracle workloads they choose to run on Bare Metal Solution, and customers are responsible for complying with those licenses. Google does not provide licenses for Oracle workloads.\n\nBefore you begin\n----------------\n\nThis guide explains the process of configuring Oracle Data Guard on Bare Metal Solution.\nIt applies to Bare Metal Solution environments running Oracle database version 12.2 or\nnewer that meet the following criteria:\n\n- Each environment contains two [Bare Metal Solution clusters](/bare-metal/docs/bms-setup) that are configured in separate regional extensions.\n- Each Bare Metal Solution cluster communicates through a Google [Virtual Private Cloud (VPC)](https://cloud.google.com/vpc) via a [Partner Cloud Interconnect](https://cloud.google.com/network-connectivity/docs/interconnect).\n- [Oracle Grid Infrastructure and Oracle database](https://docs.oracle.com/en/database/oracle/oracle-database/19/sbydb/oracle-data-guard-concepts.html#GUID-F78703FB-BD74-4F20-9971-8B37ACC40A65) are already installed on the Bare Metal Solution servers.\n- The primary and standby databases for Data Guard are hosted in separate Bare Metal Solution regional extensions.\n- Each Bare Metal Solution cluster uses Oracle Real Application Clusters (RAC) option for high availability.\n- Each Bare Metal Solution cluster uses Oracle Automatic Storage Management (ASM) for shared storage.\n- Oracle ASM diskgroup names are consistent between clusters.\n- TCP port 1521 is used for communication between the primary and standby databases.\n\nThe first Bare Metal Solution cluster hosts the Data Guard primary database and the\nsecond Bare Metal Solution cluster hosts the standby database. This guide uses the Data\nGuard broker to manage the configuration. This guide also includes instructions\nto optionally configure the Data Guard observer on Compute Engine. Configuring an\nobserver lets you configure automatic database failover between the primary and\nstandby databases.\n| **Important:** You are responsible for the disaster recovery service level objectives for your application.\n\nSystem architecture\n-------------------\n\nThe following diagram shows the system architecture used in this guide:\n\nEach regional extension contains a different Bare Metal Solution cluster. The primary\ndatabase, \u003cvar translate=\"no\"\u003eDBDG_SITE1\u003c/var\u003e, exists in regional extension 1. The\nstandby database, \u003cvar translate=\"no\"\u003eDBDG_SITE2\u003c/var\u003e, exists in regional\nextension 2 and is created via active duplication. Communication between the\ndatabases travels over the Partner Cloud Interconnect through a shared\ncustomer Virtual Private Cloud.\n\nNext steps\n----------\n\nNext, [prepare Data Guard's primary database](/bare-metal/docs/solutions/oracle/data-guard-setup/db-setup-primary)."]]
