Backup and Recovery
Backup and Recovery 7.1
Backup and Recovery 7.1
  • Storware Backup & Recovery documentation
    • Table of Contents
  • Changelog
  • 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
        • 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
      • Oracle VM
      • Proxmox VE
      • KVM/Xen
      • OpenStack
      • OpenNebula
      • Virtuozzo
      • Verge
      • Citrix Hypervisor (XenServer)
      • XCP-ng
      • Huawei FusionCompute
      • HPE SimpliVity
      • SC//Platform
    • Cloud
      • Amazon EC2
      • GCP GCE
      • Azure Cloud
    • 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
  • File Level Backup and Restore - OS Agent
  • 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
    • Endpoints
      • Environment
      • Administrators
      • Endpoints Server Management
        • Dashboard
        • Packages
        • Organizations
      • Endpoints Administrator
        • Dashboard
        • Users
          • Local users
          • LDAP users
        • Devices
          • Devices list view
          • Device status
        • Backup SLA
          • Create a Backup SLA
            • GENERAL
            • WINDOWS
            • MAC OS (technical preview)
            • EMAIL CLIENTS
          • Backup SLA management
          • Backup SLA removal
        • Restore Jobs
        • Client Deployments
    • 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
  1. Deployment
  2. Backup Destinations
  3. File System

Catalogic Software vStor

Storware Backup & Recovery supports Catalogic vStor Server and integrates with it with extended File System Backup Destination logic.

You can use Catalogic volumes like any other file system (mount a single volume over NFS) or you can use the scripts provided to automatically create and replicate volumes whenever vStor volume is being accessed. This documentation describes a setup with 2 vStor servers and a 1-volume-per-VM approach (with optional replication).

  1. Storware Backup & Recovery accesses vStor Servers using SSH public key authentication - first generate the key:

    [root@vProtectbuild ~]# sudo -u vprotect ssh-keygen
    Generating public/private rsa key pair.
    Enter file in which to save the key (/opt/vprotect/.ssh/id_rsa):  
    Created directory '/opt/vprotect/.ssh'.
    Enter passphrase (empty for no passphrase): 
    Enter same passphrase again: 
    Your identification has been saved in /opt/vprotect/.ssh/id_rsa.
    Your public key has been saved in /opt/vprotect/.ssh/id_rsa.pub.
    The key fingerprint is:
    SHA256:xeceRtL4kq3zzQrUQH/K5SbiT/nv9QvAtBEfOxeT5us vprotect@vProtectbuild.lab.local
    The key's randomart image is:
    +---[RSA 2048]----+
    |          .. . o.|
    |         o +o ooo|
    |          *o=+=. |
    |         .o%o=o. |
    |        S =+@ o .|
    |         o *.= . |
    |          = +.. .|
    |           * +.Eo|
    |            +.++=|
    +----[SHA256]-----+
  2. Add the VM fingerprint to the SSH known_hosts on the node for the primary (and optionally secondary) vStor Server:

    • It must be a known_hosts file that belongs to the vprotect user

    • The algorithm must be set to ssh-rsa

    sudo -u vprotect ssh -o HostKeyAlgorithms=ssh-rsa admin@VSTOR_HOST

    Example:

    [root@vProtectbuild ~]# sudo -u vprotect ssh -o HostKeyAlgorithms=ssh-rsa admin@10.10.10.1
    The authenticity of host '10.10.10.1 (10.10.10.1)' can't be established.
    RSA key fingerprint is SHA256:65M/6jNBXJTFqti/798STSFeZigRzHMivDNl0t95FNI.
    RSA key fingerprint is MD5:cc:91:7d:17:8e:21:68:19:4b:c9:e4:76:bd:f5:4d:fc.
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added '10.10.10.1' (RSA) to the list of known hosts.
  3. Copy the key to each vStor Server:

    [root@vProtectbuild ~]# sudo -u vprotect ssh-copy-id admin@10.10.10.1
    /bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/opt/vprotect/.ssh/id_rsa.pub"
    /bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
    /bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
    admin@10.10.10.1's password: 
    _
    Number of key(s) added: 1
    _
    Now try logging into the machine, with:   "ssh 'admin@10.10.10.1'"
    and check to make sure that only the key(s) you wanted were added.
  4. Open the "BACKUP DESTINATIONS" section on the left menu.

  5. Create a new Catalogic vStor Server Backup Destination (choose from the top-right drop-down menu).

  6. Fill in the template with your information.

  • FIRST_VS_HOST - your primary vStor Server IP/hostname

  • SECOND_VS_HOST - optional, secondary vStor Server IP/hostname, where the data will be replicated to

  • VS_PARTNER_ID - optional, secondary vStor partner ID - you can get this ID by running this command on the vStor Server shell:

    [admin@localhost ~]# vstor partner show
    ID                               | MGMT ADDRESS | API PORT | SSH PORT
    55cd380b7dc848bbb439bfd444bc1799 | 10.10.10.2   | 8900     | 22
  • If a secondary server is not provided, Storware Backup & Recovery will assume that no replication is needed.

  1. Initiate backup to test if the scripts have been executed correctly - in the vprotect_daemon.log files you should be able to see messages like this:

    2018-05-04 15:31:39.133  INFO
    [0f2b9705-61a1-44d5-876f-ac81985c4a94] Executing pre/post store command...
PreviousVirtual Data Optimizer (VDO)NextDeduplication Appliances