NetBackup™ Web UI Cloud Administrator's Guide

Last Published:
Product(s): NetBackup (9.1)
  1. Introducing the NetBackup web user interface
    1.  
      About the NetBackup web UI
    2.  
      Terminology
    3.  
      Sign in to the NetBackup web UI
    4.  
      Sign out of the NetBackup web UI
  2. Monitoring NetBackup
    1.  
      The NetBackup dashboard
    2.  
      Monitoring jobs
    3.  
      Filter jobs in the job list
  3. Managing and protecting cloud assets
    1.  
      About protecting cloud assets
    2.  
      Limitations and considerations
    3. Configure CloudPoint servers in NetBackup
      1.  
        Configure a third-party CA certificate
      2.  
        Add a CloudPoint server
      3. Add a cloud provider for a CloudPoint server
        1.  
          IAM Role for AWS Configuration
      4.  
        Associate media servers with a CloudPoint server
      5.  
        Discover assets on CloudPoint server
      6.  
        Edit a CloudPoint server
      7.  
        Enable or disable a CloudPoint server
      8.  
        (Optional) Add the CloudPoint extension
    4. Managing intelligent cloud groups
      1.  
        Create an intelligent cloud group
      2.  
        Delete an intelligent cloud group
    5. Protecting cloud assets or intelligent cloud groups
      1.  
        Customize or edit protection for cloud assets or intelligent groups
      2.  
        Remove protection from cloud assets or intelligent groups
    6.  
      AWS and Azure government cloud support
    7. About protecting Microsoft Azure resources using resource groups
      1.  
        Before you begin
      2.  
        Limitations and considerations
      3. About resource group configurations and outcome
        1.  
          Examples of resource group configurations
      4.  
        Troubleshoot resource group permissions
    8.  
      Configuring backup schedule for cloud workloads
    9.  
      Backup options for cloud workloads
    10.  
      Configure snapshot replication
    11.  
      Protect applications in-cloud with application consistent snapshots
  4. Recovering cloud assets
    1.  
      Recovering cloud assets
    2.  
      Perform rollback recovery of cloud assets
  5. Performing granular restore
    1.  
      About granular restore
    2.  
      Supported environment list
    3.  
      List of supported file systems
    4.  
      Before you begin
    5.  
      Limitations and considerations
    6.  
      Restoring files and folders from cloud virtual machines
    7.  
      Restoring volumes on cloud virtual machines
    8.  
      Troubleshooting
  6. Troubleshooting protection and recovery of cloud assets
    1.  
      Troubleshoot cloud workload protection issues

Limitations and considerations

Consider the following important points for granular restore.

  • After a restore job is completed, you cannot expand the directories in the File List section of the restore job.

  • If adequate space is not available on the target location, the restore operation fails before the copy operation begins.

  • In the activity monitor summary, when the restore job starts it shows the current file which is the first entry in the restore items. After the job is complete, the summary goes blank.

  • Bytes transferred and estimated bytes in activity monitor are not updated and shown as 0.

  • The maximum number of indexing jobs that CloudPoint supports is limited based on the following conditions:

    • The number of attachment points for a data disk available on the CloudPoint host minus 1 and the instance type. CloudPoint metadata volume consumes this one attachment point.

    • The resource availability of the CPU or memory of the CloudPoint machine.

  • The ephemeral storage devices like Amazon AWS instance store volumes and Microsoft Azure temporary disks are ignored when a snapshot is performed. These devices are also ignored for indexing as well.

  • The file systems that are created on LVM or LDM disks are ignored when host consistent snapshots are created and indexed.

  • Granular restore is not supported for the file systems and destination hosts that are created on LVM, LDM, storage pool, all variants of FAT, and volumes without drive letters.

  • If any unsupported file systems are present on the host, the host can't be added to the protection plan that is created for granular restore. The protection plans for granular restore have the Enable granular recovery for files or folders check box value set to true.

  • CloudPoint communicates the number of index jobs that can be run to NetBackup. NetBackup then throttles the requests. By default, the number of index jobs is initialized to 2. Post discovery of CloudPoint host capabilities, it is increased to number of disk slots available. However, you can update the value for indexing max_jobs=<value> in flexsnap.conf file to override this limit.

  • CloudPoint host limits the number of disk slots that the cloud providers enforce. NetBackup throttles the indexing requests to CloudPoint. To achieve this request, during Cloud Asset discovery process, NetBackup fetches CloudPoint host capabilities. These capabilities include the Max no of index jobs parameter. This parameter is used to limit the requests that are sent to CloudPoint and index job queue in NetBackup. By default, the maximum number of parallel indexing jobs is 2. But once the cloud plug-in is configured which discovers the CloudPoint host, the capability API fetches the number of max jobs based on attachment points and available resources. You can set the limit by adding the indexing max_jobs=x entry in the config file of the CloudPoint host. If the CloudPoint host receives number of indexing requests more than its capability, the requests are queued.

  • When an indexing operation is in progress, if any OS errors occur while crawling files, directories, or other entries, the errors are ignored and the indexing operation continues. To restore the missing files, you must initiate the granular restore operations on the parent folder.

  • If a mount point is not visible in the tree on the left panel for browsing when you add files or folders from the recovery point, it can be because of the following reasons:

    • The "/" (root file system) is on an LVM, and

    • The mount point is not directly related to "/" (root file system)

    In this scenario, search for the mount point from the right panel and then restore the files or folders successfully.

    For example, if a disk is mounted on /mnt1/mnt2 where /mnt1 is any directory on the "/" (root FS which is on LVM setup) and mnt2 is a mount point inside mnt1, the "mnt2" is not visible in the tree on the left panel. However, you can search and restore files or folders inside mount point.

  • To restore files and folders from VM snapshot recovery points, the /etc/fstab file on the Linux servers, must have entries based on the file system UUID, instead of device paths. The device paths can change depending on the order in which Linux discovers the devices during system boot.

  • While restoring application or file systems from one OS version to another OS version, refer to the OS and application vendor's compatibility matrix. Restore of file system from higher version to lower version is not recommended.

  • While restoring a drive as source to an alternate folder as destination, the user group cannot perform the write operation on the newly created folder due to lack of the write permission.