Veritas Access NetBackup Solutions Guide

Last Published:
Product(s): Access (7.4)
Platform: Linux
  1. Veritas Access integration with NetBackup
    1.  
      About Veritas Access
    2.  
      About Veritas Access as a NetBackup client
    3.  
      About Veritas Access as backup storage for NetBackup
    4.  
      Use cases for long-term data retention
    5.  
      Benefits of using Veritas Access with NetBackup and OpenDedup/CloudCatalyst
  2. System requirements
    1.  
      System requirements for OpenDedup installation
    2.  
      Supported configurations and versions for NetBackup with OpenDedup
    3.  
      Supported configurations and versions for NetBackup with CloudCatalyst
  3. Configuring Veritas Access backup over S3 with OpenDedup and NetBackup
    1.  
      Workflow for OpenDedup
    2.  
      Use case 1: Backing up deduplicated data (OpenDedup and NetBackup) using the S3 protocol to Veritas Access
    3.  
      Use case 2: Backing up data (NetBackup) and deduplicating the data (OpenDedup) on Veritas Access
    4.  
      Creating an S3 bucket on Veritas Access for storing deduplicated backup data from NetBackup
    5.  
      Creating a Media Server Deduplication Pool (MSDP) for primary backup using NetBackup
    6.  
      Creating an OST disk pool and STU in the NetBackup console
    7.  
      Setting up multiple NetBackup media servers in the same domain
    8.  
      Setting up multiple SDFS volumes on a NetBackup media server
  4. Configuring Veritas Access as a cloud storage server with NetBackup CloudCatalyst
    1.  
      Creating an S3 bucket on Veritas Access for storing deduplicated backup data from NetBackup
    2.  
      Configure Veritas Access as a cloud storage server on NetBackup server
  5. Configuring backup and restore using NetBackup policies
    1.  
      Storage Lifecycle Policies
    2.  
      Backup and restore
    3.  
      Running a backup policy manually
    4.  
      Restoring backed up files
  6. Troubleshooting
    1.  
      Unmounting the SDFS volume before restarting Veritas Access or the NetBackup media server
    2.  
      Log locations for troubleshooting
    3.  
      Additional resources
    4.  
      Generating Veritas Access S3 server keys using the helper script

Generating Veritas Access S3 server keys using the helper script

Create the access and the secret keys using the Veritas Access helper script in case you do not want to use the Active directory Domain user to create and own the buckets. This is an alternative way to get the Veritas Access S3 server credential keys.

  • Location of the helper script: /opt/VRTSnas/scripts/utils/objectaccess/objectaccess_client.py

  • The Veritas Access helper script can be used from any client system that has Python installed.

  • To run the script, your S3 client needs to have the argparse and requests Python modules.

    If these modules are missing, install both these modules using pip or easy_install.

  • Add the ADMIN_URL name in your /etc/hosts file.

    where the ADMIN_URL is admin.<cluster_name> and the port is 8144. This url should point to the Veritas Access management console IP address.

  • Create the access and the secret key using the Veritas Access helper script by providing the user name, password, and ADMIN_URL (check the online Help of the Veritas Access helper script for all of the provided operations like list key and delete key).

    Create a secret key:

    clus_01:~ # ./objectaccess_client.py --create_key 
    --server admin.clus:8144 --username localuser1 --password root123 
    --insecure
    UserName                : localuser1
    AccessKeyId             : Y2FkODU2NTU2MjVhYzV
    Status                  : Active
    SecretAccessKey         : ODk0YzQxMDhkMmRjM2M5OTUzNjI5OWIzMDgyNzY

    The <localuser1> is the local user created on both the Veritas Access cluster nodes with same unique ID.

    List a secret key for the specified user:

    clus_01:~ # ./objectaccess_client.py --list_key --server 
    admin.clus:8144 --username localuser2 --password root123 --insecure

    Delete a secret key for the specified user:

    clus_01:~ # ./objectaccess_client.py --delete_key 
    ZTkyNDdjZTViM2EyMWZ --server admin.clus:8144 --username localuser2 
    --password root123 --insecure
  • If the object server is enabled without the SSL option, you need to add the --insecure option.

    clus_01 ~# ./objectaccess_client.py --server 
    admin.clus:8144 --username <uname> --create_key --insecure