> 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-enterprise-w.md).

# Penguin Solutions - everRun Enterprise with Splitsite

**everRun SplitSite** provides continuous-availability protection against **localised power failures, building-wide problems, or physical machine failures**. If disaster strikes one location, the application and data are **immediately available, up-to-date, and fully operational** at the other nearby site, **without needing IT staff at the second location**.

Typical deployments span **from across a campus to a large metropolitan area**. SplitSite uses **synchronous replication**, providing **zero downtime** even in a disaster, and **automatically resynchronises** disk drives and VM memory when a failed site or machine returns.

## Deployment options

* A complete turnkey solution (server plus software).
* Software supplied separately from servers. In this case **Gallagher Engineering should be engaged** to ensure the onsite hardware meets the required specification.

Part number **C861720** (everRun Enterprise with SplitSite).

***


---

# 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-enterprise-w.md?ask=<question>&goal=<user_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.