NetBackup™ Web UI RHV Administrator's Guide

Last Published:
Product(s): NetBackup (8.2)
  1. Introducing the NetBackup web user interface
    1.  
      About the NetBackup web user interface
    2.  
      Terminology
    3.  
      Sign in to the NetBackup web UI
  2. Managing RHV servers
    1.  
      Quick configuration checklist to protect Red Hat Virtualization virtual machines
    2. Configuring secure communication between the Red Hat Virtualization server and NetBackup host
      1.  
        ECA_TRUST_STORE_PATH for NetBackup servers and clients
      2.  
        ECA_CRL_PATH for NetBackup servers and clients
      3.  
        VIRTUALIZATION_HOSTS_SECURE_CONNECT_ENABLED for servers and clients
      4.  
        VIRTUALIZATION_CRL_CHECK for NetBackup servers and clients
    3.  
      About the ports that NetBackup uses to communicate with RHV
    4. Add or browse an RHV manager
      1.  
        Adding a backup host to the NetBackup master server
      2.  
        Remove an RHV manager
    5.  
      Create an intelligent VM group
    6.  
      Remove an intelligent VM group
    7.  
      Setting global limits on the use of RHV resources
  3. Protecting RHV virtual machines
    1.  
      Things to know before you protect RHV virtual machines
    2.  
      Protect RHV VMs or intelligent VM groups
    3.  
      Remove protection from VMs or intelligent VM groups
    4.  
      View the protection status of VMs or intelligent VM groups
  4. Recovering RHV virtual machines
    1.  
      Things to consider before you recover the RHV virtual machines
    2.  
      About the pre-recovery check
    3.  
      Recover an RHV virtual machine
    4.  
      About the supported virtual disk formats and disk provisioning during VM recovery
  5. Troubleshooting RHV VM protection and recovery
    1.  
      Troubleshooting tips for NetBackup for RHV
    2.  
      Error run into during the RHV virtual machines discovery phase
    3.  
      Error run into while backing up RHV virtual machines
    4.  
      Error run into while restoring RHV virtual machines
  6. API and command line options for RHV
    1. Using APIs and command line options to manage, protect, or recover RHV virtual machines
      1.  
        Additional information about the rename file
    2. Additional NetBackup options for RHV configuration
      1.  
        OVIRT_IMAGEIO_INACTIVITY_TIMEOUT option for NetBackup servers
      2.  
        RHV_CREATEDISK_TIMEOUT option for NetBackup servers
      3.  
        RHV_AUTODISCOVERY_INTERVAL option for NetBackup servers

About the supported virtual disk formats and disk provisioning during VM recovery

RHV supported allocation methods for virtual disks

RHV supports the following allocation methods for virtual disks:

  • Pre-allocated (Thick provision)

    Pre-allocated indicates fully-allocated raw disks.

  • Thin provision

    Thin provisioned disks are of the following types:

    • Raw sparse (default on file storage such as NFS)

    • QCOW2 (default on block storage such as FC, SAN, iSCSI)

    The thin provisioned virtual disk that is created on block storage is always in QCoW2 format.

Virtual disk provisioning for RHV VM recovery

Based on the disk provisioning option that you select in NetBackup, the virtual disks are created as described in the following table:

Table: Virtual disk provisioning for RHV VM recovery

The disk provisioning option that is selected during restore

Original disk format during backup

RAW sparse

RAW pre-allocated

QCOW2

Original or default

RAW sparse

(QCOW2 on block storage)

RAW pre-allocated

RAW sparse

(QCOW2 on block storage)

Thin

RAW sparse

(QCOW2 on block storage)

RAW sparse

(QCOW2 on block storage)

RAW sparse

(QCOW2 on block storage)

Thick

RAW pre-allocated

RAW pre-allocated

RAW pre-allocated

Disk formats for VM templates

  • VM templates can have the disks that have RAW or QCOW2 format.

  • Storage allocation can be thin (dependent) or clone (independent).

    In Clone (independent) allocation, the contents of template disks are copied to the VM disk.

    In Thin (dependent) allocation, the template disks are referred as base disks for the VM.

  • When multiple VMs are deployed from the same template with Thin allocation, then the VMs share the template disks.