Veritas Access 7.3.0.1 NetBackup Solutions Guide
- Veritas Access integration with NetBackup
- System requirements
- Configuring Veritas Access backup over S3 with OpenDedup and NetBackup
- Benefits of using Veritas Access with NetBackup and OpenDedup
- Workflow for OpenDedup
- Use case 1: Backing up deduplicated data (OpenDedup and NetBackup) using the S3 protocol to Veritas Access
- Use case 2: Backing up data (NetBackup) and deduplicating the data (OpenDedup) on Veritas Access
- Creating an S3 bucket on Veritas Access for storing deduplicated backup data from NetBackup
- Creating a Media Server Deduplication Pool (MSDP) for primary backup using NetBackup
- Creating an OST disk pool and STU in the NetBackup console
- Setting up multiple NetBackup media servers in the same domain
- Setting up multiple SDFS volumes on a NetBackup media server
- Configuring backup and restore using NetBackup policies
- Troubleshooting
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.pyThe 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