Laserfiche WebLink
Chapter 3 - System Components <br />— TriTech Config. <br />— System Ini <br />— ANIAII.ini (if necessary) <br />ISQL Files - TriTech will preconfigure ISQL files that can be stored on the Disaster Server and are <br />executed via batch files. These will activate functions within SQL Server that will update server <br />configuration information that is stored within the Inform CAD databases. There are two different ISQL <br />files that need to be run before activating the system. <br />/ Manually execute a database consistency check (Optional) <br />Once the manual server failover has been activated and the previous steps are completed, the Inform CAD <br />workstations and interfaces are restarted based upon the applicable restart checklist. <br />To Tailback, the replication between the Master and Replica is reversed and another failover is manually <br />triggered once the two servers are back in sync. The same steps have to be followed when failing back to the <br />production system. The system is then reset to the original configuration to synchronize files and data. <br />13.2.3 INFORM MOBILE <br />A remote Disaster Recovery Mobile server acts as a replacement for the production Mobile server. This provides <br />and off -site redundant server which can only be activated against the Disaster Recovery Inform CAD server. The <br />Disaster Recovery Mobile server can be deployed in two methods: <br />1. The first method is with the use of Areserve HA, the production Mobile database and directory can be <br />synchronized with the DR Mobile server in real time. Any updates to the Production Mobile server such as <br />adding a device, modifying a HTML page, changing a Mobile database setting is automatically <br />synchronized with the DR Mobile Server. The failover process with the use of Areserve HA in this <br />configuration is a manual process. During the failover process, Areserve HA will copy configuration files <br />to their respective locations in the Mobile directory. To failback, the replication between the Master and <br />Replica is reversed and another failover is manually triggered once the two servers are back in synch. The <br />system is then reset to the original configuration to synchronize files and data. <br />The contents of this material are confidential and proprietary to TriTech Software Systems, Inc. and may not be reproduced, <br />published or disclosed to others without the prior written consent of TriTech Software Systems, Inc. <br />©2015 TriTech Software Systems <br />