Servers involved:
| Purpose | Environment | IP | Host Name | DB Version |
| DB Server | Production | 10.132.197.66 | INNOSIMDB1V0002 | MS SQL Server 2019 Standard Edition |
| DB Server | Production Secondary | 10.132.197.67 | INNOSIMDB1V0003 | MS SQL Server 2019 Standard Edition |
- AG status before the failover.
We had SIMPra primary over INNOSIMDB1V0002 and secondary over INNOSIMDB1V0003.
- We have issued an entry to userlog table of SIMPra database from the application end before the failover. The goal is to get the same data after the failover that eventually means DB is in sync.
EXPECTATIONS post failover:
- AG should be primary over INNOSIMDB1V0003
- Record must be visible post failover to INNOSIMDB1V0003 node.
- Failover was done from INNOSIMDB1V0002 to INNOSIMDB1V0003 node.
- AG status post failover.
- Record was present over INNOSIMDB1V0003 node.
Applications using SIMPra DB were able to connect after updating application connecting strings from INNOSIMDB1V0002 to INNOSIMDB1V0003 node.
The failover was completed well and SIMPra AG was in healthy state. DRP activity went successful.
Post DRP, we have also changed the AG mode from Asynchronous mode—> Synchronous mode as it was suggested for a long time.
Post DRP AG , we have failed back to INNOSIMDB1V0002 node.
AG status:
