| Export storage repository | SSH transfer | |
|---|---|---|
| Supported versions | 5.2, 5.3, 5.4, 6.0, 6.1, 6.2, 6.3, 6.3, 6.4, 7.0, 7.1, 7.2, 7.3, 7.4, 8.0, 8.1, 8.2 | 5.2, 5.3, 5.4, 6.0, 6.1, 6.2, 6.3, 6.3, 6.4, 7.0, 7.1, 7.2, 7.3, 7.4, 8.0, 8.1, 8.2 |
| The last snapshot is kept on the hypervisor for incremental backups | Yes | Yes |
| Access to hypervisor OS required | Yes | Yes |
| Proxy VM required | Yes | No |
| Export storage repository | SSH transfer | |
|---|---|---|
| Full backup | Supported | Supported |
| Incremental backup | Not supported | Supported |
| Restore | Supported | Supported |
| File-level restore | Supported | Supported |
| VM disk exclusion | Not supported | Supported |
| Quiesced snapshots | Supported | Supported |
| Snapshots management | Supported | Supported |
| Pre/post command execution | Supported | Supported |
| Access to VM disk backup over iSCSI | Not supported | Supported |
| VM name-based policy assignment | Supported | Supported |
| VM tag-based policy assignment | Not supported | Not supported |
| Power-on VM after restore | Supported | Supported |
| Disk attachment | CBT | SSH Transfer | |
|---|---|---|---|
| Supported versions | Queens, Rocky, Stein, Train, Ussuri, Victoria, Wallaby, Xena, Yoga, Zed, Antelope, Bobcat, Caracal | Queens, Rocky, Stein, Train, Ussuri, Victoria, Wallaby, Xena, Yoga, Zed, Antelope, Bobcat, Caracal | Queens, Rocky, Stein, Train, Ussuri, Victoria, Wallaby, Xena, Yoga, Zed, Antelope, Bobcat, Caracal |
| The last snapshot is kept on the hypervisor for incremental backups | Yes | No | Yes |
| Access to hypervisor OS required | No | No | Yes |
| Proxy VM required | Yes | Yes | No |
| Disk attachment | CBT | SSH Transfer | |
|---|---|---|---|
| Full backup | Supported * | Supported | Supported |
| Incremental backup | Not supported | Supported | Supported |
| Restore | Supported | Supported | Supported |
| File-level restore | Supported | Supported | Supported |
| VM disk exclusion | Supported | Supported | Supported |
| Quiesced snapshots | Supported ** | Supported ** | Supported ** |
| Snapshots management | Supported *** | Supported *** | Not supported |
| Pre/post command execution | Supported | Supported | Supported |
| Access to VM disk backup over iSCSI | Supported | Supported | Supported **** |
| VM name-based policy assignment | Supported | Supported | Supported |
| VM tag-based policy assignment | Supported | Supported | Supported |
| Power-on VM after restore | Not supported (always on) | Not supported (always on) | Not supported (always on) |
| Disk attachment | Image transfer | CBT | |
|---|---|---|---|
| Supported versions | 4.3, 4.4, 4.5 | 4.3, 4.4, 4.5 | 4.4, 4.5 |
| The last snapshot is kept on the hypervisor for incremental backups | No | Yes | No |
| Access to hypervisor OS required | No | No | No |
| Proxy VM required | Yes | No | No |
| Disk attachment | Image Transfer | CBT | |
|---|---|---|---|
| Full backup | Supported | Supported | Supported |
| Incremental backup | Not supported | Supported | Supported |
| Restore | Supported | Supported | Supported |
| File-level restore | Supported | Supported | Supported |
| VM disk exclusion | Supported | Supported | Supported |
| Quiesced snapshots | Supported | Supported | Supported |
| Snapshots management | Supported | Supported | Supported |
| Pre/post command execution | Supported | Supported | Supported |
| Access to VM disk backup over iSCSI | Supported | Supported * | Supported |
| VM name-based policy assignment | Supported | Supported | Supported |
| VM tag-based policy assignment | Supported | Supported | Supported |
| Power-on VM after restore | Supported | Supported | Supported |
| Disk attachment | Image transfer | CBT | |
|---|---|---|---|
| Supported versions | 4.0, 4.1, 4.2, 4.3, 4.4, 4.5 | 4.3, 4.4, 4.5 | 4.4, 4.5 |
| The last snapshot is kept on the hypervisor for incremental backups | No | Yes | No |
| Access to hypervisor OS required | No | No | No |
| Proxy VM required | Yes | No | No |
| Disk attachment | Image Transfer | CBT | |
|---|---|---|---|
| Full backup | Supported | Supported | Supported |
| Incremental backup | Not supported | Supported | Supported |
| Restore | Supported | Supported | Supported |
| File-level restore | Supported | Supported | Supported |
| VM disk exclusion | Supported | Supported | Supported |
| Quiesced snapshots | Supported | Supported | Supported |
| Snapshots management | Supported | Supported | Supported |
| Pre/post command execution | Supported | Supported | Supported |
| Access to VM disk backup over iSCSI | Supported | Supported * | Supported |
| VM name-based policy assignment | Supported | Supported | Supported |
| VM tag-based policy assignment | Supported | Supported | Supported |
| Power-on VM after restore | Supported | Supported | Supported |
| Disk attachment | Image transfer | CBT | |
|---|---|---|---|
| Supported versions | 4.0, 4.1, 4.2, 4.3 | 4.3, 4.4 | 4.4 |
| The last snapshot is kept on the hypervisor for incremental backups | No | Yes | No |
| Access to hypervisor OS required | No | No | No |
| Proxy VM required | Yes | No | No |
| Disk attachment | Image Transfer | CBT | |
|---|---|---|---|
| Full backup | Supported | Supported | Supported |
| Incremental backup | Not supported | Supported | Supported |
| Restore | Supported | Supported | Supported |
| File-level restore | Supported | Supported | Supported |
| VM disk exclusion | Supported | Supported | Supported |
| Quiesced snapshots | Supported | Supported | Supported |
| Snapshots management | Supported | Supported | Supported |
| Pre/post command execution | Supported | Supported | Supported |
| Access to VM disk backup over iSCSI | Supported | Supported * | Supported |
| VM name-based policy assignment | Supported | Supported | Supported |
| VM tag-based policy assignment | Supported | Supported | Supported |
| Power-on VM after restore | Supported | Supported | Supported |
| Export storage domain | Disk attachment | |
|---|---|---|
| Supported versions | 8.9 | 8.9 |
| The last snapshot is kept on the hypervisor for incremental backups | No | Yes |
| Access to hypervisor OS required | No | No |
| Proxy VM required | No | Yes |
| Export storage repository | SSH transfer | |
|---|---|---|
| Full backup | Supported | Supported |
| Incremental backup | Not supported | Supported |
| Restore | Supported | Supported |
| File-level restore | Not supported | Supported |
| VM disk exclusion | Supported | Supported |
| Quiesced snapshots | Not supported | Not supported |
| Snapshots management | Supported | Supported |
| Pre/post command execution | Supported | Supported |
| Access to VM disk backup over iSCSI | Supported | Supported |
| VM name-based policy assignment | Supported | Supported |
| VM tag-based policy assignment | Supported | Supported |
| Power-on VM after restore | Supported | Supported |
| HotAdd | NBD | |
|---|---|---|
| Supported versions | 6.5, 6.7, 7.0, 8.0 | 6.5, 6.7, 7.0, 8.0 |
| The last snapshot is kept on the hypervisor for incremental backups | No | No |
| Access to hypervisor OS required | No | No |
| Proxy VM required | Yes | No |
| HotAdd | NBD | |
|---|---|---|
| Full backup | Supported | Supported |
| Incremental backup | Supported | Supported |
| Restore | Supported | Supported |
| File-level restore | Supported | Supported |
| VM disk exclusion | Supported | Supported |
| Quiesced snapshots | Supported | Supported |
| Snapshots management | Supported | Supported |
| Pre/post command execution | Supported | Supported |
| Access to VM disk backup over iSCSI | Supported | Supported |
| VM name-based policy assignment | Supported | Supported |
| VM tag-based policy assignment | Supported | Supported |
| Power-on VM after restore | Supported | Supported |
| Single image (XVA) | CBT | |
|---|---|---|
| Supported versions | 7.4, 7.5, 7.6, 8.0, 8.1, 8.2, 8.3 | 7.4, 7.5, 7.6, 8.0, 8.1, 8.2, 8.3 |
| The last snapshot is kept on the hypervisor for incremental backups | Yes | Yes |
| Access to hypervisor OS required | No | Yes |
| Proxy VM required | No | No |
| Single image (XVA) | CBT | |
|---|---|---|
| Full backup | Supported | Supported |
| Incremental backup | Supported * | Supported |
| Restore | Supported | Supported |
| File-level restore | Not supported | Supported |
| VM disk exclusion | Not supported | Supported |
| Quiesced snapshots | Supported | Supported |
| Snapshots management | Supported | Supported |
| Pre/post command execution | Supported | Supported |
| Access to VM disk backup over iSCSI | Not supported | Supported |
| VM name-based policy assignment | Supported | Supported |
| VM tag-based policy assignment | Supported | Supported |
| Power-on VM after restore | Supported | Supported |
| Single image (XVA) | CBT | |
|---|---|---|
| Supported versions | 6.5, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 8.0, 8.1, 8.2 | 6.5, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 8.0, 8.1, 8.2 |
| The last snapshot is kept on the hypervisor for incremental backups | Yes | Yes |
| Access to hypervisor OS required | No | Yes |
| Proxy VM required | No | No |
| Single image (XVA) | CBT | |
|---|---|---|
| Full backup | Supported | Supported |
| Incremental backup | Supported | Supported * |
| Restore | Supported | Supported |
| File-level restore | Not supported | Supported |
| VM disk exclusion | Not supported | Supported |
| Quiesced snapshots | Supported | Supported |
| Snapshots management | Supported | Supported |
| Pre/post command execution | Supported | Supported |
| Access to VM disk backup over iSCSI | Not supported | Supported |
| VM name-based policy assignment | Supported | Supported |
| VM tag-based policy assignment | Supported | Supported |
| Power-on VM after restore | Supported | Supported |
| Helper pod | Ceph RBD | |
|---|---|---|
| Minimal version | 1.10 | 1.10 |
| The last snapshot is kept on the system for incremental backups | Yes | Yes |
| Access to OS required | No | No |
| Proxy VM required | No | No |
| Helper pod | Ceph RBD | |
|---|---|---|
| Full backup | Supported | Supported |
| Incremental backup | Not supportd | Supported * |
| Restore | Supported | Supported |
| File-level restore | Not supported | Supported * |
| Volume exclusion | Supported | Supported |
| Quiesced snapshots | Supported ** | Supported ** |
| Snapshots management | Not supported | Not supported |
| Pre/post command execution | Supported *** | Supported *** |
| Access to VM disk backup over iSCSI | Not supported | Supported * |
| Name-based policy assignment | Supported | Supported |
| Tag-based policy assignment | Supported | Supported |
| Power-on after restore | Supported | Supported |
| StatefulSet | Supported | Supported |
| Helper pod | Ceph RBD | |
|---|---|---|
| Minimal version | 4.10 | 4.10 |
| The last snapshot is kept on the system for incremental backups | Yes | Yes |
| Access to OS required | No | No |
| Proxy VM required | No | No |
| Helper pod | Ceph RBD | |
|---|---|---|
| Full backup | Supported | Supported |
| Incremental backup | Not supportd | Supported * |
| Restore | Supported | Supported |
| File-level restore | Not supported | Supported * |
| Volume exclusion | Supported | Supported |
| Quiesced snapshots | Supported ** | Supported ** |
| Snapshots management | Not supported | Not supported |
| Pre/post command execution | Supported *** | Supported *** |
| Access to VM disk backup over iSCSI | Not supported | Supported * |
| Name-based policy assignment | Supported | Supported |
| Tag-based policy assignment | Supported | Supported |
| Power-on after restore | Supported | Supported |
| StatfuSet | Supported | Supported |
| Disk attachement | CBT | |
|---|---|---|
| The last snapshot is kept on the hypervisor for incremental backups | No | No |
| Access to hypervisor OS required | No | No |
| Proxy VM required | Yes | Yes |
| Disk attachement | CBT | |
|---|---|---|
| Full backup | Supported | Supported |
| Incremental backup | Not supported | Supported |
| Restore | Supported | Supported |
| File-level restore | Supported | Supported |
| VM disk exclusion | Supported | Supported |
| Quiesced snapshots | Not supported | Not supported |
| Snapshots management | Supported | Supported |
| Pre/post command execution | Supported | Supported |
| Access to VM disk backup over iSCSI | Supported | Supported |
| VM name-based policy assignment | Supported | Supported |
| VM tag-based policy assignment | Supported | Supported |
| Power-on VM after restore | Supported | Supported |
| Disk attachement | CBT | |
|---|---|---|
| The last snapshot is kept on the hypervisor for incremental backups | No | No |
| Access to hypervisor OS required | No | No |
| Proxy VM required | Yes | Yes |
| Disk attachement | CBT | |
|---|---|---|
| Full backup | Supported | Supported |
| Incremental backup | Not supported | Supported |
| Restore | Supported | Supported |
| File-level restore | Supported | Supported |
| VM disk exclusion | Supported | Supported |
| Quiesced snapshots | Not supported | Not supported |
| Snapshots management | Not supported | Not supported |
| Pre/post command execution | Supported | Supported |
| Access to VM disk backup over iSCSI | Supported | Supported |
| VM name-based policy assignment | Supported | Supported |
| VM tag-based policy assignment | Supported | Supported |
| Power-on VM after restore | Not supported (always on) | Not supported (always on) |
| Windows | Linux | |
|---|---|---|
| Supported operating systems | Windows 10, Windows 11, Windows Server 2016, Windows Server 2019, Windows Server 2022 | Red Hat Enterprise Linux 8/9, CentOS 9 Stream, Ubuntu 23.10 |
| Windows | Linux | |
|---|---|---|
| Full backup | Supported | Supported |
| Incremental backup | Supported | Supported |
| Maximum number of protected objects per instance | 5 million | 5 million |
Storware Backup and Recovery 5.x;
Storware Backup and Recovery 6.x;
vProtect: 3.9.x, 4.x;
Storware Backup and Recovery 5.x;
Storware Backup and Recovery 6.x;
Kodo for Endpoints: 4.1
vProtect: 3.9.x, 4.x;
Storware Backup and Recovery 5.x;
Storware Backup and Recovery 6.x;
Kodo for Endpoints: 4.1
vProtect: 3.9.x, 4.x;
Storware Backup and Recovery 5.x;
Kodo for Endpoints: 4.1
vProtect: 3.9.x, 4.x;
Storware Backup and Recovery 5.x;
Kodo for Endpoints: 4.1
vProtect: 3.9.x, 4.x;
Storware Backup and Recovery 5.0;
Kodo for Endpoints: 4.1
vProtect: 3.9.x, 4.1, 4.2, 4.3;
Kodo for Cloud: migration required;
Kodo for Endpoints: 4.1
| | 4.1 (vProtect) | 28.01.2021 | vProtect: 3.9, 3.9.1, 3.9.2 | | 4.3 (Kodo for Cloud) | 31.08.2021 | 4.2, 4.1 | | 4.1 (Kodo for Endpoints) | 24.06.2021 | 4.0 | # Deployment 1. Start with **overview**: * [Architecture](/70/overview/architecture) * [Support Matrix](/70/overview/support-matrix) * [Platform Requirements](/70/deployment/platform-requirements) 2. Check **where node should be installed** for your environment: * [Virtual Environments](/70/protecting-virtual-machines) * [Microsoft 365](/70/protecting-microsoft-365) * [Applications](/70/protecting-applications) * [Storage Providers](/70/protecting-storage-providers) * [Endpoints](/70/protecting-endpoints) 3. **Install** using one of the following options: * [ISO-based installation](/70/deployment/installation/iso-based-installation) (recommended) * [All-in-one quick installation](/70/deployment/installation/quick-install-all-in-one) (recommended) * [Installation using Ansible playbook](/70/deployment/installation/installation-using-ansible-playbook) * [Installation with RPMs](/70/deployment/installation/installation-with-rpms) * [Virtual Appliance](/70/deployment/installation/virtual-appliance) (recommended) Regardless of the installation option you choose: * The node requires **staging space** - assume a number of concurrent export and store tasks and multiply it by the biggest VM size (**for example:** 6 export tasks + 4 store tasks \* 100 GB should require around 1 TB) * The [Staging space configuration](/70/deployment/common-tasks/staging-space-configuration) will guide you to prepare storage on the spare drive * Storware Backup & Recovery is installed in the `/opt/vprotect` folder and staging space is assumed to be in `/vprotect_data` - these are the defaults and should not be changed. 4. **Optionally**, if you want to enable **endpoints protection** follow [Installation overview](/70/deployment/endpoints-how-to-install/installation-overview) 5. Run the **configuration wizard** ([Initial configuration](/70/deployment/initial-configuration)), where you can (or do manually the following steps): * upload the [license](/70/administration/settings/settings#license) * configure connection to the source you would like to protect * configure backup destination - we recommend to use [Synthetic File System](/70/deployment/backup-destinations/filesystem/synthetic-file-system) * configure backup SLA (policies and schedules) * configure backup of your internal DB (for DR purposes) 6. Once you have configured source, backup destination and backup SLA - **initiate backup and restore** operations: * [Virtual Environments](/70/protecting-virtual-machines/backup-and-restore) * [Microsoft 365](/70/protecting-microsoft-365/backup-and-restore) * [Applications](/70/protecting-applications/backup-and-restore) * [Storage Providers](/70/protecting-storage-providers/backup-and-restore) * [Endpoints](/70/protecting-endpoints/backup-and-restore) # Component requirements ## System requirements ### Operating System * CentOS Linux Stream 8 * CentOS Linux Stream 9 * Red Hat Enterprise Linux 8.x * Red Hat Enterprise Linux 9.x * Oracle Linux 8.x * Oracle Linux 9.x * AlmaLinux 8.x * AlmaLinux 9.x * Rocky Linux 8.x * Rocky Linux 9.x * SUSE Linux Enterprise Server (SLES) 15 * Ubuntu 22 * Debian 12.5 {% hint style="info" %} * Using Red Hat Enterprise Linux requires an active subscription. * Minimal installation is required. {% endhint %} ### MariaDB Storware Backup & Recovery server requires a MariaDB database server. * Minimum supported MariaDB version: 10.6 * Latest supported MariaDB version: 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 cores processor * 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 cores processor * 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 cores processor * 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)` ## General network requirements For detailed information about network requirements between Storware Backup and Recovery solution and supported platforms see [Platform Requirements](/70/deployment/platform-requirements) ### Communication between node and server | 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) | ### Network consideration * Depending on where the node is located you need to verify if data will not pass via low-bandwidth links. * Access to the internet network from the node may be required in the following scenarios: * Installation, when using the external repositories * Backup and restore of Amazon EC2, Google Cloud Platform, Azure Cloud and M365 * Storware Backup & Recovery Node requires connectivity with backup destinations * Storware Backup & Recovery Node needs connectivity with the Hypervisor or Hypervisor Manager. * If a netcat transfer is used for Red Hat Virtuallization/oVirt/Oracle Linux VM/Proxmox VE/KVM stand-alone environments - **16000-16999** ports must be reachable from the hypervisors to the node which is responsible for those hypervisors. # Supported platforms requirements ## VMware vCenter/ESXi ### HotAdd **Connection URL:** `https://VCENTER_HOST` or `https://ESXI_HOST` | Source | Destination | Ports | Description | | ------ | ----------------- | ------- | ------------ | | Node | vCenter/ESXi host | 443/tcp | API access | | Node | ESXi hosts | 902/tcp | NBD transfer | ### NBD **Connection URL:** `https://VCENTER_HOST` or `https://ESXI_HOST` | Source | Destination | Ports | Description | | ------ | ----------------- | ------- | ------------ | | Node | vCenter/ESXi host | 443/tcp | API access | | Node | ESXi hosts | 902/tcp | NBD transfer | ## Nutanix AHV ### Disk attachment **Connection URL:** `https://PRISM_HOST:9440/api/nutanix/v3` (Prism Central or Prism Elements) {% hint style="info" %} **Note:** when connecting via Prism Central, the same credentials will be used to access all Prism Elements {% endhint %} | Source | Destination | Ports | Description | | ------ | ----------------------------------------------------- | -------- | --------------------------------- | | Node | Prism Elements (and optionally Prism Central if used) | 9440/tcp | API access to the Nutanix manager | ## OpenStack ### Disk attachment **Connection URL:** `https://KEYSTONE_HOST:5000/v3` | Source | Destination | Ports | Description | | ------ | ------------------------------ | ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | | Node | Keystone, Nova, Glance, Cinder | ports that were defined in endpoints for OpenStack services | API access to the OpenStack management services - using endpoint type that has been specified in hypervisor manager details | | Node | Ceph monitors | 3300/tcp, 6789/tcp | if Ceph RBD is used as the backend storage - used to collect changed-blocks lists from Ceph | ### SSH transfer **Connection URL:** `https://KEYSTONE_HOST:5000/v3` {% hint style="info" %} **Note:** you also must provide SSH credentials to all hypervisors that have been detected during inventory sync {% endhint %} | Source | Destination | Ports | Description | | ---------- | ------------- | ---------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | | Node | Hypervisor | 22/tcp | SSH access | | Hypervisor | Node | netcat port range defined in node configuration - by default 16000-16999/tcp | optional netcat access for data transfer | | Node | Ceph monitors | 3300/tcp, 6789/tcp, 10809/tcp | if Ceph RBD is used as the backend storage - used for data transfer over NBD | ## Virtuozzo ### SSH transfer **Connection URL:** `https://KEYSTONE_HOST:5000/v3` {% hint style="info" %} **Note:** you also must provide SSH credentials to all hypervisors that have been detected during inventory sync {% endhint %} | Source | Destination | Ports | Description | | ---------- | ------------- | ---------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | | Node | Hypervisor | 22/tcp | SSH access | | Hypervisor | Node | netcat port range defined in node configuration - by default 16000-16999/tcp | optional netcat access for data transfer | | Node | Ceph monitors | 3300/tcp, 6789/tcp, 10809/tcp | if Ceph RBD is used as the backend storage - used for data transfer over NBD | ## OpenNebula ### Disk attachment **Connection URL:** `https://MANAGER_HOST` | Source | Destination | Ports | Description | | ------ | ------------ | -------------------------------------- | ------------------------------------------------ | | Node | Manager Host | XML-RPC API port - 2633/tcp by default | API access to the OpenNebula management services | ## oVirt/RHV/OLVM ### Disk attachment **Connection URL:** `https://MANAGER_HOST/ovirt-engine/api` | Source | Destination | Ports | Description | | ------ | ---------------------- | ------- | ------------------------- | | Node | oVirt/RHV/OLVM manager | 443/tcp | oVirt/RHV/OLVM API access | ### Disk Image Transfer **Connection URL:** `https://MANAGER_HOST/ovirt-engine/api` | Source | Destination | Ports | Description | | ------ | ------------------------- | --------- | ------------------------------------------------------------------------------- | | Node | oVirt/RHV/OLVM manager | 443/tcp | oVirt/RHV/OLVM API access | | Node | oVirt/RHV/OLVM hypervisor | 54322/tcp | oVirt/RHV/OLVM ImageIO services - for data transfer (primary source) | | Node | oVirt/RHV/OLVM manager | 54323/tcp | oVirt/RHV/OLVM ImageIO services - for data transfer (fallback to ImageIO Proxy) | ### SSH Transfer **Connection URL:** `https://MANAGER_HOST/ovirt-engine/api` {% hint style="info" %} **Note:** you also must provide SSH credentials to all hypervisors that have been detected during inventory sync {% endhint %} | Source | Destination | Ports | Description | | ------------------------- | ------------------------- | ---------------------------------------------------------------------------- | ---------------------------------------- | | Node | oVirt/RHV/OLVM manager | 443/tcp | oVirt/RHV/OLVM API access | | Node | oVirt/RHV/OLVM hypervisor | 22/tcp | SSH access for data transfer | | oVirt/RHV/OLVM hypervisor | Node | netcat port range defined in node configuration - by default 16000-16999/tcp | optional netcat access for data transfer | ### Change-Block Tracking **Connection URL:** `https://MANAGER_HOST/ovirt-engine/api` | Source | Destination | Ports | Description | | ------ | ------------------------- | --------- | --------------------------------------------------- | | Node | oVirt/RHV/OLVM manager | 443/tcp | oVirt/RHV/OLVM API access | | Node | oVirt/RHV/OLVM hypervisor | 54322/tcp | oVirt/RHV/OLVM ImageIO services - for data transfer | | Node | oVirt/RHV/OLVM manager | 54323/tcp | oVirt/RHV/OLVM ImageIO services - for data transfer | ## Oracle VM ### Export storage domain **Connection URL:** `https://MANAGER_HOST:7002` | Source | Destination | Ports | Description | | ------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | | Node | OVM manager | 7002/tcp | OVM API access | | Hypervisor | Node | If Node is hosting staging space: 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), otherwise please check the documentation of your NFS storage provider | if staging space (export storage repository) is hosted on the Node - NFS access | | Node and hypervisor | shared NFS storage | check the documentation of your NFS storage provider | if staging space (export storage repository) is hosted on the shared storage - NFS access | ## Citrix XenServer/xcp-ng {% hint style="info" %} **Note:** all hosts in the pool must be defined {% endhint %} ### Single image (XVA-based) | Source | Destination | Ports | Description | | ------ | ----------- | ------- | ------------------------------------------------------------------------------------------------------------------------- | | Node | Hypervisor | 443/tcp | API access (for data transfer management IP is used, unless `transfer NIC` parameter is configured in hypervisor details) | ### Changed-Block Tracking | Source | Destination | Ports | Description | | ------ | ----------- | --------- | ------------------------------------------------------------------------------------------------------------------------- | | Node | Hypervisor | 443/tcp | API access (for data transfer management IP is used, unless `transfer NIC` parameter is configured in hypervisor details) | | Node | Hypervisor | 10809/tcp | NBD access (data transfer IP is returned by hypervisor) | ## KVM/Xen stand-alone ### SSH transfer | Source | Destination | Ports | Description | | ---------- | ------------- | ---------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | | Node | Hypervisor | 22/tcp | SSH access | | Hypervisor | Node | netcat port range defined in node configuration - by default 16000-16999/tcp | optional netcat access for data transfer | | Node | Ceph monitors | 3300/tcp, 6789/tcp, 10809/tcp | if Ceph RBD is used as the backend storage - used for data transfer over NBD | ## Proxmox VE ### Export storage repository | Source | Destination | Ports | Description | | ------------------- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | | Node | Hypervisor | 22/tcp | SSH access | | Hypervisor | Node | If Node is hosting staging space: 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), otherwise please check the documentation of your NFS storage provider | if staging space (export storage domain) is hosted on the Node - NFS access | | Node and hypervisor | shared NFS storage | check the documentation of your NFS storage provider | if staging space (export storage domain) is hosted on the shared storage - NFS access | ## Kubernetes **Connection URL:** `https://API_HOST:6443` | Source | Destination | Ports | Description | | ------ | ------------------- | -------- | ----------- | | Node | Kubernetes API host | 22/tcp | SSH access | | Node | Kubernetes API host | 6443/tcp | API access | ## Openshift **Connection URL:** `https://API_HOST:6443` | Source | Destination | Ports | Description | | ----------------- | ------------------- | ------------------ | -------------------------------------------------------------- | | Node | Kubernetes API host | 6443/tcp | API access | | Node | Openshift Workers | 2049/tcp, 2049/udp | NFS connection | | Openshift Workers | Node | 2049/tcp, 2049/udp | NFS connection | | Node | Openshift Workers | 30000-32767/tcp | access to service exposed by Storware Backup & Recovery plugin | ## Hyper-V | Source | Destination | Ports | Description | | ------ | -------------------------------- | ------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | | Node | Storware Backup & Recovery Agent | 50881/tcp for http connection, 50882/tcp for https connection | Storware Backup & Recovery Agent access and data transfer, firewall rules are added automatically during agent installation | ## Azure Stack HCI | Source | Destination | Ports | Description | | ------ | -------------------------------- | ------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | | Node | Storware Backup & Recovery Agent | 50881/tcp for http connection, 50882/tcp for https connection | Storware Backup & Recovery Agent access and data transfer, firewall rules are added automatically during agent installation | ## SC//Platform ### Export Storage Domain **Connection URL:** `https://MANAGER_HOST` | Source | Destination | Ports | Description | | ------------------ | -------------------- | ------- | ------------ | | Node | SC//Platform manager | 443/tcp | API access | | Node | SC//Platform hosts | 445/tcp | SMB transfer | | SC//Platform hosts | Node | 445/tcp | SMB transfer | ### Disk Attachment **Connection URL:** `https://MANAGER_HOST` | Source | Destination | Ports | Description | | ------ | -------------------- | ------- | ----------- | | Node | SC//Platform manager | 443/tcp | API access | ## Huawei FusionCompute **Connection URL:** `https://MANAGER_HOST:8443` | Source | Destination | Ports | Description | | ------------------ | ------------------------ | -------- | ------------ | | Node | Huawei FusionCompute VRM | 8443/tcp | API access | | Node | SC//Platform hosts | 445/tcp | SMB transfer | | SC//Platform hosts | Node | 445/tcp | SMB transfer | ## Microsoft 365 | Source | Destination | Ports | Description | | ------ | ------------- | ------- | ------------------------ | | Node | Microsoft 365 | 443/tcp | Microsoft 365 API access | You can find more detailed descriptions of Office 365 URLs and IP address ranges on [this page](https://learn.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide). To successfully synchronize M365 user account, it must fulfill following requirements: * has an email, * is not filtered by location, country or office location (user filter in UI), * field `user type` is set to `Member`, * has a license or is a shared mailbox. ## OS Agent | Source | Destination | Ports | Description | | -------- | ----------- | --------- | ----------------------------- | | OS Agent | Node | 15900/tcp | Node - OS Agent communication | ## Security Requirements ## User Permissions User `vprotect` must be a member of 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. ## Endpoints client support KODO for Endpoints client can be installed on the following operating systems: * Microsoft Windows 7 32-bit * Microsoft Windows 7 64-bit## VMware vCenter/ESXi ### HotAdd **Connection URL:** `https://VCENTER_HOST` or `https://ESXI_HOST` | Source | Destination | Ports | Description | | ------ | ----------------- | ------- | ------------ | | Node | vCenter/ESXi host | 443/tcp | API access | | Node | ESXi hosts | 902/tcp | NBD transfer | ### NBD **Connection URL:** `https://VCENTER_HOST` or `https://ESXI_HOST` | Source | Destination | Ports | Description | | ------ | ----------------- | ------- | ------------ | | Node | vCenter/ESXi host | 443/tcp | API access | | Node | ESXi hosts | 902/tcp | NBD transfer | * Microsoft Windows 8 32-bit * Microsoft Windows 8 64-bit * Microsoft Windows 8.1 64-bit * Microsoft Windows 8.1 64-bit * Microsoft Windows 10 32-bit * Microsoft Windows 10 64-bit ## Windows 7 (32-bit, 64-bit) The following packages need to be installed on the operating system: * Microsoft Vistual C++ 2012 Redistributable (x64) package-11.0.61030 (During the installation, select only the drive designated for the system, the other drives will be used as data storage for your backups automatically during the initial configuration.
Make sure to change proxy.address to the address of your proxy, it can be either IP address or FQDN.
It is recommended to install Storware Endpoints on different machine than Storware Backup & Recovery.