Veritas Access Appliance 8.2 Solutions Guide for NetBackup
- Access Appliance integration with NetBackup
- System requirements
- Configuring Veritas Data Deduplication with Access Appliance
- About Veritas Data Deduplication
- Benefits of using Veritas Data Deduplication with Access Appliance
- Supported features with different versions of Veritas Data Deduplication
- Configuring Veritas Data Deduplication without WORM
- Configuring Veritas Data Deduplication with WORM
- Managing Veritas Data Deduplication using the Access CLISH
- Managing Veritas Data Deduplication using GUI
- Viewing information about Veritas Data Deduplication
- Starting or stopping the Veritas Data Deduplication service
- Increasing storage for Veritas Data Deduplication
- Unconfiguring Veritas Data Deduplication
- Adding secondary IP for Veritas Data Deduplication
- Deleting secondary IP for Veritas Data Deduplication
- Changing the primary IP for Veritas Data Deduplication
- Upgrade the deduplication version for Veritas Data Deduplication
- Setting affinity node for Veritas Data Deduplication
- Accessing Access Appliance storage shell for management tasks
- Support for multiple domains across networks for Veritas Data Deduplication
- Veritas Data Deduplication storage layout
- Configuring a Veritas Data Deduplication storage unit on NetBackup
- Configuring global deduplication using the Veritas Data Deduplication storage server across the domain
- Enabling Veritas Data Deduplication encryption
- Support for bandwidth throttling during duplication
- Setting up secure communication between Veritas Data Deduplication on Access Appliance and the NetBackup primary server
- About MSDP encryption using NetBackup KMS service
- Support for NetBackup Auto Image Replication
- Setting up Auto Image Replication (AIR) between two Access Appliances which have secure communication enabled
- NetBackup Dedupe Direct for Oracle
- Configuring MSDP-C with Access Appliance
- Migrating the NetBackup images from existing storage to Veritas Access storage
- Configuring Access Appliance with the NetBackup client
- Configuring Access Appliance for NetBackup client
- Installing the NetBackup client add-on packages
- Prerequisites for configuring the NetBackup client
- Configuring the NetBackup client
- Adding an optional media server
- Adding multiple primary servers
- Adding file systems to the backup configuration
- Removing file systems from backup configuration
- Changing the virtual IP address used by the NetBackup client
- Upgrade the NetBackup client
- Unconfiguring the NetBackup client
- Enabling Veritas Data Deduplication catalog backup with NetBackup client
- Disabling Veritas Data Deduplication catalog backup from NetBackup client
- Displaying the status of NetBackup services
- Configuring backup operations using NetBackup or other third-party backup applications
- Restoring filesystems backed up with NetBackup client
- Configuring isolated recovery environment (IRE)
- Requirements
- Configuring the network isolation
- Configuring an isolated recovery environment using the command line
- Configuring an isolated recovery environment on a storage server
- Managing an isolated recovery environment on a storage server
- Configuring data transmission between a production environment and an IRE storage server
- Troubleshooting
- 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.pyThe 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