A
failback moves the primary node’s resources from the secondary
node back to the primary node and starts the primary Adaptive Server.
IRIX FailSafe and Sybase Failover software offer two different methods
to fail back:
Table 14-2: Automatic transition states
Action
|
Primary node
|
Secondary node
|
Primary server
|
Secondary server
|
|---|
Initial state.
|
The node is down.
|
The node is up and the pri_rg and sec_rg are online.
|
Not running.
|
Adaptive Server is running the primary and
secondary databases.
|
FailSafe services started on the primary
node
|
The node is up with no resource groups
assigned.
|
No change.
|
No change.
|
No change.
|
A prepare_failback is
issued on the secondary server.
|
No change.
|
No changes.
|
No change.
|
The primary server’s databases
and devices are released by the secondary server.
|
The primary resource group pri_rg is
taken offline.
|
No change.
|
The primary server’s resources
are dismounted.
|
No change.
|
No change.
|
The primary resource group pri_rg is
brought online.
|
The node is up and the pri_rg is online.
|
The node is up and the sec_rg is
online.
|
Adaptive Server is started.
|
No change.
|
A resume on the primary companion.
|
No change.
|
No changes.
|
The user databases are brought back online.
|
No change.
|
Final state.
|
The node is up and the pri_rg is online.
|
The node is up and the sec_rg is
online.
|
Adaptive Server is running the primary databases.
|
Adaptive Server is running the secondary databases.
|
