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.

Accelerator notes and requirements

Note the following about the NetBackup accelerator:

  • NetBackup accelerator must be properly licensed. For the latest information on licensing, contact your NetBackup sales or partner representative.

  • Supports the disk storage units only. Supported storage includes Media Server Deduplication Pool, NetBackup appliance, cloud storage, and qualified third-party OST storage. For supported storage types, see the NetBackup Enterprise Server and Server - Hardware and Cloud Storage Compatibility List at the following URL: http://www.netbackup.com/compatibility

  • Storage unit groups are supported only if the storage unit selection in the group is Failover.

  • Supports the full backups and incremental backups.

  • For every policy that enables the Use Accelerator option, the following backup schedules are recommended at a minimum: A full backup schedule with the Accelerator forced rescan option enabled. Another full backup schedule without the Accelerator forced rescan option enabled. See Accelerator force rescan for Cloud object store (schedule attribute).

  • If a previous backup of the policy, bucket and query does not exist on the backup host, NetBackup performs a full backup, and creates a track log on the backup host. This initial backup occurs at the speed of a normal (not accelerated) full backup. Subsequent Accelerator backups using same backup host use the track log for accelerated backup speed.

    Note:

    When you first enable a policy to use accelerator, the next backup (whether full or incremental) is in effect a full backup: It backs up all objects corresponding to Cloud objects queries. If that backup was scheduled as an incremental, it may not complete within the backup window.

  • NetBackup retains track logs for future accelerator backups. Whenever you add a query, NetBackup does a full non-accelerated backup for the queries that are added in the list. The unchanged queries are processed as normal accelerator backups.

  • If the storage unit that is associated with the policy cannot be validated when you create the policy, it is validated later when the backup job begins. If accelerator does not support the storage unit, the backup fails. In the bpbrm log, a message appears that is similar to one of the following: Storage server %s, type %s, does not support image include. Storage server type %s, does not support accelerator backup.

  • Accelerator requires that the storage has the OptimizedImage attribute enabled.

  • The Expire after copy retention can cause images to expire while the backup runs. To synthesize a new full backup, the SLP-based accelerator backup needs the previous backup.

  • To detect change in metadata, NetBackup uses one or more cloud APIs per object/blob. Hence, change detection time increases with number of object/blobs to be processed. You may observe backups running longer than expected, for cases with small or no data change but having a large number of objects.

  • If in your environment, for a given object, the metadata or tag are always changed (added/removed/updated) with its data. Evaluate using incremental without accelerator over incremental with accelerator from performance and cost view point.

  • While creating Cloud object store policy with multiple tag-based queries, you can use few simple rules to get best effect with accelerator. Use the query builder in the policy creation page, create separate queries, one query per tag. The accelerator-based policies perform best in this configuration.