rman中RETENTION POLICY和BACKUP OPTIMIZATION的制約關係!
更詳細的內容可以參考doc:
本文只針對RETENTION POLICY和BACKUP OPTIMIZATION以及結合043中的一道題做一個簡單的說明,這道題在群內問起的人很多,確實不是很好理解。
[@more@]先看一下doc吧:
If backup optimization is enabled, and if a recovery window retention policy is in
effect, then when performing SBT backups RMAN always backs up datafiles whose
most recent backup is older than the recovery window. For example, assume that:
■ Today is February 21.
■ The recovery window is 7 days.
■ The most recent backup of tablespace tools to tape is January 3.
■ Tablespace tools is read-only.
On February 21, when you issue a command to back up tablespace tools to tape,
RMAN backs it up even though it did not change after the January 3 backup (because
it is read-only). RMAN makes the backup because no backup of the tablespace exists
within the 7-day recovery window.
This behavior allows the media manager to expire old tapes. Otherwise, the media
manager would be forced to keep the January 3 backup of tablespace tools
indefinitely. By making a more recent backup of tablespace tools on February 21,
RMAN allows the media manager to expire the tape containing the obsolete January 3
backup.
--===========================================
題目如下:
You set the recovery window to seven days and the backup optimization to ON using the
CONFIGURE command of Recovery Manager (RMAN). The most recent backup of the TOOLS
tablespace to disk was taken on January 3. The TOOLS tablespace is read-only.
On February 21, when you execute a command to back up all the tablespaces to disk, you find
that RMAN backs up the TOOLS tablespace also, even though the contents of the tablespace
have not changed after the backup on January 3.
Because there are no changes made to the TOOLS tablespace, you decide that the tablespace
should not be backed up by RMAN. What can you do to skip backing up the TOOLS tablespace
without changing the current backup optimization setting?
A. configure a default device for RMAN backups
B. temporarily disable the retention policy for RMAN backups
C. configure automatic channel allocation for RMAN backups
D. use the CONFIGURE command to reconfigure the recovery window to 60 days
--==============================
答案是B沒有問題,因為儲存策略設定的是7天,1月3號做的備份其實已經過期了,所以在2月21號做備份的時候又備了只讀表空間TOOLS,儘管TOOLS的內容沒有任何變化。如果1月3號的備份不過期的話,那麼此時BACKUP OPTIMIZATION ON會發揮作用,就不會在2月21號或者之後的備份中再備份TOOLS表空間,所以說RETENTION POLICY會優先於BACKUP OPTIMIZATION 發揮作用,其實答案D中提到的透過 reconfigure the recovery window to 60 days也可以達到不備份TOOLS表空間的目的,因為修改儲存策略為60天之後,1月3號的備份就不過期了,此時BACKUP OPTIMIZATION ON發揮作用也會skip對TOOLS的備份,所以此題不是很嚴密。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/19602/viewspace-1047945/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Trust Region Policy OptimizationRust
- Using V$BACKUP_ASYNC_IO / V$BACKUP_SYNC_IO to Monitor RMAN PerformanceORM
- iOS 中 UIView 和 CALayer 的關係iOSUIView
- NIO中SelectionKey和Channel、Selector的關係
- 理解JavaScript中BOM和DOM的關係JavaScript
- js中__proto__和prototype的關係JS
- 理解RMAN backup database plus archivelog delete all input命令DatabaseHivedelete
- http中session和cookie的區別和關係HTTPSessionCookie
- WPF中Grid容器中VerticalAlignment和HorizonAlignment和Margin的關係。
- RMAN-03009: failure of backup command on ORA_DISK_1 channelAI
- HTTP請求中的referrer和Referrer-PolicyHTTP
- jre 和 jdk的關係JDK
- @SpringBootApplication和@SpringBootConfiguration的關係Spring BootAPP
- PassEncoder和Pipeline的關係
- EF Code First中的主外來鍵約定和一對一、一對多關係的實現
- java中@Retention是什麼?Java
- ThymeleafViewResolver和SpringTemplateEngine和SpringResourceTemplateResolver的關係ViewSpring
- 程式和產品的關係
- flink jobmanager和taskmanager的關係
- 矩陣:橫向關係和縱向關係矩陣
- session和cookie關係SessionCookie
- RMAN備份中的通道(CHANNEL)相關 - PARALLELISM 、FILESPERSETParallel
- repo和Git的關係 [轉載]Git
- IP地址和MAC地址的關係Mac
- cmsis和各種庫的關係
- HomeAssistantOS和docker的組織關係Docker
- 談談 JDK 和 SAPMachine 的關係JDKMac
- Python和人工智慧的關係Python人工智慧
- undo_retention的作用
- RMAN-06207和RMAN-06208的處理
- c++中的繼承關係C++繼承
- 技術界中的虛擬機器、容器和沙箱的關係虛擬機
- MySQL InnoDB中的事務隔離級別和鎖的關係MySql
- 在Linux中,Unix和Linux之間的關係是什麼?Linux
- 關係型資料庫和非關係型資料庫的區別資料庫
- Cookie 和 Session 關係和區別CookieSession
- RMAN中的通道分配
- RMAN 備份相關的概念
- 徹底搞懂Object和Function的關係ObjectFunction