Veritas Access Appliance Solutions Guide for NetBackup

Last Published:
Product(s): Appliances (7.4.3)
Platform: Veritas 3340,Access Appliance OS
  1. Access Appliance integration with NetBackup
    1.  
      About Access Appliance as a NetBackup client
    2.  
      About Access Appliance as backup storage for NetBackup
    3.  
      Use cases for long-term data retention
  2. System requirements
    1.  
      Supported configurations and versions for NetBackup with Veritas Data Deduplication
    2.  
      Supported configurations and versions for NetBackup with CloudCatalyst
  3. Configuring Veritas Data Deduplication with Access Appliance
    1.  
      About Veritas Data Deduplication
    2.  
      Benefits of using Veritas Data Deduplication with Access Appliance
    3.  
      Configuring Veritas Data Deduplication using the GUI
    4.  
      Configuring Veritas Data Deduplication using the Access CLISH
    5.  
      Support for multiple domains across networks for Veritas Data Deduplication
    6.  
      Veritas Data Deduplication storage layout
    7.  
      Configuring a Veritas Data Deduplication storage unit on NetBackup
    8.  
      Configuring global deduplication using the Veritas Data Deduplication storage server across the domain
    9.  
      Enabling Veritas Data Deduplication encryption
  4. Migrating the NetBackup images from existing storage to Veritas Data Deduplication storage
    1.  
      Migrating NetBackup images from CloudCatalyst/S3 to Veritas Data Deduplication storage
  5. Configuring Access Appliance as a cloud storage server with NetBackup CloudCatalyst
    1.  
      Creating an S3 bucket on Access Appliance for storing deduplicated backup data from NetBackup
    2.  
      Configure Access Appliance as a cloud storage server on NetBackup server using CloudCatalyst
    3.  
      Enabling SSL on Access Appliance
  6. 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
  7. Configuring Access Appliance with the NetBackup client
    1.  
      Configuring Access Appliance for NetBackup client
    2.  
      Installing the NetBackup client add-on packages
    3.  
      Prerequisites for configuring the NetBackup client
    4.  
      Configuring the NetBackup client
    5.  
      Adding an optional media server
    6.  
      Adding multiple master servers
    7.  
      Adding file systems to the backup configuration
    8.  
      Removing file systems from backup configuration
    9.  
      Changing the virtual IP address used by the NetBackup client
    10.  
      Upgrade the NetBackup client
    11.  
      Unconfiguring the NetBackup client
    12.  
      Enabling Veritas Data Deduplication catalog backup with NetBackup client
    13.  
      Disabling Veritas Data Deduplication catalog backup from NetBackup client
    14.  
      Displaying the status of NetBackup services
    15.  
      Configuring backup operations using NetBackup or other third-party backup applications
    16.  
      Configuring Access Appliance for NetBackup cloud storage
    17.  
      Restoring file systems backed up with NetBackup client
  8. Troubleshooting
    1.  
      Additional resources
    2.  
      Generating Access Appliance S3 server keys using the helper script
  9.  
    Index

Generating Access Appliance S3 server keys using the helper script

Create the access and the secret keys using the Access Appliance 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 Access Appliance S3 server credential keys.

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

  • The Access Appliance 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. The ADMIN_URL has the format admin.<cluster_name:port number> . The port number should be 8144. This url should point to the Access Appliance management console IP address.

  • Create the access and the secret key using the Access Appliance helper script by providing the user name, password, and ADMIN_URL (check the online Help of the Access Appliance 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 Access Appliance 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