5. Resume to the State before Failover
Follow the steps below to resume both Brekeke servers to the setup before the failover occurred.
After failover happened:
Server – A: Original “Primary” server
Server – B: Original “Secondary” server; (Running as “Primary” server when failover happened.)
Steps: (v3.9.1.0 or later)
1. Click [Switch the role] button.
Log in the Brekeke’s admintool in Server – A (the original primary) or Server – B (the original secondary).
Go to [SYSTEM] > [Redundancy] > [Mirroring] page.
Click [Switch the role] button.
2. Check the status at both servers.
Log in the Brekeke’s admintool of both servers.
Go to [SYSTEM] > [Redundancy] > [Mirroring] page.
Check the following fields at the [Status] section:
Server – A
role : Primary service-address : <Service IP Address> (assigned)
Server – B
role : Secondary service-address : <Service IP Address> (not assigned)
Steps:(v3.8 or earlier)
1. Shutdown the Server-B.
Go to [Status] > [Start/Shutdown] page.
Click the [Shutdown] button.
2. Remove the virtual IP address from the Server-B.
Go to the OS’s network settings.
Remove the virtual IP address (e.g. 172.16.0.10) from the OS.
3. Change the Server-B role to “Secondary”.
Go to [Redundancy] > [Mirroring] page.
Select the “Secondary” at the [Role] field.
4. Start the Server-A.
5. Start the Server-B.
6. Start the Heartbeat at the Server-B.
Go to [Redundancy] > [Heartbeat] page.
Push [Start] button.