My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
TRITECH SOFTWARE SYSTEMS -2015
Clerk
>
Contracts / Agreements
>
T
>
TRITECH SOFTWARE SYSTEMS -2015
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/16/2025 3:14:32 PM
Creation date
12/22/2015 9:39:05 AM
Metadata
Fields
Template:
Contracts
Company Name
TRITECH SOFTWARE SYSTEMS
Contract #
A-2015-252
Agency
POLICE
Council Approval Date
11/17/2015
Expiration Date
1/1/1900
Insurance Exp Date
8/31/2026
Destruction Year
2028
Document Relationships
TRITECH SOFTWARE SYSTEMS
(Amended By)
Path:
\Contracts / Agreements\T
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
375
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Chapter 3 • System Components <br />2. The second method is without the use of Areserve HA. In this configuration, all Disaster Mobile server <br />configuration files are configured to launch against the Disaster Recovery Inform CAD server. There is no <br />manual failover process nor are changes performed on the Production Mobile server being sent to the <br />Disaster Recovery Mobile server. As a result, any changes to the Production Mobile server such as adding <br />additional devices, modifying HTML files, or changing Mobile database settings have to manually be <br />performed against the Disaster Recovery Mobile Server. <br />13.3 HOT STANDBY/DISASTER SERVER BEST PRACTICES <br />The Hot Standby/Disaster Server data may not be actively utilized for reporting purposes (like a Reporting <br />Server) when it is in the Target mode. Additionally, replication may need to be restarted after each server <br />failover. <br />The system has been tested through both LAN and WAN connections. The network connectivity for LAN or <br />WAN should be 100Mbps or greater. <br />TriTech has identified some challenges related to customer use of Areserve for Disaster/Hot Standby Server <br />functionality. These best practices have been developed to prevent problems with this system. <br />Recommended Actions: <br />1. Always perform synchronization prior to failing back to the production database server. <br />2. Do not failover to your Hot Standby Server in order to do database maintenance. Areserve works by <br />copying data from the disk level. Changes made to your offline database — including reindexing or database <br />defrag — will be overwritten when you resynchronize your servers. <br />3. If you have problems with a failover or a Tailback, please contact Technical Services, including after hours. <br />Do not attempt to failback and forth between servers if you have a problem as you may damage your most <br />current 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 for the designation of a <br />configuration engineer in advance to support you if a problem is experienced. <br />5. For elective failovers, have users exit CAD and stop interfaces before the cutover. <br />6. Follow the Areserve maintenance document before you apply Microsoft updates, SQL service pack, or hot <br />fixes. <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 />
The URL can be used to link to this page
Your browser does not support the video tag.