# Architecture

***

### **Standalone System Overview**

This implementation is tailored to maximize the efficiency of a standalone x86 server, leveraging available hardware resources for scalable performance. The system is optimized to deliver robust internal hardware protection through multiple network connections and RAID disk controllers.

<figure><img src="/files/PAV5y7qfOtO9kyKNfBJ4" alt="" width="563"><figcaption></figcaption></figure>

### **High Availability**

A High Availability (HA) cluster addresses system reliability by detecting hardware and software failures on the primary node. It automatically restarts Nodeum services on a backup node, removing the need for admin interventions. Nodeum clusters are designed to ensure redundancy and eliminate single points of failure. A heartbeat mechanism continuously monitors the health and status of each node. Metadata and configurations stored in databases and files are replicated across nodes, allowing seamless failover and fallback processes.

<figure><img src="/files/qgmMfxyJOz5xIylO903U" alt="" width="563"><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nodeum.io/data-archiving/architecture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.