# Installation with RPMs {% hint style="info" %} * Before installing Storware Backup & Recovery solution we recommend performing an operating system update and reboot if neccesary * Make sure to run all of the commands with administrative privileges. For simplicity, the following commands will be executed as `root` {% endhint %} ## Common - package repositories The repository file must be created on each host where the product components will be deployed. {% hint style="info" %} You can use `current` instead of the concrete version (i.e. `7.4.0`) in the URL {% endhint %} #### **For Red Hat Enterprise Linux 8 and compatible** 1. Create a repository file`/etc/yum.repos.d/vProtect.repo` with the following content: ``` # Storware Backup & Recovery - Enterprise backup solution for virtual environments repository [vprotect] name = vProtect baseurl = https://repo.storware.eu/storware/7.4.0/el8/ gpgcheck = 0 ``` #### **For Red Hat Enterprise Linux 9 and compatible** 1. Create a repository file`/etc/yum.repos.d/vProtect.repo` with the following content: ``` # Storware Backup & Recovery - Enterprise backup solution for virtual environments repository [vprotect] name = vProtect baseurl = https://repo.storware.eu/storware/7.4.0/el9/ gpgcheck = 0 ``` #### **For SUSE Linux Enterprise Server 14 and compatible** 1. Create a repository file`/etc/yum.repos.d/vProtect.repo` with the following content: ``` # Storware Backup & Recovery - Enterprise backup solution for virtual environments repository [vprotect] name = vProtect baseurl = https://repo.storware.eu/storware/7.4.0/suse15/ gpgcheck = 0 ``` 2. Add **Desktop Application Tools** module: ``` SUSEConnect -p sle-module-desktop-applications/15.4/x86_64 ``` 3. Add the **Development tools** module: ``` SUSEConnect -p sle-module-development-tools/15.4/x86_64 ``` ## Server ### MariaDB package repository file **Before installing MariaDB, please read about supported MariaDB versions** [**here**](https://docs.storware.eu/backup-and-recovery-7.4/component-requirements#mariadb)**.** Installing MariaDB is required only on the host where the Storware Backup and Recovery server is deployed. 1. **Generate the repository file** at [MariaDB download](https://downloads.mariadb.org/mariadb/repositories) site 2. **Copy and paste** the generated repo file into `/etc/yum.repos.d/MariaDB.repo` ### Server installation #### Red Hat Enterprise Linux and compatible 1. **Install the server** using the following command: ``` dnf install vprotect-server ``` #### SUSE Linux Enterprise Server and compatible 1. **Install the server** using the following command: ``` zypper install vprotect-server ``` ### Server configuration 1. **Configure DB access.** Run the following command (it is interactive and will ask for the DB root password): ``` vprotect-server-configure ``` 2. **Start** the server service: ``` systemctl start vprotect-server ``` 3. **Open** a firewall **port:** 1. by default, the server service listens on port 8181. Open the port using the following commands: ``` firewall-cmd --add-port=8181/tcp --permanent firewall-cmd --reload ``` 4. Optionally **- forward** the default HTTPS (443) port to port 8181: ``` /opt/vprotect/server/scripts/ssl_port_forwarding_firewall-cmd.sh ``` ## Node ### **Node installation** #### Red Hat Enterprise Linux and compatible 1. **Install the node** using the following command: ``` dnf install vprotect-node ``` #### SUSE Linux Enterprise Server and compatible 1. **Install the node** using the following command: ``` zypper install vprotect-node ``` ### **Node configuration** 1. **Enable HTTPS.** To enable HTTPS connectivity, follow these steps [enabling-https-connectivity-for-nodes](https://docs.storware.eu/backup-and-recovery-7.4/deployment/common-tasks/enabling-https-connectivity-for-nodes "mention"). 2. **Configure staging space.** Follow the steps described in here [Staging space configuration](https://docs.storware.eu/backup-and-recovery-7.4/deployment/common-tasks/staging-space-configuration) to mount your storage (it can also be used for backup destination - in such case please read also the [filesystem](https://docs.storware.eu/backup-and-recovery-7.4/deployment/backup-destinations/filesystem "mention")suitable for your storage variant, especially we recommend to use [synthetic-file-system](https://docs.storware.eu/backup-and-recovery-7.4/deployment/backup-destinations/filesystem/synthetic-file-system "mention")) 3. **Configure the operating system**. Script changes the QEMU user/group to vprotect, disables SELinux, adds Storware Backup and Recovery to the disk group and sudoers policy to allow running privileged commands: ``` vprotect-node-configure ``` 4. **LVM filters.** If you're going to use a **disk** **attachment strategy** (node installed in a Proxy VM) - follow [lvm-setup-on-storware-backup-and-recovery-node-for-disk-attachment-backup-mode](https://docs.storware.eu/backup-and-recovery-7.4/deployment/common-tasks/lvm-setup-on-storware-backup-and-recovery-node-for-disk-attachment-backup-mode "mention") 5. **Register node.** Each installed node needs to be registered in the server ``` vc node inst register --name= --login= --password= --apiurl='http(s)://:/api' ``` where: * \ - the name under which the node will appear in the system * \ - the login of the administrative user * \:\ - address and port of the installed server Example: ``` vc node inst register --name=node1 --login=admin --password=vPr0tect --apiurl='http://localhost:8080/api' ``` 6. **Reboot** the Storware Backup and Recovery host to apply the operating system changes: ``` reboot ``` 7. **Verify** if the Storware Backup & Recovery node service is operational: ``` systemctl status vprotect-node ``` {% hint style="info" %} If not present or not in running state - common errors may include: * wrong FQDN used to connect to the server * wrong hostname used in the server TLS certificate * misconfiguration of staging space (make sure to have it properly mounted in RW mode for `vprotect` user) Please verify node logs to find the root cause (see: [Troubleshooting](https://docs.storware.eu/backup-and-recovery-7.4/troubleshooting)) {% endhint %} ## Post-installation Now you should be able to log in to the Storware Backup & Recovery server using `https://IP_OF_YOUR_MACHINE`. By default, Storware Backup & Recovery has one admin account - `admin` with the password `vPr0tect` (with a zero). Proceed with the [Initial configuration](https://docs.storware.eu/backup-and-recovery-7.4/deployment/initial-configuration) instructions to configure access to the hypervisors and backup destinations.