Installation with DEBs
To install Storware Backup and Recovery components, you can use DEB packages.
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
Packages repository
The repository file must be created on each host where the product components will be deployed.
You can use current instead of the concrete version (i.e. 7.4.0) in the URL
For Ubuntu 22.04 and Debian 12.5
Create a repository file:
echo "deb [trusted=yes] https://repo.storware.eu/vprotect/7.5.0/deb/ ./" | sudo tee /etc/apt/sources.list.d/storware.list
Server
MariaDB package repository file
Before installing MariaDB, please read about supported MariaDB versions here.
Installing MariaDB is required only on the host where the Storware Backup and Recovery server is deployed.
Generate the repository file at MariaDB download site
Copy and paste the generated repo file into
/etc/apt/sources.list.d/mariadb.sources
Server installation
Update the local package index:
Install the server using the following command:
Server configuration
Configure DB access. Run the following command (it is interactive and will ask for the DB root password):
Start the server service:
Open a firewall port:
by default, the server service listens on port 8181. Open the port using the following commands:
Node
Node installation
Install the node using the following command:
Node configuration
Enable HTTPS. To enable HTTPS connectivity, follow these steps Enabling HTTPS connectivity for the nodes.
Configure staging space. Follow the steps described in here Staging space configuration to mount your storage (it can also be used for backup destination - in such case please read also the File Systemsuitable for your storage variant, especially we recommend to use Synthetic File System)
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:
LVM filters. If you're going to use a disk attachment strategy (node installed in a Proxy VM) - follow LVM setup on the nodes for disk attachment backup mode
Register node. Each installed node needs to be registered in the server
where:
<node name> - the name under which the node will appear in the system
<admin user> - the login of the administrative user
<server address>:<port> - address and port of the installed server
Example:
Reboot the Storware Backup and Recovery host to apply the operating system changes:
Verify if the Storware Backup & Recovery node service is operational:
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
vprotectuser)
Please verify node logs to find the root cause (see: Troubleshooting)
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 instructions to configure access to the hypervisors and backup destinations.
Last updated