NetBackup™ Web UI Cloud Object Store Administrator's Guide

Last Published:
Product(s): NetBackup & Alta Data Protection (10.2)
  1. Introduction
    1.  
      Overview of NetBackup protection for Cloud object store
    2.  
      Features of NetBackup Cloud object store workload support
  2. Managing Cloud object store assets
    1.  
      Prerequisites for adding Cloud object store accounts
    2.  
      Permissions required for Amazon S3 cloud provider user
    3. Adding Cloud object store accounts
      1.  
        Creating cross account access in AWS
      2.  
        Check certificate for revocation
      3.  
        Managing Certification Authorities (CA) for NetBackup Cloud
      4.  
        Adding a new region
    4.  
      Manage Cloud object store accounts
  3. Protecting Cloud object store assets
    1. About accelerator support
      1.  
        How NetBackup accelerator works with Cloud object store
      2.  
        Accelerator notes and requirements
      3.  
        Accelerator force rescan for Cloud object store (schedule attribute)
      4.  
        Accelerator backup and NetBackup catalog
    2.  
      About incremental backup
    3.  
      About policies for Cloud object store assets
    4.  
      Planning for policies
    5.  
      Prerequisites for Cloud object store policies
    6.  
      Creating a backup policy
    7.  
      Setting up attributes
    8.  
      Creating schedule attributes for policies
    9.  
      Configuring the Start window
    10.  
      Configuring exclude dates
    11.  
      Configuring include dates
    12.  
      Configuring the Cloud objects tab
    13.  
      Adding conditions
    14.  
      Adding tag conditions
    15.  
      Example of conditions and tag conditions
    16. Managing Cloud object store policies
      1.  
        Copy a policy
      2.  
        Deactivating or deleting a policy
      3.  
        Manually backup assets
  4. Recovering Cloud object store assets
    1.  
      Prerequisites for recovering Cloud object store objects
    2.  
      Recovering Cloud object store assets
  5. Troubleshooting
    1.  
      Recovery for Cloud object store using web UI for original bucket recovery option starts but job fails with error 3601
    2.  
      Recovery Job does not start
    3.  
      Restore fails: "Error bpbrm (PID=3899) client restore EXIT STATUS 40: network connection broken"
    4.  
      Access tier property not restored after overwrite existing to original location
    5.  
      Reduced accelerator optimization in Azure for OR query with multiple tags
    6.  
      Backup is failed and shows a certificate error with Amazon S3 bucket names containing dots (.)
    7.  
      Azure backup job fails when space is provided in tag query for either tag key name or value.
    8.  
      The Cloud object store account has encountered an error
    9.  
      Bucket list empty when selecting it in policy selection
    10.  
      Creating second account on Cloudian fails by selecting existing region
    11.  
      Restore failed with 2825 incomplete restore operation
    12.  
      Bucket listing of cloud provider fails when adding bucket in Cloud objects tab
    13.  
      AIR import image restore fails on the target domain if the Cloud store account is not added in target domain.

The Cloud object store account has encountered an error

Explanation

In web UI, the Cloud object store account status is shown as: The Cloud object store account has encountered an error, see user documentation, and re-create the account.

You cannot edit the Cloud object store account in this state. All jobs corresponding to the Cloud object store account keep failing.

Cause

The Cloud object store account goes to error state when:

  • The alias corresponding to Cloud object store account is accidentally deleted using csconfig CLI.

  • The alias corresponding to the Cloud object store account is accidentally updated using csconfig CLI.

Note:

It is recommended not to use csconfig CLI to update alias corresponding to Cloud object store account. Correct way to update the same is through the Edit workflow or create-or-update API. Alias with same name as Cloud object store account is the alias corresponding to Cloud object store account.

Workaround

The NetBackup domain name must be unique across Cloud object store account, Cloud storage server, or MSDP-C LSU. They share single namepace. Hence we can have following usage scenarios:

Case 1: When there is no valid Cloud storage server or MSDP-C LSU with same name as Cloud object store account in the environment.

  • Gather the Cloud object store account details as per your environment and cross-check the details obtained.

    • Optionally, if the Alias corresponding to the Cloud object store account exists, use csconfig CLI and note down details of alias.

      • Use following command to list all instances for the type and locate the Cloud object store account and its instance:

        <install-path>/csconfig cldinstance -i -pt <provider_type>

      • Use following command to get the details of instance and the Cloud object store account:

        <install-path>/csconfig cldinstance -i -in <instance name>

      • Validate the details with the gathered information.

      • Delete the Alias using following command:

        <install-path>/cscpnfig cldinstance -at <api_type> -rs -in <instance_name> -sts <cloud_object_store_account_name>

  • Delete the Cloud object store account which is in error state.

  • Create the Cloud object store account using the noted details.

Case 2: When you have valid and in use Cloud storage server or MSDP-C LSU with same name as Cloud object store account in the environment.

  • You cannot re-use the same name.

  • You need to gather the Cloud object store account details as per your environment.

  • Identify the new name for the Cloud object store account.

  • Delete the Cloud object store account which is in error state. Remove the account from the policy.

  • Create the Cloud object store account using new name and details gathered. Assign this account to the same policy that the old account used.

  • This changes the Client Name used for the bucket starting from the next backup onwards.

  • NetBackup identifies the old backups using the old account name.