StorNext Connect Failovers

Note: This information applies to high-availability (HA), dual-node Quantum appliances only.

StorNext Connect is run on server Node 2 of the Quantum appliance. Server Node 1 will be operating as the primary node when the appliance is first brought online, and Node 2 will be operating as the secondary (failover/standby) node. This is the normal operating state of the appliance server nodes.

If a failover were to occur, causing both StorNext and StorNext Connect to be co-located on the same server node, the resources used by StorNext Connect could affect the performance of StorNext. A script, called snc_disable.py, is invoked by a Cron job once per minute that checks the status of snhamgr to determine the state of the server nodes. The script shuts down StorNext Connect when it detects that both the StorNext and StorNext Connect services are running on the same server node (which occurs after a failover). This allows StorNext to use all available necessary system resources.

Did you know?

During StorNext upgrades, the appliance fails over twice so that after the upgrade completes on both nodes, the server nodes are set back to the system state prior to the upgrade, with Node 1 operating as the primary. When Node 2 is operating as secondary again, StorNext Connect is enabled.