Failback moves the primary companion’s resource group from the secondary node back to the primary node and starts the primary companion on the primary node.
After your primary host is ready to take over the primary companion, disable the monitoring of the secondary resource with the scswitch utility, if you have already not done so:
scswitch -n -M -j secondary_resource
Issue the following from the secondary companion:
sp_companion primary_companion_name, prepare_failback
This command moves the primary companion’s resource group back to the primary host.
For example, to fail back the primary companion MONEY1, issue this command from the secondary companion PERSONEL1:
sp_companion MONEY1, prepare_failback
Alternatively, you can use the following Sun Cluster scswitch utility to
fail back the resource group:
scswitch -z -h primary_host -g failed_over_group
For example, to failback the primary companion MONEY1 on node1, issue the following from either the secondary or primary host (if it is running normally under cluster control):
scswitch -z -h node1 -g ase_rg1
________________________________________________________
To resume normal companion mode, disable monitoring of the primary resource with the scswitch utility:
scswitch -n -M -j primary_resource
Issue the following from the primary companion:
sp_companion secondary_companion_name, resume
For example, to resume normal companion mode for primary companion MONEY1:
sp_companion PERSONEL1, resume
Enable the monitoring of the primary resource with the scswitch utility:
scswitch -e -M -j primary_resource
If you are in symmetric mode, enable monitoring of the secondary resource with the scswitch utility.
You cannot connect clients with the failover property
to an Adaptive Server configured for high availability until you
issue sp_companion resume. If you try
to connect them after issuing sp_companion prepare_failback,
the client hangs until you issue sp_companion
resume.
