> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/resilience-solutions/penguin-solutions-technologies-stratus/penguin-solutions-everrun-and-ftserver.md). # Penguin Solutions - everRun and ftServer For sites that cannot tolerate Command Centre server downtime, **Penguin Solutions** (the company; the product line was previously branded **Stratus**) provides fault-tolerant infrastructure that runs Command Centre **without any changes to the application**. Gallagher supports the Command Centre software side. It **cannot** support setting up the failover software itself. > **Note:** if the Command Centre server fails, **controllers and doors still work regardless** and continue recording events. Failover protects the central server, not door operation. ## Failover compared with switchover * **Failover** is switching to a redundant or standby server, system, hardware component, or network on failure of the active one. It is **automatic**, usually without warning. * **Switchover** is the same operation but requires **human intervention**. ## ftServer (2920 and 4920) ftServer provides the **highest levels of availability**, preventing downtime and data loss before it occurs, with no performance hit to Command Centre. It uses **mirrored hardware components processing the same instructions in "lockstep"** (at the exact same time), keeping both halves of the ftServer in sync. If a component malfunctions, the mirrored component continues processing. It is built from two **enclosures** of redundant hardware. Each performs the same instructions at the same time and constantly monitors its partner (**Lockstep technology**). The **ftServer system software (ftsss)** monitors hardware and runs diagnostics. If an enclosure fails, the second is **immediately promoted to master**, and the server may alert Penguin Solutions via a **dedicated network interface** so a **replacement enclosure** can be dispatched. Once replaced, both parts resynchronise and the ftServer re-enters **Full Duplex** (the fault-tolerant state). ![Stratus ftServer: a black rack-mounted fault-tolerant server built from two stacked enclosures](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-82f5e0ed84efb0d06a0bce8a5732c79575fbfffc%2FSECHUB-failover-penguin-01-ftserver.jpeg?alt=media) ## everRun everRun is a **software layer on top of Intel servers**, adding embedded clustering, fault tolerance, and data replication to **XenServer** (a Linux-based hypervisor). It reaches availability competitive with hardware-based fault-tolerant servers. Because the two servers are **independent** (not one chassis, unlike ftServer), they can be **physically separated**, for example in two rooms or buildings. Software **checkpoints every few hundred milliseconds**, keeping memory, I/O, and applications synchronised. If an application instance fails on the primary, processing continues on the secondary. everRun suits most Command Centre installations, especially where the customer already has servers to deploy on or mandates a specific server brand. ![Stratus everRun product box render: "Continuous application availability software"](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-e2b1e2f8cb01d5f9631a39ba993e7786e1e86806%2FSECHUB-failover-penguin-02-everrun-box.jpeg?alt=media) ## Part numbers > ⚠️ **Check the part number before ordering.** Gallagher's product advisories record that `C861730` and `C861732` transitioned on 1 January 2022 to represent the ztC Edge **200i** and **250i**, and that the **200i (`C861730`) reached end of sale on 30 September 2024**, superseded by the **250i (`C861732`)**. The mapping below comes from the integration documentation and has not yet been reconciled with those advisories. Confirm the current part number with your Gallagher contact before placing an order. | Part Number | Description | | ----------- | --------------------------------- | | C861700 | ftServer 2920 | | C861710 | ftServer 4920 | | C861720 | everRun Enterprise with SplitSite | | C861730 | ztC Edge 250i | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/resilience-solutions/penguin-solutions-technologies-stratus/penguin-solutions-everrun-and-ftserver.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.