Mirroring: Auto-Failover

Tips & Tricks

Back to Tips & Tricks

An auto-failover is triggered if the Acting-Primary or Arbiter determine that a primary can no longer function. The most common reasons are:

  • The Acting-Primary lost contact with the Failover and Arbiter, but the Failover and Arbiter maintained contact with each other
  • The Acting Primary runs into a critical problem, such as an inability to write to disk or major database corruption
  • InterSystems Caché on the Acting-Primary was shut down or restarted without selecting “Don’t fail over.” The following image shows “Don’t fail over” selected as a best practice for continued functionality of the primary
  • The operating system on the Acting-Primary was shut down for any reason while running InterSystems Caché


Failover process overview:

  1. The mirror determines that the Acting-Primary can no longer fulfill its duties
  2. The mirror confirms that the Failover is able to take over the duties of the Acting-Primary. Once this test is passed, the Auto-Failover cannot be cancelled
  3. The Failover is promoted into the Acting-Primary role
  4. If the previous Acting-Primary is still running, its InterSystems Caché will be forced to shut down. It will stay down until manually turned back on


What to do after the failover:

  1. Confirm the new Acting-Failover has every connection in the “On” state. Some connections might not have made the transition
  2. Turn InterSystems Caché on the previous Acting-Primary back on
  3. If the failover was unwanted, gather the cconsole.log file from each system and send them to Support. They are the best way to determine the root cause of the auto-failover
  1. Please label the files by system of origin for clarity
  2. If the failover was unwanted, work on preventing the root cause

More Tips & Tricks Articles

Tips & Tricks

TCP/IP Keep-Alive

Data Innovations’ (DI’s) Instrument Manager (IM) offers connectivity that enables integration with virtually any instrument, LIS, or EMR/EHR regardless of...

Instrument Manager, Tips & Tricks

Following Driver Updates in My DI Community

Overview

Data Innovations (DI) provides ways to stay up to date on the latest driver updates.The first way is right through...

Instrument Manager, Tips & Tricks

Net Gateway Startup Issues (Error 5023)

Overview

When IRIS and Instrument Manager (IM) are starting after a server shuts down or restarts, the .NET gateway is not...

Tips & Tricks

How to Install Instrument Manager™ Core Software

NOTE These instructions apply for Data Innovations’ North American customers. If this is your first time installing IM, please contact Data...

Tips & Tricks

How to help Data Innovations help you when requesting Support

Data Innovations' Tips & Tricks are intended to promote the effective and productive use of Instrument Manager. Fortunately, Instrument Manager...

Tips & Tricks

Evaluation Rules for Clinical Ranges Precaution

When building an Autoverification Rule Set it's common to include evaluation rules for Clinical Ranges. These rules typically set test...

Tips & Tricks

Instrument Manager System Preventative Maintenance (volume 1)

Instrument Manager is a robust software application with a proven track record of operational stability. However, as with any software...

Tips & Tricks

Instrument Manager System Preventative Maintenance (volume 2)

This month's Tips & Tricks is the second installation of Preventative Maintenance recommendations intended to help you maintain a stable...

Ready to learn more?