Laserfiche WebLink
Chapter 3 - System Components <br />13.2 INFORM CAD HOT STANDBY/DISASTER SERVER <br />TriTech has approved a third party Disaster Recovery software that is used to automatically update Inform CAD <br />Database information and Inform CAD File Share information between the production database server on either <br />an on -site Hot Standby Server (HSB) or remote Disaster Server. <br />iB3 AI NI&INi1i[adU1:[9YI& —11�III ]5 <br />All on -site HSB acts as a replacement for the production database server. This provides an on -site redundant <br />server for those sites that operate standard servers and a third level of redundancy for sites that operate Stratus <br />fault tolerant servers. The HSB Server reuses the production server's business server(s) and workstation(s) and <br />there are minimal manual configurations that have to be executed on the production database server, such as <br />database consistency check. This is facilitated by the Disaster Recovery Software Areserve High Availability's <br />(HA) ability to update the DNS record of the production server in DNS. The update of the DNS record allows the <br />business server(s) and workstation(s) to continue to point to the production database server's host name and <br />launch CAD. <br />At this time, TriTech configures the system for manual intervention to initiate a failover. The System <br />Administrator can do manual activation of the failover process remotely. The TriTech.Launch icon on the <br />workstations and interfaces are pointed to the HSB database server's name and no workstation change or <br />re -direction is needed after a successful failover to the HSB Server. Once the manual server failover has been <br />activated, the Inform CAD workstations and interfaces are restarted. To failback — the replication between the <br />Master and Replica is reversed and another failover is manually triggered once the two servers are back in sync. <br />The system is then reset to the original configuration to synchronize files and data. <br />While the Stratus Active Service Architecture would be the recommended method, the HSB Server has been <br />tested to allow for rolling upgrades of OS service packs and server firmware on the primary server. This would <br />reduce system downtime during such scheduled upgrades to a few minutes. Upgrades of full OS versions may be <br />so extensive that a rolling upgrade may not be possible in all situations. Please contact TriTech for additional <br />information regarding specific OS versions. <br />13.2.2 INFORM CAD DISASTER SERVER <br />A remote Disaster Server acts as a replacement for the production database server, This provides an off -site <br />redundant server, but the system requires its own set of business server(s) to operate the system from the remote <br />site. <br />The WAN connection between production and Disaster Server sites should be a minimum of Tl (1.544Mbps) <br />speed to allow for the timely update of files and data. This is only for the data update and is not sufficient <br />bandwidth to operate a substantial number workstations and interfaces from one site connected to another. <br />At this time, the system will be configured for a manual intervention to activate a failover. Manual activation of <br />failover can be done remotely by the System Administrator. <br />There are manual steps that are needed to activate a remote Disaster Center. TriTech will configure Areserve to <br />perform many of the manual steps such as copying preconfigured files and executing batch files. These are based <br />upon the need to change certain database and file settings before the system can be activated. These settings can <br />be pre -configured in advance to allow for a simplified process for the System Administrator. These include the <br />following: <br />/ Preconfigured Files — These files must be preconfigured for the Disaster System and should be stored on the <br />Disaster Server. Areserve post failover will copy the files into their respective location in the Inform CAD <br />File Share. <br />— Launch - Maintaining a preconfigured Launch <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 />