NetBackup™ Web UI Cloud Object Store Administrator's Guide

Last Published:
Product(s): NetBackup (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.

Planning for policies

Policy configuration is flexible enough to meet the various needs of all the Cloud object store accounts in a NetBackup environment. To take advantage of this flexibility, take time to plan before starting to configure the policies.

The following table outlines the steps to take to ensure that you get optimal results from your policy configurations.

Table: Steps for planning policies

Step

Action

Description

Step 1

Gather information about the Cloud object store account.

Gather the following information about each bucket/container:

  • The Account name: Credential and connection details mentioned in account are used to access cloud resources using REST APIs during backup. An account is associated with a single region, hence a policy can contain bucket/containers associated with that region only.

  • The bucket/container names

  • The approximate number of objects on each bucket/container to be backed up.

  • The typical size of the objects.

One account may contain a large amount of data in number of objects, while the other accounts are smaller with lesser number of objects. To avoid long backup times, include the larger account in one policy and the smaller one in another policy. It may be beneficial to create more than one policy for the larger account.

Step 2

Group the objects based on backup requirements

Divide the different objects in the accounts into groups according to the different backup and archive requirements.

Step 3

Consider the storage requirements

The NetBackup environment may have some special storage requirements that the backup policies must accommodate.

The storage unit and volume pool settings apply to all the objects that are backed up by a policy. If objects have special storage requirements, create separate policies for the objects, even if other factors are the same, such as schedules.

Step 4

Consider the backup schedule

Create additional backup policies if the schedules in one policy do not accommodate all objects and objects in an account.

Consider the following factors when deciding to create additional policies:

  • Best times for backups to occur.

    To back up different objects on different schedules may require additional policies with different time schedules. For example, create different policies for night-shift and day-shift objects.

  • How frequently the objects change.

    If some objects change more frequently than others, the difference may be enough to warrant creating another policy with a different backup frequency.

  • How long backups need to be retained.

    Each schedule includes a retention setting that determines how long NetBackup keeps the objects that are backed up by the schedule. Because the schedule backs up all the objects in the backup selection list, all objects should have similar retention requirements. Do not include the objects whose full backups must be retained forever, together in a policy where full backups are retained for only four weeks.

Step 5

Select exactly what to backup.

You do not need to backup entire objects, unless required. Create queries to select and back up only the required object(s).