Failing back to the primary companion

Failback switches the service group that originally belonged to the primary node from the secondary node back to the primary node and brings it online.

To initiate failback:

After your primary node is ready to take back the service group, issue the following from the secondary companion:
```
sp_companion primary_companion_name, prepare_failback
```
where primary_companion_name is the name of primary companion. This command switches the primary node's service group from secondary node back to primary node. For example, to fail back the primary companion MONEY1, issue this command from the secondary companion PERSONNEL1:
```
sp_companion "MONEY1", prepare_failback
```
```
Step: Primary databases are shutdown in secondary.
Step: Primary databases dropped from current secondary.
Step: Primary devices released from current secondary.
Step: Prepare failback for primary server completed successfully.
```
Make sure the primary nodes service group is successfully switched to primary node by issuing this command from the command line:
```
hastatus -group service_group_name
```
This command displays the status of the primary nodes service group.
To resume normal companion mode, issue the following from the primary companion:
```
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 for primary companion MONEY1:
```
sp_companion "PERSONNEL1", resume
```

You cannot connect clients with the failover property (for example isql -Q) to Adaptive Server 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.