Backup and Recovery
Backup and Recovery 7.3
Backup and Recovery 7.3
  • About Storware Backup & Recovery
  • What's new in this release
  • Overview
    • Main Features
    • Storware Backup and Recovery concepts
      • Support Matrix
      • Architecture
      • Components
      • Backup types
      • Typical Scenarios
    • Licensing
    • Product Life Cycle
  • Deployment
    • Component requirements
    • Supported platforms requirements
    • Sizing Guide
      • Small
      • Medium
      • Large
    • Installation
      • ISO-based installation
      • Quick Installation using all-in-one script
      • Installation using Ansible playbook
      • Installation with RPMs
      • Deployment in Microsoft Azure
      • Virtual Appliance
        • RHV/oVirt/OLVM Virtual Appliance
        • Citrix Hypervisor | XCP-ng Virtual Appliance
        • VMware Virtual Appliance
        • Nutanix Acropolis Hypervisor (AHV)
    • Initial Configuration
    • Backup Destinations
      • File System
        • Synthetic File System
          • XFS
          • DD Boost
          • ZFS
        • isoLayer (Synthetic)
        • File system
          • Virtual Data Optimizer (VDO)
        • Catalogic Software vStor
      • Deduplication Appliances
        • Dell EMC Data Domain
        • Huawei OceanProtect
        • HPE StoreOnce
        • Exagrid
        • Neverfail HybriStor
      • Object Storage
        • Alibaba Cloud OSS
        • AWS S3 or S3-compatible
        • Ceph Rados Gateway
        • Cloudian S3
        • Wasabi
        • Google Cloud Storage
        • IBM Cloud Object Storage
        • Microsoft Azure Blob Storage
        • Nutanix Objects
        • OpenStack SWIFT
        • Oracle Cloud Infrastructure Object Storage
        • Scality RING
      • Enterprise Backup Providers
        • Dell EMC Avamar
        • Dell EMC Networker
        • IBM Spectrum Protect
        • Micro Focus Data Protector
        • Veritas NetBackup
        • Rubrik Managed Volumes
      • Tape Pools
    • High Availability
      • 2 Node Cluster
      • 3 Node Cluster
    • Common tasks
      • Staging space configuration
      • Enabling HTTPS connectivity for nodes
      • LVM setup on Storware Backup & Recovery Node for disk attachment backup mode
      • Full versions of libvirt/qemu packages installation
      • SSH public key authentication
      • Enabling HTTP(S) Proxy for Storware Backup & Recovery
  • Protecting Virtual Environments
    • Virtual Machines
      • VMware vSphere/ESXi
      • Microsoft Hyper-V
      • Azure Stack HCI
      • Nutanix Acropolis Hypervisor (AHV)
      • Red Hat Openshift Virtualization
      • Red Hat Virtualization
      • oVirt
      • Oracle Linux Virtualization Manager
      • Proxmox VE
      • OpenStack
      • OpenNebula
      • Virtuozzo
      • Verge
      • Citrix Hypervisor (XenServer)
      • XCP-ng
      • SC//Platform
    • Cloud
      • Amazon EC2
      • GCP GCE
      • Azure Cloud
      • Zadara zCompute (Technical preview)
    • Containers
      • Kubernetes
      • Red Hat OpenShift
      • Proxmox VE
    • Backup & Restore
    • v2v migration
  • Protecting Microsoft 365
    • Microsoft 365 organization management
      • Configure Microsoft 365 access
      • Add Microsoft 365 organization manually
      • Add Microsoft 365 organization using the Setup Assistant
      • Account auto-synchronization
    • Backup & Restore
    • Suppoted Sharepoint templates, and limitations
  • Protecting Filesystems
  • Protecting Applications
    • Applications
      • MSSQL
      • MySQL/MariaDB
      • PostgreSQL
      • DB2
      • Oracle
      • Relax and Recover - ReaR
      • Git
      • oVirt/RHV/OLVM
      • Kubernetes/OpenShift etcd
    • Backup & Restore
  • Protecting Storage Providers
    • Storage Providers
      • Ceph RBD
      • Nutanix Files
      • Nutanix Volume Groups
    • Backup & Restore
  • Administration
    • Dashboard
    • Virtual Environments
      • Instances
        • Backup on-demand
        • Restore on-demand
        • Snapshot Management
      • Virtualization Providers
      • Backup SLAs
        • Policies
        • Schedules
      • Snapshot SLAs
        • Policies
        • Schedules
      • Recovery Plans
        • Policies
        • Schedules
      • Mounted Backups (File-level Restore)
    • Storage
      • Instances
        • Backup on-demand
        • Restore on-demand
      • Infrastructure
      • Backup SLAs
        • Policies
        • Schedules
      • Snapshot SLAs
        • Policies
        • Schedules
      • Mounted Backups (File-level Restore)
    • Cloud
      • Instances
      • Service Providers
      • Backup SLAs
        • Policies
        • Schedules
      • Download
    • Applications
      • Instances
      • Execution Configurations
      • Backup SLAs
    • Reporting
      • Virtual Environments
      • Storage
      • Microsoft 365
      • Applications
      • Notifications
      • Audit Log
    • Nodes
      • Instances
      • Node Configurations
    • Access Management
      • Users
      • Groups
      • Roles
      • OS Credentials
    • Settings
      • Global Settings
      • Internal DB Backup
      • Notification Rules
      • Mailing Lists
      • Endpoints Global Settings
    • Upgrade
    • CLI Reference
    • CLI v2 Reference
  • Integration
  • Integration Plugins
    • Red Hat Virtualization UI Plugin
    • oVirt UI Plugin
    • Oracle Linux Virtualization Manager UI Plugin
    • OpenStack UI Plugin
  • Troubleshooting
    • Enable DEBUG mode in Storware Backup and Recovery
    • Collecting logs
    • External log targets
    • Disaster Recovery
  • Known software issues and limitations
  • Glossary
Powered by GitBook
On this page
  • Procedure
  • Create a repository file for Storware Backup and Recovery
  • Create a repository file for MariaDB
  • Red Hat Enterprise Linux or and compatible
  • SUSE Linux Enterprise Server and compatible
  • Server configuration
  • Open a firewall port
  • Node registration
  • Post-installation
  1. Deployment
  2. Installation

Installation with RPMs

To install Storware Backup and Recovery components, you can use RPM packages.

Procedure

Create a repository file for Storware Backup and Recovery

The repository file must be created on each host where the product components will be deployed.

  1. Create a repository file/etc/yum.repos.d/vProtect.repo with the following content:

For Red Hat Enterprise Linux 8 and compatible

# Storware Backup & Recovery - Enterprise backup solution for virtual environments repository
[vprotect]
name = vProtect
baseurl = https://repo.storware.eu/storware/7.3.0/el8/
gpgcheck = 0

For Red Hat Enterprise Linux 9 and compatible

# Storware Backup & Recovery - Enterprise backup solution for virtual environments repository
[vprotect]
name = vProtect
baseurl = https://repo.storware.eu/storware/7.3.0/el9/
gpgcheck = 0

For SUSE Linux Enterprise Server 14 and compatible

# Storware Backup & Recovery - Enterprise backup solution for virtual environments repository
[vprotect]
name = vProtect
baseurl = https://repo.storware.eu/storware/7.3.0/suse15/
gpgcheck = 0

Create a repository file for MariaDB

Installing MariaDB is required only on the host where the Storware Backup and Recovery server is deployed.

  1. Copy and paste the generated repo file into /etc/yum.repos.d/MariaDB.repo

Red Hat Enterprise Linux or and compatible

Server installation

  1. Install package "sudo":

    dnf install sudo
  2. Install the Storware Backup and Recovery server using the following command:

    dnf install vprotect-server

Node installation

  1. Install the Storware Backup and Recovery node using the following command

    dnf install vprotect-node

SUSE Linux Enterprise Server and compatible

Server installation

  1. Add Desktop Application Tools module:

    SUSEConnect -p sle-module-desktop-applications/15.4/x86_64
  2. Add Development tools module:

    SUSEConnect -p sle-module-development-tools/15.4/x86_64
  3. Install package "sudo":

    zypper install sudo
  4. Install the Storware Backup and Recovery server using the following command:

    zypper install vprotect-server

Node installation

  1. Install the Storware Backup and Recovery node using the following command

    zypper install vprotect-node

Server configuration

  1. Configure access to the database. Run the following command:

    vprotect-server-configure
  2. Start the Storware Backup and Recovery server service:

    systemctl start vprotect-server

Open a firewall port

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 --complete-reload

(optional) Forward the default HTTPS port 443 to port 8181:

/opt/vprotect/scripts/./ssl_port_forwarding_firewall-cmd.sh

Node registration

  1. Each installed node needs to be registered in the server:

    vc node inst register --name=<node name> --login=<admin user> --password=<user password> --apiurl='http://<server address>:<port>/api'

    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:

    vc node inst register --name=node1 --login=admin --password=vPr0tect --apiurl='http://localhost:8080/api'
  2. Start the Storware Backup & Recovery node service:

    systemctl start vprotect-node
  3. Run the script to 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 allows run privileged commands:

    vprotect-node-configure
  4. Reboot the Storware Backup and Recovery host to apply the operating system changes:

    reboot

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

Verify in the node section that the node that you installed is connected to the server.

PreviousInstallation using Ansible playbookNextDeployment in Microsoft Azure

Last updated 12 days ago

Before installing MariaDB please read about supported MariaDB versions .

Generate repository file at site

After the initial log in you can configure .

Remember to prepare your staging space as described in the .

Now proceed with the instructions, to configure access to the hypervisors and backup destinations.

MariaDB download
single sign-on using LDAP or Keycloak
Staging space configuration
Initial configuration
here