DG的保護模式
In some situations, a business cannot afford to lose data regardless of the
circumstances. In other situations, the availability of the database may be more
important than any potential data loss in the unlikely event of a multiple failure.
Finally, some applications require maximum database performance at all times, and
can therefore tolerate a small amount of data loss if any component should fail. The
following descriptions summarize the three distinct modes of data protection.
在一些情形下,一些業務不能忍受資料的丟失,一些業務對資料庫的可用性要求比較高,一些業務則可以忍受小資料量的丟失,以下三種情況可以滿足三種不同的模式:
Maximum availability
This protection mode provides the highest level of data
protection that is possible without compromising the availability of a primary
database. Transactions do not commit until all redo data needed to recover those
circumstances. In other situations, the availability of the database may be more
important than any potential data loss in the unlikely event of a multiple failure.
Finally, some applications require maximum database performance at all times, and
can therefore tolerate a small amount of data loss if any component should fail. The
following descriptions summarize the three distinct modes of data protection.
在一些情形下,一些業務不能忍受資料的丟失,一些業務對資料庫的可用性要求比較高,一些業務則可以忍受小資料量的丟失,以下三種情況可以滿足三種不同的模式:
Maximum availability
This protection mode provides the highest level of data
protection that is possible without compromising the availability of a primary
database. Transactions do not commit until all redo data needed to recover those
transactions has been written to the online redo log and to the standby redo log on at
least one synchronized standby database. If the primary database cannot write its redo
stream to at least one synchronized standby database, it operates as if it were in
maximum performance mode to preserve primary database availability until it is
again able to write its redo stream to a synchronized standby database.
This protection mode ensures zero data loss except in the case of certain double faults,
such as failure of a primary database after failure of the standby database.
最大可用,介於最大保護和最大效能之間,如果redo可以傳輸,則會等到至少一個同步的備庫實現日誌已經寫入redo log才會commit,如果實現不了redo的傳輸則主庫則會持續可用。
這種保護模式能夠確保資料0丟失,除了遇到兩個錯誤,例如備庫down機後,主庫也down機了
Maximum performance
This is the default protection mode. It provides the highest
level of data protection that is possible without affecting the performance of a primary
database. This is accomplished by allowing transactions to commit as soon as all redo
data generated by those transactions has been written to the online log. Redo data is
also written to one or more standby databases, but this is done asynchronously with
respect to transaction commitment, so primary database performance is unaffected by
delays in writing redo data to the standby database(s).
This protection mode offers slightly less data protection than maximum availability
mode and has minimal impact on primary database performance.
這種保護模式屬於非同步傳輸,即主庫不考慮備庫的是否已應用日誌的影響
Maximum protection
This protection mode ensures that no data loss will occur if the
primary database fails. To provide this level of protection, the redo data needed to
recover a transaction must be written to both the online redo log and to the standby
redo log on at least one synchronized standby database before the transaction
commits. To ensure that data loss cannot occur, the primary database will shut down,
rather than continue processing transactions, if it cannot write its redo stream to at
least one synchronized standby database.
All three protection modes require that specific redo transport options be used to send
redo data to at least one standby database.
最大保護
這種方式不會出現資料的丟失,主庫會在redo stream失敗的同時shutdown主庫,並且會同時只有當redo log buffer的資訊都寫入到了主庫和至少一個備庫的redo log中才會提交事務
least one synchronized standby database. If the primary database cannot write its redo
stream to at least one synchronized standby database, it operates as if it were in
maximum performance mode to preserve primary database availability until it is
again able to write its redo stream to a synchronized standby database.
This protection mode ensures zero data loss except in the case of certain double faults,
such as failure of a primary database after failure of the standby database.
最大可用,介於最大保護和最大效能之間,如果redo可以傳輸,則會等到至少一個同步的備庫實現日誌已經寫入redo log才會commit,如果實現不了redo的傳輸則主庫則會持續可用。
這種保護模式能夠確保資料0丟失,除了遇到兩個錯誤,例如備庫down機後,主庫也down機了
Maximum performance
This is the default protection mode. It provides the highest
level of data protection that is possible without affecting the performance of a primary
database. This is accomplished by allowing transactions to commit as soon as all redo
data generated by those transactions has been written to the online log. Redo data is
also written to one or more standby databases, but this is done asynchronously with
respect to transaction commitment, so primary database performance is unaffected by
delays in writing redo data to the standby database(s).
This protection mode offers slightly less data protection than maximum availability
mode and has minimal impact on primary database performance.
這種保護模式屬於非同步傳輸,即主庫不考慮備庫的是否已應用日誌的影響
Maximum protection
This protection mode ensures that no data loss will occur if the
primary database fails. To provide this level of protection, the redo data needed to
recover a transaction must be written to both the online redo log and to the standby
redo log on at least one synchronized standby database before the transaction
commits. To ensure that data loss cannot occur, the primary database will shut down,
rather than continue processing transactions, if it cannot write its redo stream to at
least one synchronized standby database.
All three protection modes require that specific redo transport options be used to send
redo data to at least one standby database.
最大保護
這種方式不會出現資料的丟失,主庫會在redo stream失敗的同時shutdown主庫,並且會同時只有當redo log buffer的資訊都寫入到了主庫和至少一個備庫的redo log中才會提交事務
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/29802484/viewspace-2063792/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 【DG】DG的3種保護模式模式
- DG學習筆記(7)_保護模式筆記模式
- ORACLE10G DG中資料保護模式Oracle模式
- DG中3種保護模式之間的切換模式
- DG保護模式與備用聯機日誌檔案模式
- 保護模式模式
- 10g DG保護模式的切換:從最大效能到最大可用模式
- Windows的保護模式 (轉)Windows模式
- 真實模式和保護模式模式
- Oracle-DG最大保護模式下,dg備庫出現問題對主庫有什麼影響?Oracle模式
- 保護性暫停模式模式
- dataguard三種保護模式模式
- DataGuard切換保護模式模式
- 保護模式:段機制模式
- 圖解CPU的真實模式與保護模式圖解模式
- 保護模式篇——PAE分頁模式
- 保護模式知識(三) (轉)模式
- Data Guard 的3種資料保護模式模式
- 保護模式篇——總結與提升模式
- 80386保護模式簡介(轉)模式
- Linux從頭學08:Linux 是如何保護核心程式碼的?【從真實模式到保護模式】Linux模式
- 10G DG最大可用模式下備庫發生故障時主庫保護級別的變化模式
- Data Guard的三種保護模式(摘自官方文件)模式
- 聊聊Dataguard的三種保護模式實驗(上)模式
- 聊聊Dataguard的三種保護模式實驗(下)模式
- 保護模式下的特權級檢查 (轉)模式
- 6 Oracle Data Guard Protection Modes 保護模式Oracle模式
- redis配置檔案中的保護模式protected-modeRedis模式
- Win10系統解除qq保護模式的方法Win10模式
- Oracle9iR2 Data Guard的保護模式(ZT)Oracle模式
- x64 番外篇——保護模式相關模式
- 建立 oracle data gurd 以及三種保護模式Oracle模式
- 【DataGuard】Oracle DataGuard 資料保護模式切換Oracle模式
- 10gR2最大保護模式DataGuard建立模式
- 建立DATAGUARD最大保護模式-測試手記模式
- win10桌面眼睛保護模式怎麼開啟_win10設定電腦眼睛保護模式步驟Win10模式
- 使用Broker管理Data Guard——停用、改保護模式等模式
- 11g dataguard 型別、保護模式、服務型別模式