# Component requirements

## System requirements

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

**CentOS**

* CentOS Linux Stream 9

**Red Hat Enterprise Linux**

* Red Hat Enterprise Linux 8.8
* Red Hat Enterprise Linux 8.9
* Red Hat Enterprise Linux 8.10
* Red Hat Enterprise Linux 9.0
* Red Hat Enterprise Linux 9.1
* Red Hat Enterprise Linux 9.2
* Red Hat Enterprise Linux 9.3
* Red Hat Enterprise Linux 9.4
* Red Hat Enterprise Linux 9.5
* Red Hat Enterprise Linux 9.6
* Red Hat Enterprise Linux 9.7

**SUSE Linux Enterprise Server**

* SUSE Linux Enterprise Server 15 SP3
* SUSE Linux Enterprise Server 15 SP4
* SUSE Linux Enterprise Server 15 SP5

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

* Oracle Linux 9

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

* Ubuntu 22.04
* Debian 12.5

{% hint style="info" %}

* Using Red Hat Enterprise Linux requires an active subscription.
* Minimal installation is required.
  {% endhint %}

### Supported browsers

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

* Chrome (latest version)

### MariaDB

Storware Backup & Recovery server requires a MariaDB database server.

* Supported MariaDB versions: 10.11

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 all-in-one installation (Storware Backup & Recovery server and node on the same host):

* 64-bit, 8 processing cores
* 10 GB RAM
* 20GB free disk space for the operating system and Storware Backup and Recovery installation
* Free disk space for data staging
  * You can estimate the free space requirement using the following equation:\
    `(Size of the biggest virtual machine) * (number of parallel backup threads)`

#### Minimum requirements for Storware Backup & Recovery server (standalone installation):

* 64-bit, 4 processing cores
* 4 GB RAM
* 20GB free disk space for the operating system and Storware Backup and Recovery installation

#### Minimum requirements for Storware Backup & Recovery node (standalone installation):

* 64-bit, 4 processing cores
* 6 GB RAM
* 20GB free disk space for the operating system and Storware Backup and Recovery installation
* Free disk space for data staging
  * You can estimate the free space requirement using the following equation:\
    `(Size of the biggest virtual machine) * (number of parallel backup threads)`

More detailed sizing can be found [here](/deployment/sizing.md).

## 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                                                                   | 111/tcp, 111/UDP, 2049/tcp, 2049/UDP, ports specified in `/etc/sysconfig/nfs` - variables `MOUNTD_PORT` (TCP and UDP), `STATD_PORT` (TCP and UDP), `LOCKD_TCPPORT` (TCP), `LOCKD_UDPPORT` (UDP) | NFS access to browse mountable backups and logs from administrative portal (using IP that is detected as the source IP - shown in the Node list in the portal) |
| 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

User `vprotect` must be a member of the group "disk".

Sudo privileges are required for the following commands:

**Storware Backup & Recovery 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`

**Storware Backup & Recovery server:**

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

## SELinux

PERMISSIVE - currently, it interferes with the mountable backups (file-level restore) mechanism. Optionally can be changed to ENFORCING if the file-level restore is not required.


---

# 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.storware.eu/deployment/component-requirements.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.