Rolling Upgrade Scenario: Two OneSpan Authentication Server Instances Using Individual Databases

About this scenario

This scenario describes an environment with the following setup:

• There are two OneSpan Authentication Server instances: server A and server B.
• Each OneSpan Authentication Server instance has its own database.
• User load is distributed evenly between all OneSpan Authentication Server instances using a third-party solution.
• Two-way replication is enabled between all instances to ensure consistency of data across databases

Figure: Rolling upgrade scenario: Two servers using individual databases and replication

Before you begin

Verify that you have addressed the different usability and user load issues related to a rolling upgrade (see General considerations).

Walkthrough: Performing a rolling upgrade on two servers with individual databases

Performing a rolling upgrade on two servers with individual databases

1. Remove the load from server A.
2. Break replication from server B to server A.
3. Wait until the replication queue on server A is empty.
4. Stop the OneSpan Authentication Server service on server A.
5. Break replication from server A to server B.
6. Upgrade OneSpan Authentication Server on server A.
7. Restore replication from server B to server A.
8. Wait until the replication queue on server B is empty.
9. Restore the load to server A.
10. Remove the load from server B.
11. Wait until the replication queue on server B is empty.
12. Stop the OneSpan Authentication Server service on server B.
13. Break replication from server B to server A.
14. Upgrade OneSpan Authentication Server on server B.
15. Restore replication from server A to server B.
16. Restore replication from server B to server A.
17. Wait until the replication queue on server A is empty.
18. Restore load to server B.