Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Men-deploy Oracle Data Guard di Solusi Bare Metal
Oracle® Data Guard adalah solusi ketersediaan tinggi dan pemulihan dari bencana (disaster recovery) untuk database Oracle.
Menyiapkannya di Solusi Bare Metal mengikuti praktik terbaik yang sama
seperti deployment Oracle Data Guard di infrastruktur lokal atau deployment lainnya.
Sebelum memulai
Panduan ini menjelaskan proses mengonfigurasi Oracle Data Guard di Solusi Bare Metal.
Hal ini berlaku untuk lingkungan Solusi Bare Metal yang menjalankan database Oracle versi 12.2 atau
yang lebih baru yang memenuhi kriteria berikut:
Setiap lingkungan berisi dua cluster Solusi Bare Metal
yang dikonfigurasi dalam ekstensi regional terpisah.
Database utama dan standby untuk Data Guard dihosting di ekstensi regional
Solusi Bare Metal yang terpisah.
Setiap cluster Solusi Bare Metal menggunakan opsi Oracle Real Application Clusters (RAC)
untuk ketersediaan tinggi.
Setiap cluster Solusi Bare Metal menggunakan Oracle Automatic Storage Management (ASM) untuk
penyimpanan bersama.
Nama diskgroup Oracle ASM konsisten di antara cluster.
Port TCP 1521 digunakan untuk komunikasi antara database utama dan cadangan.
Cluster Solusi Bare Metal pertama menghosting database utama Data Guard dan
cluster Solusi Bare Metal kedua menghosting database standby. Panduan ini menggunakan broker Data
Guard untuk mengelola konfigurasi. Panduan ini juga menyertakan petunjuk
untuk mengonfigurasi observer Data Guard secara opsional di Compute Engine. Dengan mengonfigurasi pengamat, Anda dapat mengonfigurasi failover database otomatis antara database utama dan standby.
Arsitektur sistem
Diagram berikut menunjukkan arsitektur sistem yang digunakan dalam panduan ini:
Setiap ekstensi regional berisi cluster Solusi Bare Metal yang berbeda. Database
utama, DBDG_SITE1, ada di ekstensi regional 1. Database
standby, DBDG_SITE2, ada di ekstensi regional
2 dan dibuat melalui duplikasi aktif. Komunikasi antara database tersebut
dilakukan melalui Partner Cloud Interconnect melalui Virtual Private Cloud
pelanggan bersama.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\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)."]]
