FSFO in Oracle Data Guard Broker
📌 What is FSFO?
FSFO = Fast-Start Failover
It is a feature that allows automatic failover from Primary to Standby without DBA intervention when the primary database crashes.
🔑 Key Benefits of FSFO
- Automatic Failover
- Standby becomes Primary automatically if Primary fails
- No DBA intervention required
- Minimizes Downtime
- Critical for production systems
- Failover happens within seconds
- Improves High Availability
- Ensures continuous database access
- Reduces business impact during outages
- Safe Role Transition
- Only triggers failover when Broker detects confirmed failure
- Avoids human error
- Reintegration of Old Primary(reinstate)
- Old Primary can be automatically reinstated as standby if Flashback Database is enabled
flashback database to SCN 121212; but here every thing will be taken care by FSFO🎯 Simple Explanation :
Normally:
-
If Primary fails → DBA must manually run
failover.
With FSFO enabled:
-
If Primary fails → Broker automatically promotes Standby to Primary.
No manual command needed.
FSFO:
-
Continuously monitors the Primary database
-
Uses a separate process called the Observer
-
Automatically triggers failover if conditions are met
-
Minimizes downtime
-
Can provide zero or near-zero data loss (depending on protection mode)
🔑 Key Components
-
Primary database
-
Standby database
-
Observer process (runs on separate server)
✅ In One Line
FSFO is automatic failover in Data Guard Broker that switches to standby immediately when primary fails.
Downside of FSFO (Fast-Start Failover) in Data Guard Broker:
- Observer must run on separate server
- If Observer stops → FSFO does not work
- Extra monitoring responsibility for DBA
-
May trigger failover on temporary glitches → risk of unnecessary role change
-
Requires Observer process running on separate server
-
Possible data loss if using ASYNC redo transport
-
Needs Flashback Database enabled to easily reinstate old primary
-
Adds configuration complexity
In short: FSFO improves availability but can increase risk and complexity if not properly configured.
====>>>>>In real time it is not advisable to use observer (FSFO) <<<<<<<=========
but in case your Client want to have install it on separate server so not to hit the database performance.
No comments:
Post a Comment
Please do not enter any spam link in the comments