Optimizing Serviceguard Failover Time, Version A.11.19 and later, April 2009

7
What happens when failover is triggered by a package failure
These are the steps in a failover that is caused by a package failure (rather than a node failure).
Figure 3. Steps in a failover caused by package failure— Serviceguard implementation
Note: Diagram is not to scale. Application failover time varies by application.
The steps in the Serviceguard component of failover are:
• Resource failure detection—Serviceguard notices that a monitored service or resource is down.
• Package determination—Serviceguard decides whether, and where, to restart the packages.
With Serviceguard implementations, the steps in the application-dependent component are:
• Resource recovery—Serviceguard makes the packages resources available for the packages.
• Application recovery—This time is to restart applications or processes that were moved to a new
node.
Serviceguard with Serviceguard Extension for RAC, failure of a RAC package does not trigger any
failover action from Serviceguard. If there is a failure, such as a database instance crash, the
Serviceguard cluster will keep running without re-forming, so there is no Serviceguard component to
the failover.
Oracle RAC re-forms a new membership and performs database recovery.
Resource
failure detection
Serviceguard
failover time
Application
failover time
Package
determination
Resource recovery (VG, FS, IP) Application recovery