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
  1. Deployment
  2. Backup Destinations
  3. File System

File system

PreviousisoLayer (Synthetic)NextVirtual Data Optimizer (VDO)

In this section, we'll show you how to set up a file system (it can be a local or remote file system, but this example assumes that you have a dedicated disk that you're going to use as a backup destination with a local XFS file system)

Note:

  • Any remote FS like NFS, SMB, etc. - needs to be mounted by the user, and the vprotect user/group must own the directories within the backup destination. Storware Backup & Recovery expects an already mounted file system and mount point in the backup destination.

  • You should add this file system to your /etc/fstab file on the node so that it gets mounted automatically if the OS is rebooted.

  • Consider using the same file system for the staging and backup destination (this boosts storage tasks, as no data needs to be copied again) - in such a scenario, the only difference would be that the presented /backupdestinationmount point becomes a subdirectory of the staging space (usually /vprotect_data/backups).

Preparation

  1. Log in to Storware Backup & Recovery Node and create the mount directory as in the example /backupdestination

    mkdir /backupdestination
  2. List all existing disks and find your drive:

    [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. Prepare a filesystem on it:

    mkfs.xfs -K /dev/sdc
  4. Add permission for the Storware Backup & Recovery user to access the directory /backupdestination

    • we assume here that you use a separate file system than your staging space

    • as an alternative, you also can point Storware Backup & Recovery to use a subdirectory on the same file system as your staging space, i.e. /vprotect_data/backups (which you probably don't have to initialize at this point, as you may have already prepared it in the , and you can just jump to the Web UI part in the next steps).

    chown vprotect:vprotect -R /backupdestination
  5. Add this line to the /etc/fstab file to automatically mount new the filesystem after reboot:

    /dev/sdc    /backupdestination    xfs    defaults 0 0

    or if you want to store backups on NFS share then it will look like this (where 10.50.1.28 is your host):

    10.50.1.28:/example_nfs_share /backupdestination nfs defaults  0 0
  6. Check if the fstab entry is OK and mount the filesystem:

    mount /backupdestination
  7. Log in to the Storware Backup & Recovery web UI.

  8. Go to Backup Destinations.

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

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

  11. You have to decide if your backup destination is a separate entity from the staging space.

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

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

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

      • In Storage paths type /vprotect_data/backups, where you point to a subdirectory (i.e. backups on your staging space path, i.e. /vprotect_data).

  12. Save the configuration.

Staging space configuration