This content has been marked as final. Show 7 replies
If it helps at all, here is our config:1 person found this helpful
We have 188.8.131.52 3-Node RAC. Archive logs, RMAN backups etc.... are stored in Fast Recovery Area which is stored in ASM Disk Group consisting of multiple RAID10 SAN LUNs with many back-end spindles...write performance is real good. We backup archive logs from FRA to an ACFS file system on another ASM Disk Group which is on another set of SAN LUNs. We use Data Guard, so archive logs are backed up from the standby site.
Ok, great thank You, someone else ?
Hi,1 person found this helpful
OCFS2 is definitely not the best option (never has been for RAC) => since Oracle 10 it is directly in the ASM diskgroup / FRA.
One reason is: With OCFS2 you have another clusterware running on the node (besides Oracle clusterware), which is not directly integrated.
So ASM (in FRA) and maybe a copy in ACFS for easier administration is the recommended option.
@Greg1 person found this helpful
OCFS2 requires an interconnect. Preferably private because it typically has lower latency.
So,my recommendation is ACFS, because is fully supported and meets all the needs for backup and recover without additional configuration outside the clusterware. Centralized management (such as rolling upgrade, add/remove nodes and so on).
So acfs is the choice , one thing which bothers me is maturity of acfs as its quite fresh .
Did You find it stable in production with 1TB per day of archive and I saw few space related bugs with acfs .
Yes.. Is stable.
I recommend you use ACFS only if it's necessary, because archivelog/backuppiece/redo is supported place directly on ASM.
If you need manage these files (e.g copy from ASM filesystem to tape not using RMAN) then ACFS is recommended.
All depend on of your needs.
You can also store archive logs on ASM disk group :
1) Create new disk group for archive log
2)Change archive location to archive disk group path e.g. '+archive/db/arc'
3) Schedule archive backup using RMAN on ocfs mount point .