> For the complete documentation index, see [llms.txt](https://docs.storware.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storware.eu/deployment/component-requirements.md).

# Component requirements

Overview of hardware, software, operating system, and network requirements for Storware Backup & Recovery components.

## Operating System <a href="#operating-system" id="operating-system"></a>

The operating system should always be kept up to date with the latest available maintenance updates, patches, and security fixes provided by the operating system vendor.

### **Red Hat Enterprise Linux**

* Red Hat Enterprise Linux 9.8
* Red Hat Enterprise Linux 9.6
* Red Hat Enterprise Linux 8.10

{% hint style="info" icon="redhat" %}
Using Red Hat Enterprise Linux requires an active subscription.
{% endhint %}

### **CentOS**

* CentOS Linux Stream 9

### **SUSE Linux Enterprise Server**

* SUSE Linux Enterprise Server 15 SP7

### Oracle Linux <a href="#debian-ubuntu" id="debian-ubuntu"></a>

* Oracle Linux 9

### Ubuntu <a href="#debian-ubuntu" id="debian-ubuntu"></a>

* Ubuntu 22.04

### Debian <a href="#debian-ubuntu" id="debian-ubuntu"></a>

* Debian 12

## NTFS File System Support

Windows file-level operations require the Storware Backup & Recovery Node to access NTFS file systems.

The node operating system must therefore provide NTFS support, typically through the `ntfs-3g` package or another compatible NTFS driver.

If NTFS support is unavailable, File-Level Restore operations for Windows volumes may fail or may not be available.

## Supported browsers

Administrative UI supports the following browsers.&#x20;

* Google Chrome

We recommend that you use the most up-to-date browser that's compatible with your operating system.

## MariaDB

Storware Backup & Recovery server requires a MariaDB database server.

* Supported MariaDB versions: 10.11 - 11.08

We recommend installing MariaDB from the official [repository](https://mariadb.com/kb/en/mariadb-package-repository-setup-and-usage/).

{% hint style="info" %}
If you need to install MariaDB packages without accessing an external repository during Storware Backup & Recovery installation you also can download RPMs and install them manually as described [here](https://mariadb.com/kb/en/installing-mariadb-with-the-rpm-tool/)
{% endhint %}

## Hardware Requirements

### **Minimum requirements for an all-in-one installation**

Storware Backup & Recovery Server and Node installed on the same host:

* 64-bit system with 8 CPU cores
* 10 GB RAM
* 20 GB of free disk space for the operating system and Storware Backup & Recovery
* Additional free disk space for data staging

Estimate the staging space using:

`Largest protected virtual machine size × number of parallel backup threads`

### **Minimum requirements for Storware Backup & Recovery Server**

For a standalone Server installation:

* 64-bit system with 4 CPU cores
* 4 GB RAM
* 20 GB of free disk space for the operating system and Storware Backup & Recovery

### **Minimum requirements for Storware Backup & Recovery Node**

For a standalone Node installation:

* 64-bit system with 4 CPU cores
* 6 GB RAM
* 20 GB of free disk space for the operating system and Storware Backup & Recovery
* Additional free disk space for data staging

Estimate the staging space using:

`Largest protected virtual machine size × number of parallel backup threads`

## General network requirements

### Communication between the Server and the Node

| Source | Destination                                                            | Ports               | Description                                                                   |
| ------ | ---------------------------------------------------------------------- | ------------------- | ----------------------------------------------------------------------------- |
| Node   | Server                                                                 | 443/tcp or 8181/tcp | Node <-> Server communication over HTTPS (port 443 or 8181)                   |
| Server | Node                                                                   | 2049/tcp            | NFSv4 access to browse mountable backups (using IP detected as the source IP) |
| Server | <p>General Internet access<br>OR<br>fallback-api.cloud.storware.eu</p> | 443/tcp             | Subscription license renewal                                                  |

### Subscription and telemetry

**Server requires Internet access** (on 443/TCP port) in order to enable subscription-based license model and send reports/logs to the support team.

If the Internet connectivity is restricted, then you need to allow traffic from the server to the fallback API endpoint: [fallback-api.cloud.storware.eu](http://fallback-api.cloud.storware.eu) (port 443/TCP)

### Network bandwidth

Make sure to use a high-bandwidth, dedicated network for data transfers:

* from the source to the node
* from the node to the backup destination of your choice

## Security Requirements

### User Permissions

{% hint style="info" icon="arrow-right" %}
User `vprotect` must be a member of the group "disk".
{% endhint %}

Sudo privileges are required for the following commands

**The Node:**

* `/usr/bin/targetcli`
* `/usr/sbin/exportfs`
* `/usr/sbin/kpartx`
* `/usr/sbin/dmsetup`
* `/usr/bin/qemu-nbd`
* `/usr/bin/guestmount`
* `/usr/bin/fusermount`
* `/bin/mount`
* `/bin/umount`
* `/usr/sbin/parted`
* `/usr/sbin/nbd-client`
* `/usr/bin/tee`
* `/opt/vprotect/scripts/vs/privileged.sh`
* `/usr/bin/yum`
* `/usr/sbin/mkfs.xfs`
* `/usr/sbin/fstrim`
* `/usr/sbin/xfs_growfs`
* `/usr/bin/docker`
* `/usr/bin/rbd`
* `/usr/bin/chown`
* `/usr/sbin/nvme`
* `/bin/cp`
* `/sbin/depmod`
* `/usr/sbin/modprobe`
* `/bin/bash`
* `/usr/local/sbin/nbd-client`
* `/bin/make`

**The Server:**

* `/opt/vprotect/scripts/application/vp_license.sh`
* `/bin/umount`
* `/bin/mount`

### SELinux

SELinux should be configured in **Permissive** mode when File-Level Restore is required, as **Enforcing** mode may interfere with mounted backup operations.

If File-Level Restore is not used, SELinux can be configured in **Enforcing** mode.