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
  • Preparation
  • Importing existing VDO volumes to LVM
  1. Deployment
  2. Backup Destinations
  3. File System
  4. File system

Virtual Data Optimizer (VDO)

In this section, you can find information on how to enable deduplication using basically any block storage available. We assume that you have prepared your storage provider and have exposed the block device to the system where Storware Backup & Recovery Node is installed.

Preparation

Disable Secure Boot option for the VM to allow VDO work properly. Run below command to check status of Secure Boot option:

mokutil --sb-state
  1. Log in to Storware Backup & Recovery Node and create a mount directory as in the example /backupdestination

    mkdir /backupdestination
  2. List all existing disks, and find your drive. Let's assume /dev/sdc is your empty block device that you want to use:

    [root@vProtect01 ~]# fdisk -l | grep dev
    Disk /dev/sda: 32.2 GB, 32212254720 bytes, 62914560 sectors
    /dev/sda1   *        2048     1026047      512000   83  Linux
    /dev/sda2         1026048    62914559    30944256   8e  Linux LVM
    Disk /dev/sdc: 500 GB, 17179869184 bytes, 33554432 sectors
    Disk /dev/sdb: 21.5 GB, 21474836480 bytes, 41943040 sectors
    Disk /dev/mapper/centos-root: 28.5 GB, 28462546944 bytes, 55590912 sectors
    Disk /dev/mapper/centos-swap: 3221 MB, 3221225472 bytes, 6291456 sectors
  3. Log in to the vProtect web UI.

  4. Go to Backup Destinations.

  5. Click on Create Backup Destination, choose a File system.

  6. Type the name for the new backup destination, set the retention, and select at least one node configuration.

  7. Based on whether the staging space is same as backup destination or not, do one of the following:

    • If the staging space is different than your backup destination storage:

      • In Storage paths type /backupdestination - this path will be used to mount the prepared file system (XFS) on top of the VDO volume.

      • Check Enable deduplication.

      • Provide your block device (for example /dev/sdc) as your Deduplication device.

    • If the staging space needs to be the same as your backup destination storage:

      • In Storage paths type /vprotect_data/backups - this path assumes that /vprotect_data is your staging space path and backups is a subdirectory of the staging space.

      • Check Enable deduplication.

      • Provide your block device (for example /dev/sdc) as your Deduplication device.

      • Enable Mount deduplicated file system to a different directory than backup destination path and provide the mount point - your staging space path, for example /vprotect_data - this will force Storware Backup & Recovery to mount XFS on top of VDO in the staging space directory rather than in the backup subdirectory.

Note: Only one file system backup destination with deduplication using VDO pointing to a specific directory can be used. If you want to add another backup destination using the same VDO device, but just a different subdirectory, create it without deduplication enabled.

Importing existing VDO volumes to LVM

The python-based VDO management software has been deprecated and removed from RHEL 9/CentOS 9 Stream. It has been replaced by the LVM-VDO integration. If you are using VDO on RHEL 8/CentOS 8 Stream and plan to upgrade to version 9, you need to convert VDO volume.

In this example we have VDO volume called VDOexample created and managed by Storware Backup & Recovery.

[root@sbr-node ~]# lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda            8:0    0   40G  0 disk 
|-sda1         8:1    0  600M  0 part /boot/efi
|-sda2         8:2    0    1G  0 part /boot
`-sda3         8:3    0 38.4G  0 part 
  |-cs-root  253:0    0 34.4G  0 lvm  /
  `-cs-swap  253:1    0    4G  0 lvm  [SWAP]
sdb            8:16   0  100G  0 disk 
`-VDOexample 253:2    0  300G  0 vdo  /backups
sr0           11:0    1 1024M  0 rom  
  1. On Storware Backup & Recovery Node, stop vprotect-node service.

    [root@sbr-node ~]# systemctl stop vprotect-node
  2. Unmount VDO volume from backup destination path.

    [root@sbr-node ~]# umount /backups
  3. Convert VDO volume. Change /dev/sdb to the device on which you have created VDO.

    [root@sbr-node ~]# lvm_import_vdo /dev/sdb
    Convert VDO device "/dev/sdb" to VDO LV "vdovg/vdolvol"? [y|N]: Yes
    Stopping VDO VDOexample
    Converting VDO VDOexample
        Opening /dev/sdb exclusively
        Loading the VDO superblock and volume geometry
        Checking the VDO state
        Converting the UDS index
        Converting the VDO
        Conversion completed for '/dev/sdb': VDO is now offset by 2097152 bytes
    Physical volume "/dev/sdb" successfully created.
    Volume group "vdovg" successfully created
    WARNING: Logical volume vdovg/vdolvol_vpool not zeroed.
    Logical volume "vdolvol_vpool" created.
    WARNING: Converting logical volume vdovg/vdolvol_vpool to VDO pool volume WITHOUT formating.
    WARNING: Using invalid VDO pool data MAY DESTROY YOUR DATA!
    Logical volume "vdolvol" created.
    Converted vdovg/vdolvol_vpool to VDO pool volume and created virtual vdovg/vdolvol VDO volume.
  4. Rename volume group and logical volume names. They must be the same as the original VDO volume name.

    [root@sbr-node ~]# vgrename vdovg VDOexample
    Volume group "vdovg" successfully renamed to "VDOexample"
    [root@sbr-node ~]# lvrename /dev/VDOexample/vdolvol /dev/VDOexample/VDOexample
    Renamed "vdolvol" to "VDOexample" in volume group "VDOexample"
  5. Edit /etc/yum.repos.d/vProtect.repo and change baseurl to point to el9.

    [root@sbr-node ~]# vim /etc/yum.repos.d/vProtect.repo
    
    [vProtect]
    baseurl = http://repo.storware.eu/storware/current/el9
    gpgcheck = 0
    name = vProtect repo
  6. On Storware Backup & Recovery Server machine, create a vprotect database backup and copy it to safe place. Wait for all tasks to finish before stopping the vprotect-server service.

    [root@sbr-server ~]# stop systemctl vprotect-server
    [root@sbr-server ~]# /opt/vprotect/scripts/backup_db.sh
    [root@sbr-server ~]# cp /tmp/vprotect_db.sql.gz /root
  7. Login to mysql and execute below SQL query.

    [root@sbr-node ~]# mysql -uroot -p vprotect
    
    update filesystembackupdestination
    inner join backupdestination on filesystembackupdestination.guid = backupdestination.guid
    set filesystembackupdestination.dedupvolume = CONCAT('/dev/', REGEXP_REPLACE(backupdestination.name,'\\W','_'), '/', REGEXP_REPLACE(backupdestination.name,'\\W','_'))
    where filesystembackupdestination.dedupvolume is not null;
    
    MariaDB [vprotect]> quit
  8. Start vprotect-server service.

    [root@sbr-server ~]# systemctl start vprotect-server
  9. Proceed with the system upgrade of the Storware Backup & Recovery Node machine. After the reboot, you should have new LVM-VDO mounted on your backupdestination directory.

    [root@sbr-node ~]# lsblk
    NAME                               MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
    sda                                  8:0    0   40G  0 disk 
    ├─sda1                               8:1    0  600M  0 part /boot/efi
    ├─sda2                               8:2    0    1G  0 part /boot
    └─sda3                               8:3    0 38.4G  0 part 
    ├─cs-root                        253:0    0 34.4G  0 lvm  /
    └─cs-swap                        253:1    0    4G  0 lvm  [SWAP]
    sdb                                  8:16   0  100G  0 disk 
    └─VDOexample-vdolvol_vpool_vdata   253:2    0  100G  0 lvm  
    └─VDOexample-vdolvol_vpool-vpool 253:3    0  300G  0 lvm  
        └─VDOexample-VDOexample        253:4    0  300G  0 lvm  /backups
PreviousFile systemNextCatalogic Software vStor