When the primary machine is again available after a failover has occurred, failback can occur, allowing all database update activity to then occur on that machine. Failback is essentially a failover from the secondary to the primary machine.
Once the failback process completes, all database update operations are again performed on the primary database, and the secondary database returns to read-only access.
You typically run the failback process after the following events occur:
1. A source database has failed.
2. Database processing has moved to the secondary (target) database.
3. The source database been repaired, and you are ready to reinstate the primary database as the source.
