ASM 11g新功能fast disk resync
背景:
1) When we take a disk offline in case the disk is corrupted or database is not able to read or write from the disk. In case of Oracle database 10g, oracle engine use to balance the other disks with the content of offline disk. This process was a relatively costly operation, and could take hours to complete, even if the disk failure was only a transient failure.
--10g時,若有ASM disk離線,資料庫會將offline disk的資料分配到其他disk,此操作比較耗時且代價高昂;
2) Oracle Database 11g introduces the ASM Fast Mirror Resync feature that significantly reduces the time required to resynchronize a transient failure of a disk. When a disk goes off line oracle engine doesn’t balance other disk, instead ASM tracks the allocation units that are modified during the outage. The content present in the failed disk is tracked by other disks and any modification that is made to the content of failed disk is actually made in other available disks. Once we get the disk back and attach it, the data belonging to this disk and which got modified during that time will get resynchronized back again. This avoids the heavy re-balancing activity.
--11g引入fast mirror resync功能,若磁碟offline則其他磁碟負責記錄並用對該磁碟的所有改動,等磁碟可訪問時再進行同步,前提是該磁碟資料沒有損壞,否則需要drop;
3) ASM fast disk resync significantly reduces the time required to resynchronize a transient failure of a disk. When a disk goes offline following a transient failure, ASM tracks the extents that are modified during the outage. When the transient failure is repaired, ASM can quickly resynchronize only the ASM disk extents that have been affected during the outage.
4) This feature assumes that the content of the affected ASM disks has not been damaged or modified.
5) When an ASM disk path fails, the ASM disk is taken offline but not dropped if you have set the DISK_REPAIR_TIME attribute for the corresponding disk group. The setting for this attribute determines the duration of a disk outage that ASM tolerates while still being able to resynchronize after you complete the repair.
Note: The tracking mechanism uses one bit for each modified allocation unit. This ensures that the tracking mechanism very efficient.
--ASM使用bit追蹤每個被修改的AU,一個bit對應一個AU
ASM 11g New Features - How ASM Disk Resync Works.
Requirements:
1) This feature requires that the redundancy level for the disk should be set to NORMAL or HIGH.
2) compatible.asm & compatible.rdbms = 11.1.0.0.0 or higher
3) You need to set DISK_REPAIR_TIME parameter, which gives the time it takes for the disk to get repaired. The default time for this is set to 3.6 hours.
Examples:
SQL> ALTER DISKGROUP dgroupA SET ATTRIBUTE 'DISK_REPAIR_TIME'='3H';
4) The disk has to be offline (automatically due to the hardware failure or manually for maintenance operations) and should not be dropped.
To take the disk offline use:
SQL> ALTER DISKGROUP ??? OFFLINE DISKS command.
Example:
ALTER DISKGROUP dgroupA OFFLINE DISKS IN FAILGROUP controller2 DROP AFTER 5H;
Repair time for the disk is associated with diskgroup. You can override the repair time of diskgroup using following command:
SQL> ALTER DISKGROUP dgroupA SET ATTRIBUTE ???DISK_REPAIR_TIME???='3H???;
Additional Manual Offline Disk Operations Examples:
SQL>ALTER DISKGROUP DG1 OFFLINE DISK DG1_0003 ;
SQL>ALTER DISKGROUP DG1 OFFLINE DISK DG1_0003 DROP AFTER 1H;
SQL>ALTER DISKGROUP DG1 OFFLINE DISKS IN FAILGROUP FG1;
SQL> ALTER DISKGROUP dgroupA OFFLINE DISKS IN FAILGROUP controller2 DROP AFTER 5H;
5) After the transient failure was corrected on the affected disks, you will need to explicitly online the disks.
Examples:
SQL>ALTER DISKGROUP DG1 ONLINE DISK DG1_0003;
SQL>ALTER DISKGROUP DG1 ONLINE DISKS IN FAILGROUP FG1 POWER 8 WAIT;
6) If you cannot repair a failure group that is in the offline state, you can use the ALTER DISKGROUP DROP DISKS IN FAILGROUP command with the FORCE option. This ensures that data originally stored on these disks is reconstructed from redundant copies of the data and stored on other disks in the same diskgroup.
Example:
SQL> ALTER DISKGROUP dgroupA DROP DISKS IN FAILGROUP controller2
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/15480802/viewspace-733942/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ASM Fast Mirror ResyncASMAST
- ASM 11g New Features - How ASM Disk Resync WorksASM
- drop asm disk、撤銷drop asm diskASM
- 手工建立ASM Disk Groups、為 ASM Disk Groups 新增 diskASM
- Asm disk managerASM
- Oracle ASM Disk DirectoryOracleASM
- Oracle ASM Disk PartnerOracleASM
- ASM Disk Group TemplateASM
- ASM: Device is already labeled for ASM diskASMdev
- Oracle ASM Disk HeaderOracleASMHeader
- Oracle ASM spfile in a disk groupOracleASM
- Oracle ASM Disk Used Space DirectoryOracleASM
- Oracle ASM ACFS disk group rebalanceOracleASM
- Oracle ASM Disk Group AttributesOracleASM
- ASM DISK HEADER CORRUPTION & REPAIRASMHeaderAI
- ASM Normal需要3個disk ?ASMORM
- asm disk 的結構(1)ASM
- oracleasm createdisk ASM: Device is already labeled for ASM diskOracleASMdev
- ASM 翻譯系列第十彈:ASM Internal ASM DISK headerASMHeader
- Using ASMLIB Management ASM DiskASM
- [Oracle Script] ASM Disk Groups UsedOracleASM
- ASM磁碟組刪除DISK操作ASM
- Identify If A Disk/Part Is Still Used By ASM,Used by ASM Or Used by ASM_603210.1IDEASM
- RAC關鍵資訊(OCR/VOTE DISK/ASM DISK HEADER)備份ASMHeader
- Oracle ASM disk誤被格式化OracleASM
- V$ASM_DISK 檢視含義ASM
- 使用KFOD模擬ASM DISK DISCOVERY過程ASM
- ASM disk group mount fails with ORA-15036ASMAI
- oracle10g_asm_v$asm_disk之header_statusOracleASMHeader
- ASM disk group mount fails with ORA-15036: disk is truncated [ID 1077175.1]ASMAI
- ASM Disk丟失的臨時解決方法ASM
- 幾個重要的 ASM Disk Groups 引數ASM
- ORA-15260: permission denied on ASM disk groupASM
- ASM的資料庫遷移回到DISK上ASM資料庫
- TROUBLESHOOTING - ASM disk not found/visible/discovered issuesASM
- 對ASM dgdata 磁碟組增加disk實施步驟ASM
- 直接修改ASM disk大小導致ORA-15036ASM
- Oracle 使用BBED 檢視 ASM Disk Header 內容OracleASMHeader