# Compatibility Guide

### Software requirement

**Supported Operating Systems**: List all operating systems the software supports.

**Minimal ISO Image**: Ensure a minimal ISO image is available.

<table><thead><tr><th width="216">Operating System</th><th width="243.33333333333331">Version</th><th>Architecture</th></tr></thead><tbody><tr><td>Linux</td><td>RHEL 8</td><td>x86-64</td></tr><tr><td></td><td>Rocky 8</td><td>x86-64</td></tr><tr><td></td><td>Almalinux 8</td><td>x86-64</td></tr></tbody></table>

### Server Specification

The software can be installed on both physical and virtual servers.

{% hint style="danger" %}
To configure a Tape Library, Nodeum must be installed on a physical server. Tape Libraries are not supported on Virtual Machines.
{% endhint %}

For optimal performance, we suggest these specifications:

<table><thead><tr><th width="166"></th><th width="189">Up to 10 Million Files</th><th width="204">Up to 100 Million Files</th><th>Up to 1 Billion Files</th></tr></thead><tbody><tr><td><strong>Memory</strong></td><td>32 GB</td><td>128GB</td><td>Upon Request</td></tr><tr><td><strong>Processors</strong></td><td>6</td><td>2 x 12</td><td>Upon Request</td></tr><tr><td><strong>System Disk</strong></td><td>110 GB</td><td>900 GB</td><td>Upon Request</td></tr></tbody></table>

{% hint style="info" %}
For configuration and setup details, contact our support team. They will assist in validating the architecture sizing.
{% endhint %}

#### Disk Partitioning Guidelines

For optimal performance, the following disk and volume partitioning specifications are recommended:

* `/opt/`: Minimum size of 100GB (size may vary based on the number of executed tasks and number of files processed by each task)
* `/home/`: Minimum size of 10GB
* `/var/`: Minimum size of 100GB (size may vary based on the number of managed and indexed contents)
* `/tmp/`: Minimum size of 10GB

{% hint style="info" %}
Minimal ISO image is required.
{% endhint %}

### NAS Storage&#x20;

Nodeum supports the following network protocols :

* **NFS**: Versions v3, v4, v4.1, v4.2
* **SMB**: Versions v1, v2.1, v3.0

### Object Storage&#x20;

Nodeum supports interaction with object storage using S3 or Swift protocols.&#x20;

The software ensures compatibility and connectivity with numerous object storage providers.

#### Provider supported

We have validated and certified the compatibility of our product with various object storage providers. The compatibility matrix below outlines the different technologies and vendors that Nodeum supports:

<details>

<summary><strong>Amazon</strong></summary>

<mark style="color:blue;">Product :</mark> AWS S3 Storage

<mark style="color:blue;">Type :</mark> Public

<mark style="color:blue;">Protocol :</mark> S3

<mark style="color:blue;">Nodeum Connector :</mark> Amazon AWS S3 Storage

</details>

<details>

<summary><strong>CEPH</strong></summary>

<mark style="color:blue;">Product :</mark>

<mark style="color:blue;">Type :</mark> On-Premise

<mark style="color:blue;">Protocol :</mark> S3

<mark style="color:blue;">Nodeum Connector :</mark> Generic S3

</details>

<details>

<summary><strong>Cloudian</strong></summary>

<mark style="color:blue;">Product :</mark> HyperStore

<mark style="color:blue;">Type :</mark> On-Premise

<mark style="color:blue;">Protocol :</mark> S3

<mark style="color:blue;">Nodeum Connector :</mark> Cloudian HyperStore

</details>

<details>

<summary><strong>Datacore</strong></summary>

<mark style="color:blue;">Product :</mark> DataCore Swarm

<mark style="color:blue;">Type :</mark> On-Premise

<mark style="color:blue;">Protocol :</mark> S3

<mark style="color:blue;">Nodeum Connector :</mark> DataCore Swarm

</details>

<details>

<summary><strong>DellEMC ECS</strong></summary>

<mark style="color:blue;">Product :</mark> ECS

<mark style="color:blue;">Type :</mark> On-Premise

<mark style="color:blue;">Protocol :</mark> S3

<mark style="color:blue;">Nodeum Connector :</mark> DellEMC ECS

</details>

<details>

<summary><strong>FileBase</strong></summary>

<mark style="color:blue;">Product :</mark>

<mark style="color:blue;">Type :</mark> Public

<mark style="color:blue;">Protocol :</mark> S3

<mark style="color:blue;">Nodeum Connector :</mark> Generic S3

</details>

<details>

<summary><strong>Google</strong></summary>

<mark style="color:blue;">Product :</mark> Google Cloud Storage

<mark style="color:blue;">Type :</mark> Public

<mark style="color:blue;">Protocol :</mark> Google Storage

<mark style="color:blue;">Nodeum Connector :</mark> Google Cloud Storage

</details>

<details>

<summary><strong>Huawei</strong></summary>

<mark style="color:blue;">Product :</mark> **OceanStore**

<mark style="color:blue;">Type :</mark> On-Premise

<mark style="color:blue;">Protocol :</mark> S3

<mark style="color:blue;">Nodeum Connector :</mark> Generic S3

</details>

<details>

<summary><strong>IBM</strong></summary>

<mark style="color:blue;">Product :</mark> IBM Cloud Object Storage (COS)

<mark style="color:blue;">Type :</mark> On-Premise

<mark style="color:blue;">Protocol :</mark> S3

<mark style="color:blue;">Nodeum Connector :</mark> Generic S3

</details>

<details>

<summary><strong>MinIO</strong></summary>

<mark style="color:blue;">Product :</mark>

<mark style="color:blue;">Type :</mark> On-Premise

<mark style="color:blue;">Protocol :</mark> S3

<mark style="color:blue;">Nodeum Connector :</mark> Generic S3

</details>

<details>

<summary><strong>Microsoft</strong></summary>

<mark style="color:blue;">Product :</mark> Azure Blob

<mark style="color:blue;">Type :</mark> Public

<mark style="color:blue;">Protocol :</mark> Blob

<mark style="color:blue;">Nodeum Connector :</mark> Microsoft Azure Blob Storage

</details>

<details>

<summary><strong>NetApp</strong></summary>

<mark style="color:blue;">Product :</mark> StorageGRID

<mark style="color:blue;">Type :</mark> On-Premise

<mark style="color:blue;">Protocol :</mark> S3

<mark style="color:blue;">Nodeum Connector :</mark> Generic S3

</details>

<details>

<summary><strong>OpenStack SwIFT (°)</strong></summary>

<mark style="color:blue;">Product :</mark> non-Keystone - Keystone v2.0 - Keystone v3.0

<mark style="color:blue;">Type :</mark> On-Premise

<mark style="color:blue;">Protocol :</mark> Swift

<mark style="color:blue;">Nodeum Connector :</mark> Openstack Swift

</details>

<details>

<summary><strong>Quantum</strong></summary>

<mark style="color:blue;">Product :</mark> Activescale - ActiveScale Cold Storage

<mark style="color:blue;">Type :</mark> On-Premise

<mark style="color:blue;">Protocol :</mark> S3

<mark style="color:blue;">Nodeum Connector :</mark> Quantum ActiveScale

</details>

<details>

<summary><strong>Scality</strong></summary>

<mark style="color:blue;">Product :</mark> Scality Ring

<mark style="color:blue;">Type :</mark> On-Premise

<mark style="color:blue;">Protocol :</mark> S3

<mark style="color:blue;">Nodeum Connector :</mark> Scality Ring

</details>

<details>

<summary><strong>Wasabi Hot Cloud Storage</strong></summary>

<mark style="color:blue;">Product :</mark>

<mark style="color:blue;">Type :</mark> Public

<mark style="color:blue;">Protocol :</mark> S3

<mark style="color:blue;">Nodeum Connector :</mark> Wasabi Hot Cloud Storage

</details>

### Tape Library&#x20;

Natively, Nodeum supports and manages tape library as secondary storage.
\
It uses the LTFS open format specifications (2.4.0) to write data on magnetic tapes.

Barcode Tape management capabilities are supported for Fiber Channel - SAS Tape Library

Nodeum seamlessly integrates with a variety of Tape Libraries and Tape Drives.&#x20;

It automates tape library management through SCSI over Fiber Channel or an ACSLS server.&#x20;

For tape drive connectivity, it supports both Fiber Channel and SAS. The default tape format is LTO, starting from LTO5.

<details>

<summary><strong>DELL/EMC PowerVault</strong></summary>

<mark style="color:blue;">Product :</mark> Tape Library TL2000 - TL4000 -  ML6000&#x20;

<mark style="color:blue;">Protocol :</mark> Fiber Channel

</details>

<details>

<summary><strong>HPE StoreEver</strong></summary>

<mark style="color:blue;">Product :</mark>  Tape Library ESL G3 - T950 - MSL6480 - MSL2024/4048 -&#x20;

<mark style="color:blue;">Protocol :</mark> Fiber Channel

</details>

<details>

<summary><strong>IBM TS Series</strong></summary>

<mark style="color:blue;">Product :</mark> TS Series

<mark style="color:blue;">Protocol :</mark> Fiber Channel

</details>

<details>

<summary><strong>Quantum Scalar</strong></summary>

<mark style="color:blue;">Product :</mark> Scalar i3 - Scalar i6 - Scalar i500 - Scalar i6000

<mark style="color:blue;">Protocol :</mark> Fiber Channel

</details>

<details>

<summary><strong>Oracle / StorageTek</strong></summary>

<mark style="color:blue;">Product :</mark>  Modular Tape Library : SL150 - SL3000 - SL4000 - SL8500&#x20;

<mark style="color:blue;">Protocol :</mark> Fiber Channel / ACSLS

</details>

<details>

<summary><strong>Overland</strong></summary>

<mark style="color:blue;">Product :</mark>  Neo Series

<mark style="color:blue;">Protocol :</mark> Fiber Channel&#x20;

</details>

<details>

<summary><strong>Spectra Logic</strong></summary>

<mark style="color:blue;">Product :</mark> T950

<mark style="color:blue;">Protocol :</mark> Fiber Channel

</details>

#### LTO Ultrium Drive Series

* LTO-10 Ultrium Drive
* LTO-9 Ultrium Drive
* LTO-8 Ultrium Drive
* LTO-7 Ultrium Drive
* LTO-6 Ultrium Drive
* LTO-5 Ultrium Drive

### Client OS&#x20;

The file system used an internal cache system and is extended with secondary storage volumes.

<table><thead><tr><th width="151">Client Operating system</th><th>Version</th><th>Access Container</th><th>Access Console</th></tr></thead><tbody><tr><td>Windows</td><td>Windows 10 - 11
<br>Windows Server 2008, 2012, 2016</td><td>SMB / NFS</td><td>HTTP/HTTPS</td></tr><tr><td>MacOS</td><td>MacOS </td><td>SMB / NFS</td><td>HTTP/HTTPS</td></tr><tr><td>Linux</td><td>Ubuntu
<br>Debian
<br>Fedora
<br>CentOS
<br>RHEL</td><td>SMB / NFS</td><td>HTTP/HTTPS</td></tr></tbody></table>

### Client Application&#x20;

| Client Application  | OS                  | Protocol        |
| ------------------- | ------------------- | --------------- |
| Cyberduck           | Windows/MacOS       | S3 (HTTP/HTTPS) |
| CloudBerry Explorer | Windows/MacOS       | S3 (HTTP/HTTPS) |
| MinIO Client        | Windows/MacOS/Linux | S3 (HTTP/HTTPS) |
| rclone              | Windows/MacOS/Linux | S3 (HTTP/HTTPS) |


---

# 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/compatibility-guide.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.