Failback moves the primary companion’s shared disks from the secondary node back to the primary node and starts the primary companion on the primary node. A failback is a planned event. To fail back to the primary companion:
Issue sp_companion from the secondary companion to verify that it is in failover mode.
The high availability system automatically restarts
the primary companion.
Issue the following from the secondary companion, where primary_companion_name is the name of primary companion server:
sp_companion primary_companion_name, prepare_failback
From the primary companion, issue, where secondary_companion_name is the name of the secondary companion server:
sp_companion secondary_companion_name, resume
Issue sp_companion without any options from either companion to make sure you are in normal companion mode.
You cannot connect clients with the failover property
until you issue sp_companion resume.
If you do try to reconnect them after issuing sp_companion
prepare_failback, the client stops responding
until you issue sp_companion resume.
