NetBackup™ Web UI Cloud Administrator's Guide

Last Published:
Product(s): NetBackup & Alta Data Protection (11.0)
  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. About storage lifecycle policies
      1.  
        Adding an SLP
      2.  
        SLP configurations for PaaS and IaaS policies
    8. Managing policies for cloud assets
      1.  
        Limitations and considerations
      2.  
        Planning for policies
      3.  
        Creating policies for cloud assets
      4.  
        Setting up attributes for PaaS assets
      5.  
        Setting up attributes for IaaS assets
      6.  
        Creating schedules
      7.  
        About backup frequency
      8.  
        About assigning retention periods
      9. Configuring the Start window
        1.  
          Example of schedule duration
      10.  
        Configuring the include dates
      11.  
        Configuring the exclude dates
      12.  
        Configuring the cloud assets for PaaS
      13.  
        Configuring the cloud assets for IaaS
      14.  
        Configuring backup options for IaaS
      15. Managing cloud policies
        1.  
          Copy a policy
        2.  
          Deactivating or deleting a policy
        3.  
          Manually backup assets
    9. Scan for malware
      1.  
        Scanning backup images
      2.  
        Assets by workload type
    10. 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
    11. 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
    12.  
      Configuring backup schedules for cloud workloads using protection plan
    13.  
      Backup options for cloud workloads
    14. AWS Snapshot replication
      1.  
        Configure AWS snapshot replication
      2.  
        Using AWS snapshot replication
      3.  
        Support matrix for account replication
    15.  
      Protect applications in-cloud with application-consistent snapshots
    16.  
      Protecting AWS or Azure VMs for recovering to VMware
    17.  
      Cloud asset cleanup
    18.  
      Cloud asset filtering
  2. Protecting PaaS assets
    1.  
      Protecting PaaS assets
    2.  
      Prerequisites for protecting PaaS assets
    3.  
      Enabling binary logging for MySQL and MariaDB databases
    4.  
      Enabling backup and restore in Kubernetes
    5.  
      Prerequisites for protecting Amazon RDS SQL Server database assets
    6. Protecting RDS Custom instances
      1.  
        Protecting RDS Custom for SQL Server assets
      2.  
        Consideration for protecting RDS Custom for SQL Server assets
      3.  
        Protecting RDS Custom for Oracle assets
      4.  
        Consideration for protecting RDS Custom for Oracle assets
    7. Protecting Azure Managed Instance databases
      1.  
        Prerequisites for protecting Azure Managed Instance databases
      2.  
        Permissions required for protecting Azure Managed Instance databases
    8. Limitation and considerations
      1.  
        For all databases
      2.  
        For PostgreSQL
      3.  
        For incremental backups for Azure PostgreSQL
      4.  
        For AWS RDS PostgreSQL and AWS Aurora PostgreSQL
      5.  
        For AWS DynamoDB
      6.  
        For AWS DocumentDB
      7.  
        For AWS Neptune
      8.  
        For AWS RDS SQL
      9.  
        For Azure, AWS RDS, and Aurora MySQL
      10.  
        For incremental backups using Azure MySQL server
      11.  
        For incremental backups using the GCP SQL Server
      12.  
        For Azure SQL and SQL Managed Instance
      13.  
        For Azure SQL and SQL Managed Instance (without temp. database)
      14.  
        For Azure SQL Server and SQL Managed Instance incremental backup
      15.  
        For Azure Cosmos DB for MongoDB
      16.  
        For Azure Cosmos DB for NoSQL
      17.  
        For Amazon RDS for Oracle
      18.  
        For Amazon Redshift databases
      19.  
        For Amazon Redshift clusters
      20.  
        For GCP SQL Server
      21.  
        For GCP BigQuery
    9. 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
    10. Configuring storage for different deployments
      1.  
        For MSDP cloud deployments
      2.  
        For Kubernetes deployments
      3.  
        For VM-based BYO deployments
    11.  
      Configuring the storage server for instant access
    12.  
      About incremental backup for PaaS workloads
    13.  
      Configuring incremental backups for Azure MySQL server
    14.  
      About archive redo log backup for PaaS workloads
    15.  
      About Auto Image Replication for PaaS workloads
    16.  
      Discovering PaaS assets
    17.  
      Viewing PaaS assets
    18. Managing PaaS credentials
      1.  
        View the credential name that is applied to a database
      2.  
        Add credentials to a database
      3.  
        Creating an IAM database username
      4.  
        Creating a system or user-managed identity username
      5.  
        Configuring permissions for the database user
    19. Add protection to PaaS assets
      1.  
        Perform backup now
  3. Recovering cloud assets
    1. Recovering cloud assets
      1.  
        About the pre-recovery check for VMs
      2.  
        Supported parameters for restoring cloud assets
      3.  
        Recovering virtual machines
      4.  
        Recovering applications and volumes to their original location
      5.  
        Recovering applications and volumes to an alternate location
      6.  
        Recovery scenarios for GCP VMs with read-only volumes
      7.  
        (GCP only) Restoring virtual machines and volumes using the autoDelete disk support
    2.  
      Perform rollback recovery of cloud assets
    3. 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
    4. Recovering PaaS assets
      1.  
        Recovering non-RDS PaaS assets
      2.  
        Recovering Redshift clusters
      3.  
        Recovering AWS DocumentDB and Neptune assets
      4.  
        Recovering RDS-based PaaS asset
      5.  
        Recovering Azure-protected assets
      6.  
        Recovering duplicate images from AdvancedDisk
  4. 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
  5. 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.  
      VMs and other OCI assets with CMK-encrypted disks are marked as deleted in NetBackup UI.
    4.  
      Backup from snapshot jobs take longer time than expected
    5.  
      Backup from snapshot job fails due to connectivity issues when Snapshot Manager is deployed on an Ubuntu host
    6.  
      Error disambiguation in NetBackup UI
    7.  
      Status Code 150: Termination requested by administrator
    8. Troubleshoot PaaS workload protection and recovery issues
      1.  
        Troubleshooting Amazon Redshift issues
      2.  
        Troubleshooting Azure Postgres issues
      3.  
        Troubleshooting Amazon RDS Custom for SQL issues

Troubleshooting

Troubleshooting snapshot restore process for Microsoft Azure cloud

When you start a subsequent (twice) restore operation on the same VM, an error occurs during a restore operation. This error causes the following issues:

  • The tags from the original OS disk are not copied to the newly created restored OS disk.

  • User logon might fail after the VM restore due to SSH failure.

Workaround:

Check if the SSH daemon is running on the system. If not, then perform the steps in the following article.

learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/troubleshoot-ssh-connection

Filtering unsupported files and folders

If you try to restore files or folders from a partition or a file system that Snapshot Manager does not support, then you get the following error in the restore job.

Error nbcs (pid=<processs id>) Failed to restore file(s) and folder(s) from snapshot for asset <asset name>

Workaround:

You can filter any files or folders that Snapshot Manager does not support. In the bp.conf file on the primary server, enable the CP DISKMAP check by setting the following flag.

CP_DISKMAP_CHECK = true/yes

Backup from restore operation is partially successful

Backup from restore operation is partially successful when disk is full on the selected target directory. The following messages are displayed:

Dec 29, 2022 2:57:51 PM - Info nbcs (pid=2244) Granular restore(SFR) is completed
    Dec 29, 2022 2:57:51 PM - Info nbcs (pid=2244) Summary of SFR Operation - Success files/folders count: 0 , 
    Failed files/folders count: 1 , Warning files/folders 
    count: 0, Skipped files/folders count: 0
    Dec 29, 2022 2:57:51 PM - Info nbcs (pid=2244) 
    Detailed restore summary report is available on recovery target host at location: 
    /var/log/flexsnap/restore/granular-restore-09b4d44d
    .
    .
    Dec 29, 2022 2:57:51 PM - Warning bprd (pid=1977) Granular Restore from backup completed with error. 
    Copy the files manually from live access mount: 
    ip-10-239-185-241:/mnt/vpfs_shares/vmfiles/8fcc/8fcc132b-a202-49a8-b654-81ff242a718a/livemount
    Dec 29, 2022 2:57:51 PM - end Restore; elapsed time 0:01:51
    the requested operation was partially successful(1)

For a backup from restore, if a live mount is created successfully, then even if other errors are reported apart from ASSET_NOT_FOUND, it is considered as partial success. If no network devices or a file system are mounted on the target location, or the disk is full, the following messages are displayed in the job details:

 Jan 02, 2023 12:11:16 AM - Error nbcs (pid=13934) 
187776K space required for file/folder restore while 20K is total available space on /disk1

In this case, other network devices or the file system must have been mounted on the target path, hence the Snapshot Manager agent considers the free space on the device or file system. As the copy fails with space error, it is logged into the summary report. For example:

 /var/log/flexsnap/restore/granular-restore-09b4d44d in above Job details log

Workaround:

  • Check the summary report on the target-host location. For example,

    /var/log/flexsnap/restore/granular-restore-09b4d44d
    [root@ip-10-239-187-148 granular-restore-09b4d44d]# cat root-error.log
    Dec 29 09:27:44: ERROR - FILE: /disk1/dl380g9-149-vm15_package.zip
    [Error 28] IOError: No space left on device
  • If the file copy operation failed due to disk space, then create some space and copy the file from live mount.

    The live mount path details can be found in the job details as follows:

    Dec 29, 2022 2:57:51 PM - Warning bprd (pid=1977) Granular Restore from backup completed with error. 
    Copy the files manually from live access mount: 
    ip-10-239-185-241:/mnt/vpfs_shares/vmfiles/8fcc/8fcc132b-a202-49a8-b654-81ff242a718a/livemount
Partial recovery is observed when the user selects a disconnected target virtual machine

Partial recovery may be due to the following reasons:

  • If the target virtual machine is disconnected (no connectivity through an agent).

  • If any failure is seen during the copy of files or folders on the target virtual machine.

  • When a Windows virtual machine content is restored on a Linux target virtual machine.

In these partial recovery cases, the created instant access is not deleted and is available for the next 24 hours.

You can configure the instance access retention interval using the CLOUD_VM_IA_RETENTION_INTERVAL_IN_HOURS parameter in the bp.conf file. (Default value is 24 hours.)

Workaround:

User can perform manual steps to access the instant access share on the target host and then manfully copy the required files or folders.

(Copy files over NFS) To restore Linux image content on a Linux host:

  • To mount an NFS share on a Linux system, install the NFS client package using the following command:

    $ sudo yum install nfs-utils

  • Using the following mount command, mount the Instant access on the target Linux host:

    # Create a directory say /mnt/restore
    
    $ mkdir -p /mnt/restore
    
    # Mount the instant access 
    
    $ mount -t nfs <InstantAccessServer:InstantAccessPath> /mnt/restore
  • Instant access path can be retrieved from activity manager logs which is in the following format:

    <InstantAccessServer>:/mnt/vpfs_shares/vmfiles/<id>/<InstantAccessId>/livemount

(SMB access) To restore Windows image contents (with ACL) on Windows target host:

  • SMB credentials of MSDP storage server of source virtual machine image must be added to the Windows credential manager.

  • Use the given live mount to access virtual hard disks by navigating to Activity Monitor > Job details.

    The virtual hard disks are listed under the folder with vhd_ as the prefix.

  • From the Action tab, attach the required virtual hard disk and click on OK.

  • Select Assign the following drive letter option to assign the letter to virtual disk to browse data and click on OK.

  • Navigate to the assigned drive in the previous step and copy the data manually.

(Live mount) To restore Windows image contents on a Linux target host:

  • Linux must have the CIFS package. Obtain the packages using the # yum install cifs-utils command.

  • Create the mount directory using the # mkdir <my_mount_dir> command.

  • Use your Samba username and password to mount the exported path as follows:

    mount -t cifs -o username=<sambauser> //<InstantAccessServer>/<InstantAccessPath> <my_mount_dir>

  • Copy the files using the following command:

    # cp <my_mount_dir>/<file_path> <target_dir_path>

Issues with single file restore from the backup of a snapshot

Issue/Error

Description

Workaround

Log path to check

For information related to restore details on the target host, check the following logs:

  • For agentless:

    /opt/VRTScloudpoint/.agent/flexsnap-agentless-onhost.log

  • For on-host agent:

    /var/log/flexsnap/flexsnap-agentless-onhost.log

  • For single file restore specific logs, use the path provided in the Activity monitor.

To resolve the failures or any exceptions that occurred during the single file restore on Snapshot Manager, refer to the following logs on the Snapshot Manager host:

/cloudpoint/logs/flexsnap.log

Pre-recovery check fails

When restoring files and folders to the disconnected target virtual machine, the pre-recovery check fails with the following error:

Target VM state: Target VM <vm_name> has no agent configured

If recovery is started, the restore operation is partially successful.

Ensure that the target virtual machine is connected to the agent configured for successful restore.

Partial recovery for source Linux VM to target Windows VM (no NFS client)

If you do not install the NFS client on the Windows target computer, a restore of files and folders from a source Linux VM is partially successful. The following error displays:

Error nbcs (pid=42513) Invalid operation for asset: <asset_id> Warning bprd (pid=42045) Granular Restore from backup completed with error. Copy the files manually from live access mount: <livemount_path>. Note that live access mount is available only for 24 hrs.

Install the NFS client on the Window target computer before you perform the restore from a Linux VM to a Windows VM.

Restore job fails for deleted target VM

The restore job fails with the following error when restoring files and folders to the target VM which is deleted from the cloud environment:

Error nbcs (pid=44859) Target VM not found, asset_id <asset_id>

Select a different target VM.

Creating instant access fails

If instant access is not enabled on the MSDP storage server, the creation of the instant access fails during the restore job.

Verify if instant access is supported on the MSDP media server. Run the following pre-check script:

/usr/openv/pdde/vpfs/bin/ia_byo_precheck.sh

Target VM does not have the free drives to attach to the virtual disk

If the number of volumes that contain the selected file(s) is more than the number of free available drives on the target host, the operation fails.

Select a smaller number of volumes for the restore.

Not enough space: '*\\driverMapping.json

The media server where MSDP is configured has FIPS enabled.

Disable FIPS on the media server where MSDP is installed. Or, add the domain user Samba credentials to the target VM.

Issue with Azure cloud provider VMs

If any one of the disks in the VM is not initialized, download or restore of the VM 's files using instant access fails with the following error:

Jan 24, 2023 11:58:47 AM - Error NBWMC (pid=3716) Internal Error: ('failed to find operation system information, please check the source VM', ('Failed to expose 
VMDK', 1006), None)
Failed to create the instant access mount.
(4001)

libguestfs is a third-party tool that instant access uses to retrieve files from a VM backup. If a disk is not initialized, libguestfs cannot retrieve the files.

Workaround:

Initialize the disk and back up the VM. Then try again to download or restore the VM files using instant access.

Issues in snapshot restore from OCI
Invalid target path. Both the source and destination disks are boot disks, or the disks are mounted on /dev/oracleoci/oraclevda

This error occurs when you try granular restore from a snapshot with at least one of the selected files from the boot volume, and the destination volume of restoration being a boot volume.

Workaround:

To restore files and folders from the boot volume or file system, specify a block volume as the target path.

The selected files/folders were skipped from recovery as the snapshot does not contain the corresponding file system.

During granular restore from snapshot, this error occurs for VMs that do not have the Oracle Cloud Agent installed, or have the disks attached using the paravirtualized attachment method.

Error in the Activity monitor:

[{'error': 'The selected files/folders were skipped from recovery as the snapshot does not contain the corresponding file system.', 'mount': 'Unknown Mount Point/Drive'}]}}"

Workaround:

Do the following:

  • Install the Oracle Cloud Agent if it is supported on the platform by Oracle. Or, attach all the disks using iSCSI attachment type, including the boot disk.

  • Wait for the discovery to complete and retry the backup.

Granular restore from snapshot copy fails with the error "Block Volume Plug-in: must be enabled on the instance…"

This error occurs when the Block Volume Management plug-in for the Oracle Cloud Agent is not enabled on the target VM.

Workaround:

Do the following:

  1. Enable the Block Volume Management plug-in from the OCI Console, in the target VM. 

  2. Restart the VM.

  3. Try to restore again.