NetBackup™ Web UI Cloud Administrator's Guide

Last Published:
Product(s): NetBackup (10.3.0.1, 10.3)
  1. Managing and protecting cloud assets
    1.  
      About protecting cloud assets
    2.  
      Limitations and considerations
    3. Configure Snapshot Manager in NetBackup
      1.  
        Add a Snapshot Manager
      2. Add a cloud provider for a Snapshot Manager
        1.  
          IAM Role for AWS Configuration
      3.  
        Associate media servers with a Snapshot Manager
      4.  
        Discover assets on Snapshot Manager
      5.  
        Enable or disable a Snapshot Manager
      6.  
        (Optional) Add the Snapshot Manager 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.  
      Cloud asset cleanup
    7.  
      Cloud asset filtering
    8.  
      AWS and Azure government cloud support
    9. 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
    10. About the NetBackup Accelerator for cloud workloads
      1.  
        How the NetBackup Accelerator works with virtual machines
      2.  
        Accelerator forced rescan for virtual machines (schedule attribute)
      3.  
        Accelerator backups and the NetBackup catalog
      4.  
        Accelerator messages in the backup job details log
    11.  
      Configuring backup schedule for cloud workloads
    12.  
      Backup options for cloud workloads
    13.  
      Snapshot replication
    14.  
      Configure AWS snapshot replication
    15.  
      Using AWS snapshot replication
    16.  
      Support matrix for account replication
    17.  
      Protect applications in-cloud with application consistent snapshots
    18. Protecting PaaS assets
      1.  
        Prerequisites for protecting PaaS assets
      2. Installing the native client utilities
        1.  
          Installing the MySQL client utility
        2.  
          Installing the sqlpackage client utility
        3.  
          Installing PostgresSQL client utility
        4.  
          Installing MongoDB client utility
        5.  
          Installing the Amazon RDS for Oracle client utility
      3.  
        Configuring the storage server for instant access
      4. Configuring storage for different deployments
        1.  
          For MSDP cloud deployments
        2.  
          For Kubernetes deployments
        3.  
          For VM-based BYO deployments
      5.  
        About incremental backup for PaaS workloads
      6.  
        Limitations and considerations
      7.  
        Discovering PaaS assets
      8.  
        Viewing PaaS assets
      9.  
        Managing PaaS credentials
      10.  
        View the credential name that is applied to a database
      11. Add credentials to a database
        1.  
          Creating an IAM database username
        2.  
          Configuring permissions for database user
        3.  
          Creating a system or user managed identity username
      12.  
        Add protection to PaaS assets
      13.  
        Perform backup now
  2. Recovering cloud assets
    1.  
      Recovering cloud assets
    2.  
      Perform rollback recovery of cloud assets
    3. Recovering PaaS assets
      1.  
        Recovering non-RDS PaaS assets
      2.  
        Recovering RDS-based PaaS asset
      3.  
        Recovering Azure protected assets
      4.  
        Recovering duplicate images from AdvancedDisk
  3. 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.  
      Performing steps after volume restore containing LVM
    9.  
      Troubleshooting
  4. Troubleshooting protection and recovery of cloud assets
    1.  
      Troubleshoot cloud workload protection issues
    2. Troubleshoot PaaS workload protection and recovery issues
      1.  
        Troubleshooting Amazon Redshift issues

Performing steps after volume restore containing LVM

You can perform steps after volume restore for the LVM volumes.

Note:

SFR (Single File Restore) or GRT (Granule Restore) and application restore is performed through the installed agents. But for volume recovery, it is necessary to make the associated file systems online after successful recovery.

To perform steps after volume restore

  1. Run the command to see all newly attached post volumes on to the host.PVS

    If there are duplicate PVs (a warning is displayed on the above command) then run,

    vgimportclone --import /dev/<Device1> /dev/<Device2> ... --basevgname <NewVGName>

    Else, find out the newly created Volume Groups (VG) on the host. If new VGs are not displayed then import the VG using the following command. It will discover new VG as <NewVGName>

    vgimport -a

    vgs

  2. Run below command to list all the logical volumes (new and old)

    lvs <NewVGName>

  3. Activate all the LVs belonging to <NewVGName> as,

    lvchange --activate y /dev/mapper/<NewVGName>-<LVName1>

    lvchange --activate y /dev/mapper/<NewVGName>-<LVName2>

    lvchange --activate y /dev/mapper/<NewVGName>-<LVNameN>

  4. Identify the UUID and file system of an authenticate and newly activated LV.

    blkid -p /dev/mapper/<NewVGName>-<LVName1> 

    Output: /dev/mapper/<NewVGName>-<LVName1>: 
UUID="2a4bdc14-b5eb-4ee6-b876-ebdcb66c55d9" 
BLOCK_SIZE="4096"TYPE="xfs" USAGE="filesystem"

    blkid -p /dev/mapper/<OldVGName>-<LVName1> 

    Output: /dev/mapper/<OldVGName>-<LVName1>: 
UUID="2a4bdc14-b5eb-4ee6-b876-ebdcb66c55d9" 
BLOCK_SIZE="4096"TYPE="xfs" USAGE="filesystem"
  5. If the UUID is the same, then you need to change it as follows

    File System

    Steps

    xfs

    mkdir <NewMountPoint>

    mount -o nouuid /dev/mapper/<NewVGName>-<LVName1> <NewMountPoint>

    umount <NewMountPoint>

    xfs_admin -U generate /dev/mapper/<NewVGName>-<LVName1>

    mount /dev/mapper/<NewVGName>-<LVName1> <NewMountPoint>

    ext2 / ext3/ ext4

    mkdir<NewMountPoint>

    tune2fs -U random /dev/mapper/<NewVGName>-<LVName1>

    mount /dev/mapper/<NewVGName>-<LVName1> <NewMountPoint>

  6. If the UUID is different, then run the following command.

    mount /dev/mapper/<NewVGName>-<LVName1> <NewMountPoint>