Retaining connectivity post failover

[Richard_Evans1]

Hi All!

Our installation of OnBase is very sensitive to network issues (v.18).   All of our other applications, with the exception of voice and video traffic, do  not appear to suffer the same issues. Our network is built with redundancy in place. If a network device fails, traffic is routed to a working device automatically. All of our applications with the exception of OnBase seem to survive these brief outages (typically just seconds).  Over the years, we have come to believe that it is related to the connection to the SQL database.  OnBase is our only application that does not survive a quick cluster failover. Nor do its VMs survive a host migration.    We have always wondered if the application's tolerance to a loss of connectivity to SQL are configurable. Maybe some type of "keep alive" setting.   

Is there anything in OnBase that can be configured to prevent the web, application, and timer servers from failing due to a brief loss of connectivity?

I really appreciate the help. 

Makarios

[AdamShaneHyland]

Hi Ashish.

You can read more about Microsoft SQL Always On Availability Groups here (link).

Most of the references to hostnames are in configuration files (web.config for the web services like the Web Server and Application, or client configuration files like the obunity.exe.config for the Unity Client).  When it comes to hostnames of servers, from a DR perspective alias's are very helpful (DNS CNAME records).  This way the hostname of a server is never directly referenced, but instead your servers are always referenced by their alias.  If a DR scenario occurs, all you would need to do is update the alias records where applicable.  Keep in mind that there are many technologies which can be used to limit the amount of downtime in order to fail over to the DR site. 

You can read more about DR strategies in the HA/DR white paper here (link).