Content deleted Content added
Flag as containing how-to content |
m Disambiguating links to Disaster recovery (link changed to IT disaster recovery) using DisamAssist. |
||
| (116 intermediate revisions by 64 users not shown) | |||
Line 1:
The software which [[Oracle Corporation]] markets as '''Oracle Data Guard''' forms an extension to the [[Oracle Database|Oracle relational database management system]] (RDBMS). It aids in establishing and maintaining secondary standby databases as alternative/supplementary repositories to production primary databases.
Oracle provides both [[graphical user interface]] (GUI) and [[command line interface|command-line]] (CLI) tools for managing Data Guard configurations.
Data Guard supports both '''physical standby''' and '''logical standby''' sites. Oracle Corporation makes Data Guard available only as a [[product bundling|bundled]] feature included within its "Enterprise Edition" of the [[Oracle RDBMS]].<ref>http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/standby.htm#insertedID3 ''Data Guard Concepts and Administration'', 11g Release 1 (11.1); Section 2.3.2: "Oracle Software Requirements" Retrieved 2007-10-01</ref>
With appropriately set-up Data Guard operations, [[database administrator|DBA]]s can facilitate [[failover]]s or [[switchover]]s to alternative hosts in the same or alternative locations.
Line 11 ⟶ 9:
== Configurations ==
For the purposes of Data Guard, each Oracle database functions either in a primary database role or in a standby database role - with the ability to transition from one role to the other.<ref>{{cite book|url=http://docs.oracle.com/cd/E11882_01/server.112/e41134/concepts.htm#i1033808|title=Oracle Data Guard Concepts and Administration 11g Release 2 (11.2)|last=Rich|first=Kathy|display-authors=etal|access-date=8 Mar 2017}}
</ref>
=== Physical standby (Redo Apply) ===
A physical standby database replicates the exact contents of its primary database across the [[Oracle Net]] [[network layer]]. While the relative physical storage locations can differ, the data in the database will be exactly the same as in the primary database. Physical standby databases can function either in managed-recovery mode or in read-only mode, but not in both modes at the same time (unless the databases are at Oracle Database 11.1 or higher and the Active Data Guard option is licensed - see below). The standby makes use of "Redo Apply" technology.
Physical standby databases have the same DBID identifiers as their primary equivalents.<ref>
{{cite book
|last1= Tchoko
|first1= Floribert
|title= Oracle: Protect Your Data
|url= https://books.google.com/books?id=1Py_soo_3pkC
|publisher= AuthorHouse
|publication-date= 2012
|page= 128
|isbn= 9781467896214
|access-date= 2015-03-17
|quote= [...] a new identifier DBID is assigned to the new database unless the database is a standby database. In this case it retains the same DBID as the source database.
}}
</ref>
=== Logical standby (SQL Apply) ===
Logical standby databases convert the redo generated at the primary database into data and SQL and then re-apply those SQL transactions on the logical standby. Thus, physical structures and organization will be different from the primary database. Users can read from logical standby databases while the changes are being applied and, if the GUARD is set to STANDBY (ALTER DATABASE GUARD STANDBY;), write to tables in the logical standby database that are not being maintained by SQL Apply.
Unfortunately there are a number of '''unsupported objects''' (e.g. tables or sequences owned by SYS, tables that use table compression, tables that underlie a materialized view or Global temporary tables (GTTs)) and '''unsupported data types''' (i.e.: datatypes BFILE, ROWID, and UROWID, user-defined TYPEs, multimedia data types like Oracle Spatial, ORDDICOM, and Oracle Text Collections (e.g. nested tables, VARRAYs), SecureFile LOBs, OBJECT RELATIONAL XMLTypes and BINARY XML).<ref>
{{cite web
| url = http://www.databasejournal.com/features/oracle/article.php/3860251/Leveraging-Logical-Standby-Databases-in-Oracle-11g-Data-Guard.htm
| title = Leveraging Logical Standby Databases in Oracle 11g Data Guard
| access-date = 2010-07-16
| last = Czuprynski
| first = Jim
|date=January 2010
}}</ref> Logical standby may not be appropriate in such a case.
=== Active Data Guard ===
The "Oracle Active Data Guard" option, an extra-cost facility,<ref name="Oracle Database Options">
{{cite web
| first = Diana
| last = Lorentz
| title = Oracle Database Options
| url = http://download.oracle.com/docs/cd/B28359_01/license.111/b28287/options.htm#sthref21
| work = Oracle Database Licensing Information 11g Release 1 (12c)
| publisher = Oracle Corporation
| date = January 2009
| access-date = 2009-04-22
| quote = If a physical standby database in a Data Guard configuration has any of the above features enabled, then the Active Data Guard option must be licensed for every such physical standby, and also for the primary database.
}}</ref> extends Oracle Data Guard functionality in Oracle 11g configurations. It allows read-only access on the Physical standby node at the same time as applying archived transactions from the primary node. Also it features Automatic Block Repair and Fast Incremental Backup on Physical Standby,<ref name="Oracle Active data Guard">
{{cite web
| title = Oracle Active data Guard
| url = http://www.oracle.com/database/active-data-guard.html
| work = Oracle Database
| publisher = Oracle Corporation
| date = January 2010
| access-date = 2009-04-22
| quote = Oracle Active Data Guard enables read-only access to a physical standby database for queries, sorting, reporting, web-based access, etc., while continuously applying changes received from the production database.
}}</ref>
== Operation ==
=== Server-side functionality ===
'''LNS''' (log-write network-server) and '''ARCH''' (archiver) processes running on the primary database select archived [[redo log]]s and send them to the standby-database host,<ref>
{{cite web
| url = http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_DataGuardNetworkBestPractices.pdf
| title = Data Guard Redo Transport & Network Best Practices: Oracle Database 10g Release 2
| access-date = 2009-03-11
| last = Smith
| first = Michael T
|date= February 2007
| format = PDF
| publisher = Oracle Corporation
| pages = 6, 14
| quote = ... sending processes (LNS and ARC) on the production database....The Data Guard LNS process on the production database performs a network send to the Data Guard RFS process on the standby database.
}}</ref> where the '''RFS''' (remote file server) background process within the Oracle instance performs the task of receiving archived redo logs originating from the primary database and writing them to a standby redo log (SRL).<ref>
{{cite book
|last1= Carpenter
|first1= Larry
|display-authors= etal
|title= Oracle Data Guard 11g Handbook
|url= https://books.google.com/books?id=FG8vM7gsSp8C
|series= Oracle Press
|publisher= McGraw Hill Professional
|publication-date= 2009
|page= 5
|isbn= 9780071621489
| access-date = 2015-02-17
| quote = Redo records transmitted by the LNS are received at the standby database by another Data Guard process called the ''Remote File Server (RFS)''. The RFS receives the redo at the standby database and writes it to a sequential file called a ''standby redo log file (SRL)''.
}}
</ref>
Alternatively, a supplementary mechanism may transfer the archived redo logs. On the standby database a Fetch Archive Log ('''FAL''') client monitors for gaps in the sequence of received logs. If it finds a gap, it may invoke one or more Fetch Archive Log (FAL) servers to run on the primary database to forward the missing item(s).<ref>
[http://www.oracle-base.com/articles/9i/DataGuard.php Oracle-Base site summary of Data Guard], retrieved 2007-09-05; [http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/toc.htm Oracle Corp version 11.1 documentation links], retrieved 2007-09-05.
</ref>
Once the archived redo logs have arrived on the standby host, other processes - such as an '''ARCH''' (archiver process), an '''MRP''' (Managed Recovery Process<ref>
{{cite book
| last = Ault
| first = Mike
| author-link = Mike Ault
| series = Oracle In-Focus Series
| others = Madhu Tumma
| title = Oracle 10g Grid & Real Application Clusters: Oracle 10g Grid Computing with RAC
| url = https://books.google.com/books?id=p-XwSIV9ZYIC
| access-date = 2012-08-31
| year = 2004
| publisher = Rampant TechPress
| isbn = 9780974435541
| page = 640
| quote = [...] the managed recovery process (MRP) on the standby database determines the correct order to apply the archive logs from the different threads on the Standby Database.
}}
</ref>), and/or an '''LSP''' (Logical Standby Process) - may set about applying the log contents to the standby database.
The use of '''standby redo logs''' can speed up the application of changes to a standby database<ref>
{{cite book
|last1= Bach
|first1= Martin
|title= Expert Consolidation in Oracle Database 12c
|url= https://books.google.com/books?id=85cQAwAAQBAJ
|series= Expert's voice in Oracle
|publisher= Apress
|publication-date= 2013
|page= 320
|isbn= 9781430244295
|access-date= 2015-02-19
|quote= [...] with Oracle 10g, [u]sing standby redo logs on the standby database server, the redo stream arriving on the destination could be applied to the standby database immediately, without having to wait for the standby redo log to be archived and applied.
}}
</ref>
with real-time apply.<ref>
{{cite web
| url = http://docs.oracle.com/cd/B19306_01/server.102/b14239/concepts.htm#i1033747
| title = Oracle Data Guard Concepts and Administration, 10g Release 2 (10.2)
| last1 = Schupmann
| first1 = Vivian
| year = 2008
| publisher = Oracle
| access-date = 2015-02-20
| quote = Redo data can be applied either from archived redo log files, or, if real-time apply is enabled, directly from the standby redo log files as they are being filled, without requiring the redo data to be archived first at the standby database.
}}
</ref>
The Data Guard Connection process ('''DRCX''') plays a role in transferring data between databases.<ref>
{{cite web
| url = http://docs.oracle.com/cd/B19306_01/server.102/b14219/e12700.htm#ORA-16589
| title = Oracle Database Online Documentation, 10g Release 2 (10.2)
| year = 2015
| website = docs.oracle.com
| publisher = Oracle
| access-date = 2015-06-16
| quote = The Data Guard Connection process (DRCX) detected an error while transferring data from one database to another.
}}
</ref>
===Client-side access===
The Data Guard Broker subsystem can aid in the setup, management and monitoring of Data Guard configurations.<ref>
{{cite book
| last = Whalen
| first = Edward
| title = Oracle Database 10g Linux administration
| url = https://books.google.com/books?id=2ImPFP6Yk64C
| access-date = 2011-09-07
| year = 2005
| publisher = McGraw-Hill Professional
| isbn = 978-0-07-223053-6
| page = 329
| quote = The Data Guard Broker is the set of utilities and services that manage Data Guard. Included in the Data Guard Broker are both a GUI interface using Oracle Enterprise Manager and a command-line interface (CLI). The Data Guard Broker is used to set up Data Guard, to manage the configuration, and to monitor Data Guard.
}}</ref>
== Advantages ==
Data Guard provides [[high availability]] for a database system. It can also reduce the human intervention required to switch between [[databases]] at [[IT disaster recovery|disaster-recovery]] ("failover") or [[upgrade]]/[[Preventive maintenance|maintenance]] ("switchover") time.
Through the use of standby redo log files, Data Guard can minimize data loss.<ref>
{{cite book
| last = Kumar
| first = Bipul
| title = Oracle Data Guard: Standby Database Failover Handbook
| series = Oracle In-Focus Series
| volume = 19
| year = 2005
| publisher = Rampant TechPress
| isbn = 9780974599380
| page = 277
| quote = With the introduction of [...] standby redo logs [...] it is possible to have a logical standby database be a part of a data Guard configuration running in maximum protection mode. In this way, the Data Guard SQL Apply method offers complete zero-data-loss support.
}}
</ref>
It supports heterogeneous configurations in which the primary and standby systems may have different CPU architectures, operating systems (for example, Microsoft Windows and Linux), operating-system binaries (32-bit/64-bit), or Oracle database binaries (32-bit/64-bit).<ref name="Data Guard Operational Prerequisites">
{{cite web
| title = Data Guard Operational Prerequisites
| url = http://docs.oracle.com/cd/E11882_01/server.112/e10700/standby.htm#i58150
| work = Data Guard Concepts and Administration
| publisher = Oracle Corporation
| access-date = 2013-08-26
| quote = As of Oracle Database 11g, Data Guard provides increased flexibility for Data Guard configurations in which the primary and standby systems may have different CPU architectures, operating systems (for example, Windows & Linux), operating system binaries (32-bit/64-bit), or Oracle database binaries (32-bit/64-bit).
}}</ref>
== Disadvantages ==
If the network link connecting primary and standby is over-subscribed, the redo logs are not shipped in chronological order, which can result in large gaps appearing in the available redo at the standby. Such a condition results in the standby being behind the primary.
<ref name="Oracle Database Options"/> This can be overcome, using Oracle’ Active Data Guard Farsync technology.
The same release of Oracle Database Enterprise Edition must be installed on the primary database and all standby databases, except during rolling database upgrades using logical standby databases.
Oracle Data Guard is available only as a feature of Oracle Database Enterprise Edition.
== See also ==
[[Oracle RAC]]
== References ==
{{Reflist|
[[Category:Oracle software]]
| |||