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 the 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.
Alternatively, you can use this command to fail back
the resource group:
scswitch -z -h primary_host -g failed_over_group
For example, perform a failback to the primary companion MONEY1 on node1, issue the following command from either the secondary or primary host (if it is running normally under cluster control):
scswitch
-z -h node1 -g rg_MONEY1
To resume normal companion mode, disable monitoring of the primary resource:
scswitch -n -M -j primary_resource
Issue the following from the primary companion:
sp_companion secondary_companion_name, resume
Enable the monitoring of the primary resource with:
scswitch -e -M -j primary_resource
If you are in symmetric mode, use scswitch to enable monitoring of the secondary resource.
You cannot connect clients with the failover property
to an Adaptive Server configured for high availability until you
issue sp_companion resume. If you attempt
to connect them after issuing sp_companion prepare_failback,
the client hangs until you issue sp_companion
resume.