Steps to Enable SQL Always On:

SQL Server Always On is a high-availability and disaster recovery feature in Microsoft SQL Server, designed to enhance the resilience and reliability of database systems. It allows databases to have backup copies of the main server, that can take over if the main server faces issues, ensuring that your data is safe and accessible all the time. This provides failover and redundancy to safeguard critical data. SQL Always On support has been introduced from OpManager versions 127256 and above.

Note: This is applicable only to OpManager's MSSQL builds configured with Always On.

To enable SQL Always on in OpManager, follow the below steps,

1. Stop the service
2. Open <OpManagerHome>/conf/customer-config.xml file in text editor, and search for <extended-configurations>.
3. Within the <extended-configurations> section, add the following command line,
   <configuration name="DBCrashHandler" value="com.zoho.mickey.db.adapter.FailOverDBCrashHandler"/>.
4. In the same xml file, change the highlighted value as follows:
   
   

   From this:

   <configuration name="DBConnectionProps" value="">
   
   <property name="DBConnectionRetryInterval" value="30"/>
   
   <property name="DBConnectionRetryCount" value="1"/>
   
   </configuration>

   To this:

   <configuration name="DBConnectionProps" value="">
   
   <property name="DBConnectionRetryInterval" value="5"/>
   
   <property name="DBConnectionRetryCount" value="6"/>
   
   </configuration>

   DBConnectionRetryInterval:Specifies the time interval between each ping from OpManager to the database for connection retries.

   DBConnectionRetryCount: Determines the total number of ping attempts that OpManager will make to the database.

   We've adjusted the values, so that OpManager will try to connect to the DB server six times(DBConnectionRetryCount), waiting five seconds(DBConnectionRetryInterval) between each attempt. This means it will keep trying for a total of 30 seconds. If the SQL failover takes longer than 10 seconds, the DBConnectionRetryCount value should be updated accordingly.

5. Start the service

For failover configured setups, follow the above steps in both primary and secondary servers