NetBackup™ Web UI Cloud Administrator's Guide

Last Published:
Product(s): NetBackup & Alta Data Protection (10.5)
  1. Managing and protecting cloud assets
    1.  
      About protecting cloud assets
    2.  
      Limitations and considerations
    3.  
      AWS and Azure government cloud support
    4. Configure Snapshot Manager in NetBackup
      1.  
        Add a Snapshot Manager
      2. Add a cloud provider for a Snapshot Manager
        1.  
          Adding a new region
        2.  
          IAM Role for AWS Configuration
        3.  
          IAM policy for OCI 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
    5. Managing intelligent groups for cloud assets
      1.  
        Considerations for cloud intelligent groups
      2.  
        Create an intelligent group for cloud assets
      3.  
        Delete an intelligent group for cloud assets
    6. Protecting cloud assets or intelligent groups for cloud assets
      1.  
        Customize or edit protection for cloud assets or intelligent groups
      2.  
        Remove protection from cloud assets or intelligent groups
    7. Managing policies for cloud assets
      1.  
        Limitations and considerations
      2. Add an SLP and cloud policy
        1.  
          Setting up attributes for IaaS cloud type
        2.  
          Setting up attributes for PaaS cloud type
        3. Creating schedule attributes for PaaS policy type
          1.  
            Configuring the Start window
          2.  
            Configuring the exclude dates
          3.  
            Configuring the include dates
        4.  
          Configuring the cloud assets for IaaS
        5.  
          Configuring the cloud assets for PaaS
        6.  
          Backup options for IaaS
      3.  
        Operations on cloud policy
      4.  
        PaaS and IaaS policy SLP configurations
    8. Scan for malware
      1.  
        Scanning backup images
      2.  
        Assets by workload type
    9. 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. 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 schedules for cloud workloads using protection plan
    12.  
      Backup options for cloud workloads
    13. AWS Snapshot replication
      1.  
        Configure AWS snapshot replication
      2.  
        Using AWS snapshot replication
      3.  
        Support matrix for account replication
    14.  
      Protect applications in-cloud with application-consistent snapshots
    15. 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 PostgreSQL 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.  
        Prerequisites for protecting Amazon RDS SQL Server database assets
      5. Configuring storage for different deployments
        1.  
          For MSDP cloud deployments
        2.  
          For Kubernetes deployments
        3.  
          For VM-based BYO deployments
      6.  
        About incremental backup for PaaS workloads
      7.  
        Configuring incremental backups for Azure MySQL server
      8.  
        About archive redo log backup for PaaS workloads
      9.  
        About Auto Image Replication for PaaS workloads
      10.  
        Limitations and considerations
      11.  
        Discovering PaaS assets
      12.  
        Viewing PaaS assets
      13.  
        Managing PaaS credentials
      14.  
        View the credential name that is applied to a database
      15. Add credentials to a database
        1.  
          Creating an IAM database username
        2.  
          Configuring permissions for the database user
        3.  
          Creating a system or user-managed identity username
      16.  
        Add protection to PaaS assets
      17.  
        Perform backup now
    16.  
      Protecting AWS or Azure VMs for recovering to VMware
    17.  
      Cloud asset cleanup
    18.  
      Cloud asset filtering
  2. Recovering cloud assets
    1. Recovering cloud assets
      1.  
        About the pre-recovery check for VMs
      2.  
        Supported parameters for restoring cloud assets
      3.  
        Restoring to a different cloud provider
      4.  
        Recovering virtual machines
      5.  
        Recovering applications and volumes to their original location
      6.  
        Recovering applications and volumes to an alternate location
      7.  
        Additional steps required after restoring an AWS RDS database instance
      8.  
        Recovery scenarios for GCP VMs with read-only volumes
      9.  
        (GCP only) Restoring virtual machines and volumes using the autoDelete disk support
    2.  
      Perform rollback recovery of cloud assets
    3. Restore to a different cloud provider
      1.  
        Prepare the VMs for back up
      2.  
        Post-restore configurations
    4. Recovering AWS or Azure VMs to VMware
      1.  
        Post-recovery considerations for cloud VMs recovered to VMware
      2. Steps to recover images from cloud VMs to VMware
        1.  
          Recovering images from AWS to VMware
        2.  
          Recovering images from Azure to VMware
    5. Recovering PaaS assets
      1.  
        Recovering non-RDS PaaS assets
      2.  
        Recovering Redshift clusters
      3.  
        Recovering RDS-based PaaS asset
      4.  
        Recovering Azure-protected assets
      5.  
        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.  
      Error Code 9855: Error occurred while exporting snapshot for the asset: <asset_name>
    3.  
      Backup from snapshot jobs take longer time than expected
    4.  
      Backup from snapshot job fails due to connectivity issues when Snapshot Manager is deployed on an Ubuntu host
    5.  
      Error disambiguation in NetBackup UI
    6.  
      Status Code 150: Termination requested by administrator
    7. Troubleshoot PaaS workload protection and recovery issues
      1.  
        Troubleshooting Amazon Redshift issues

Prepare the VMs for back up

This section describes the considerations and prerequisites to back up the VMs for restoring to a different cloud platform. The process is different for different operating systems, depending on the cloud service to which you want to restore.

RHEL

Target: AWS

  1. Install the required Xen and Nitro drivers:
    • If drivers are not installed, then install them by running the following commands:

    • Validate if the drivers are installed successfully by running the following command:

      lsinitrd | grep -i -e nvme -e ena -e xen

  2. To avoid mount failures, it is recommended to replace the device names with UUID in /etc/fstab file.

    Back up the original fstab file and comment out Azure-specific entries, and other non-critical entries which might cause boot failures after restore. Alternatively, you can add nofail in fstab file for these entries.

  3. Create a root user password.
  4. Configure or obtain the root user credentials, if the VM is configured with key based logon.

    To use the key based logon, perform the following:

    • Back up the original /root/.ssh/authorized_keys.

    • The /root/.ssh/authorized_keys contains the same public key as azureuser, but cannot log on using the root user and key due to the following command present in authorized_keys for the root user and the associated key:

      `echo 'Please login as the user \"azureuser\" rather than the user \"root\".';echo;sleep 10;exit 142`

      Note:

      This is applicable for Azure-created keys and user-provided keys.

      You must delete the command to let the root logon work after restore.

    • After editing, the entry appears as follows:

      cat /root/.ssh/authorized_keys
      no-port-forwarding,no-agent-forwarding,no-X11-forwarding, ssh-rsa AAAAB3Nza..<truncated>..HruCzDsb3j

Target: Azure

  1. AWS instances have Hv and NVMe drivers preinstalled and hence no additional steps are required. Confirm if the drivers exist in your instance, run the command:

    lsinitrd | grep -i -e hv -e nvme

  2. Replace the device names with UUID in /etc/fstab file.

SLES

Target: AWS

By default, AWS uses SUSE kernel. Hence install the SUSE kernel and select it at the boot time from the GRUB menu on the restored VM as follows:

  1. Refer to the following documentation for more information on entries in zypp.conf file as it may affect the number of kernels retained and their behavior:

    Installing multiple kernel versions

    Proceed with the next steps after ensuring that the SUSE computer can work with multiple kernels.

  2. Run the following command to list the available kernels:

    zypper se -s 'kernel*'

  3. From the list of kernels displayed in the above step, install a suitable default kernel version:

    zypper in kernel-default-<VERSION>

    For example, zypper in kernel-default-5.3.18-53.3

  4. List the installed kernels and kernel modules using the following command:

    zypper se -si 'kernel*'

  5. It is recommended to set a root user password.
  6. If the required drivers are not installed, then install them by running the following commands:
    • lsinitrd --kver <YOUR NEW KERNEL VERSION> | grep xen

    • Update/Create the /etc/dracut.conf file with the following line:

      add_drivers+="xen-blkfront xen-netfront nvme-core nvme"

    • Run the following command:

      dracut -f -v

    • dracut -f -v --kver <YOUR NEW KERNEL VERSION>

    • lsinitrd --kver <YOUR NEW KERNEL VERSION> | grep xen

    <YOUR NEW KERNEL VERSION> is the new kernel version installed in Step 3 above.

  7. Back up the /etc/default/grub file. Edit the original grub file, add GRUB_TIMEOUT and GRUB_TIMEOUT_STYLE entries and comment out the following parameters:

    GRUB_HIDDEN_TIMEOUT

    GRUB_HIDDEN_TIMEOUT_QUIET

    By default, GRUB_DEFAULT is set to 0 in the /etc/default/grub file. Change the default value so that it loads Azure kernel on restart and not the newly installed kernel.

    • For example, GRUB_DEFAULT='1>KERNEL_INDEX' where KERNEL_INDEX can be found with grub2-mkconfig command or by analyzing /boot/grub2/grub.cfg file.

    • Updating GRUB_DEFAULT ensures that the source VM keeps using Azure kernel, in an event, where it is restarted while the new kernel is installed.

    • The GRUB config file has entries similar to the following:

      #GRUB_HIDDEN_TIMEOUT= 
      #GRUB_HIDDEN_TIMEOUT_QUIET=true 
      GRUB_DEFAULT'1><YOUR KERNEL INDEX NUMBER>' 
      GRUB_TIMEOUT=20 
      GRUB_TIMEOUT_STYLE=menu
    • Update the GRUB config file using the following command:

      grub2-mkconfig -o /boot/grub2/grub.cfg

    • After restore, to access GRUB menu during restart, press ESC twice during the countdown on EC2 Serial Console.

    For more information on GRUB entries, refer to Simple configuration handling

Target: Azure

  1. Run the following command to verify if the drivers are preinstalled:

    lsinitrd | grep -i -e hv -e nvme

  2. It is recommended to replace the device names with UUID in /etc/fstab file.
Ubuntu

Target: AWS

  1. Run the following command to install the linux-aws kernel package:

    sudo apt-get update && sudo apt-get upgrade -y linux-aws

  2. Change grub countdown style and increase time-out in /etc/default/grub file. This enables the user to enter the recovery mode if issues are faced during the restart:

    GRUB_TIMEOUT_STYLE=menu

    GRUB_TIMEOUT=20

  3. To avoid loading the new kernel on restart, ensure that the default kernel entry (GRUB_DEFAULT) in the grub configuration file is pointing to Azure-specific kernel and not the newly installed kernel.
  4. Run the following command to update grub file:

    update-grub

Target: Azure

  1. Run the following command to verify if the drivers are preinstalled:

    lsinitrd | grep -i -e hv -e nvme

  2. It is recommended to replace the device names with UUID in /etc/fstab file.

Windows

Target: AWS

  1. Check the boot mode (Legacy or UEFI).
  2. Run the following:

    (Ctrl + R) -> MSInfo32.exe → BIOS Mode

  3. Install the following drivers: