Laserfiche WebLink
)) TRITRCH <br />SOFTWARE SYSTEMS <br />Inform RMS System Planning Document <br />• Manually execute a database consistency check. (Optional) <br />To failback, the replication between the Master and Replica is reversed and another <br />failover is manually triggered once the two servers are back in synch. The same steps <br />have to be followed when failing back to the production system. The system is then <br />reset to the original configuration to synchronize files and data. <br />Note: Servers utilized for production and disaster recovery must have matching <br />operating systems and SOL versions including service packs. <br />11.2 Disaster Server Best Practices <br />The Disaster Server data may not be actively utilized for reporting purposes (like a <br />Reporting Server) when it is in the Target mode. Additionally, replication may need to be <br />restarted after each server failover. <br />TriTech has identified some challenges related to customer use of ARCserve for <br />Disaster Server functionality. These best practices have been developed to prevent <br />problems with this system. <br />Recommended Actions: <br />1. Always perform synchronization prior to failing back to the production <br />database server. <br />2. ARCserve works by copying data from the disk level. Changes made to your <br />offline database — including reindexing or database def rag — will be <br />overwritten when you resynchronize your servers. <br />3. If you have problems with a failover or a failback, please contact Technical <br />Services, including after hours. Do not attempt to failback and forth between <br />servers if you have a problem as you may damage your most current <br />database if you have missed a step or had an interruption in the process. <br />4. Always contact Technical Services before elective failovers. This will allow <br />for the designation of a configuration engineer in advance to support you if a <br />problem is experienced. <br />5. For elective failovers, have users exit RMS and stop interfaces before the <br />cutover. <br />6. Follow the ARCserve maintenance document before you apply Microsoft <br />updates, SOL service pack, or hot fixes. <br />11.2.1 Disaster Server Hardware Requirements <br />Disaster Server hardware should match the Production Database Server. <br />Page 19 of 25 <br />Proprietary Information. Do not duplicate or disclose. <br />TriTech Software Systems Proprietary Copyrighe2015 <br />