Failing back to the primary companion and resuming normal companion mode

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. Failback is a planned event. To failback to the primary companion:

Issue sp_companion from the secondary companion to verify that it is in failover mode.

The high availability subsystem automatically restarts the primary companion.
Issue the following from the secondary companion:
```
sp_companion primary_companion_name, prepare_failback
```
where primary_companion_name is the name of primary companion server.

For example, to fail back the primary companion MONEY1, issue the following from the secondary companion PERSONNEL1:
```
sp_companion MONEY1, prepare_failback
```
From the primary companion, issue:
```
sp_companion secondary_companion_name, resume
```
Where secondary_companion_name is the name of the secondary companion server. For example, to resume normal companion mode between primary companion MONEY1 and secondary companion PERSONNEL1:
```
 sp_companion PERSONNEL1, '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 (for example isql -Q) until you issue sp_companion resume. If you do try to reconnect them after issuing sp_companion prepare_failback, the client hangs until you issue sp_companion resume.