NetBackup™ Web UI Cloud Administrator's Guide

Last Published:
Product(s): NetBackup & Alta Data Protection (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

Troubleshooting Amazon Redshift issues

Restore fails for Amazon Redshift, if the query string is larger than 100 KB

Explanation:

This is a known limitation of AWS. The maximum query statement size is 100 KB. See the AWS documentation for the details:

https://docs.aws.amazon.com/redshift/latest/mgmt/data-api.html

After a successful Redshift database restore, if the number of stored procedures, views, and functions are not the same with the source database.

Workaround:

Do the following:

  1. Mount the Instant Access (IA) path using the following API:

    netbackup/recovery/workloads/cloud/paas/instant-access-mounts

  2. Navigate to the mount path in the media server.
  3. Ensure that the mount path directory hierarchy is as follows:

    ClusterDirectory/DatabaseDirectory/DatabaseDirectory/SchemaDirectory/TableDirectory

  4. In the SchemaDirectory, locate the files StoredProcedures.json, Views.json, and Functions.json. Each of these files contains one or more SQL statements which you can run in Amazon Redshift Query Editor-2.

    Manually run these SQL statements.

botocore.exceptions.ClientError: An error occurred (InvalidSignatureException) when calling the ListDatabases operation

Explanation:

If the system time where you run the AWS Redshift APIs is not correct, you get this error. This message appears in the logs: 

Signature expired: 20230226T181919Z is now earlier than 20230226T181921Z (20230226T182421Z - 5 min.)"

Workaround:

Run the ntpdate command to fix the system time.

Backup or restore jobs fail with "NoCredentialsError: Unable to locate credentials" error.

Explanation:

This error appears when region is not specified. You can see the following error in the dbagentsutil logs. You can find the dbagentsutil logs at the following location:

/usr/openv/netbackup/logs/

Workaround:

Do the following:

  1. Download AWS CLI on the media server where the dbagent is running.
  2. Run the command:

    aws configure

  3. Enter the region name for EC2 when prompted. Do not specify the values for the other parameters.
Backup and restore stuck for Redshift databases

Explanation:

This error appears when the NetBackup Snapshot Manager that runs the discovery does not have access to the Redshift cluster. You can see the following error in the flexsnap logs:

Connect timeout on endpoint URL: "https://redshift.us-east-2.amazonaws.com/

Workaround:

Without access permission, the Snapshot Manager requires the inbound rules to be configured for the snapshot manager in the security group of the 'VPC endpoint of the Redshift service'.

On the AWS portal, select a cluster. Click Properties > click Network and security settings > click the virtual private cloud object > click Endpoints. Search for "redshift-endpoint" in the search field > click the VPC endpoint ID > click the Security Groups tab. Click the Security Group ID > click Edit Inbound rules, and add the following for media servers.

Type : HTTPS

Protocol : TCP

Port range : 443

Source : 10.177.77.210/32

* Here, the source refers to the media server instance.

Run discovery from NetBackup web UI again.