Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Component requirements

System requirements

Operating System

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

  • Oracle Linux 9

Debian/Ubuntu

  • Ubuntu 22.04

  • Debian 12.5

  • Using Red Hat Enterprise Linux requires an active subscription.

  • Minimal installation is required.

NTFS File System Support

Windows file-level operations require the Storware Backup and Recovery Node to access NTFS file systems. This is needed when the node mounts backup data and allows users to browse, recover, or restore individual files from Windows volumes.

To perform these operations, the node operating system must provide NTFS support. In most Linux environments, this is provided by the ntfs-3g package or another compatible NTFS driver/module.

If NTFS support is not installed on the node, Windows File-Level Restore operations may not be available or may fail when accessing NTFS volumes.

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.

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

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.

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

General Internet access OR fallback-api.cloud.storware.eu

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 (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.

PreviousDeployment
NextSizing Guide

Last updated