NetBackup™ Deduplication Guide
- Introducing the NetBackup media server deduplication option
- Quick start
- Planning your deployment
- About MSDP storage and connectivity requirements
- About NetBackup media server deduplication
- About NetBackup Client Direct deduplication
- About MSDP remote office client deduplication
- About MSDP performance
- About MSDP stream handlers
- MSDP deployment best practices
- Provisioning the storage
- Licensing deduplication
- Configuring deduplication
- Configuring the Deduplication Multi-Threaded Agent behavior
- Configuring the MSDP fingerprint cache behavior
- Configuring MSDP fingerprint cache seeding on the storage server
- About MSDP Encryption using NetBackup KMS service
- Configuring a storage server for a Media Server Deduplication Pool
- Configuring a disk pool for deduplication
- Configuring a Media Server Deduplication Pool storage unit
- About MSDP optimized duplication within the same domain
- Configuring MSDP optimized duplication within the same NetBackup domain
- Configuring MSDP replication to a different NetBackup domain
- About NetBackup Auto Image Replication
- Configuring a target for MSDP replication to a remote domain
- Creating a storage lifecycle policy
- Resilient Network properties
- Editing the MSDP pd.conf file
- About protecting the MSDP catalog
- Configuring an MSDP catalog backup
- About NetBackup WORM storage support for immutable and indelible data
- MSDP cloud support
- About MSDP cloud support
- Cloud space reclamation
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About MSDP cloud immutable (WORM) storage support
- About immutable object support for AWS S3
- About immutable object support for AWS S3 compatible platforms
- About immutable storage support for Azure blob storage
- About immutable storage support for Google Cloud Storage
- S3 Interface for MSDP
- Configuring S3 interface for MSDP on MSDP build-your-own (BYO) server
- Identity and Access Management (IAM) for S3 interface for MSDP
- S3 APIs for S3 interface for MSDP
- Monitoring deduplication activity
- Managing deduplication
- Managing MSDP servers
- Managing NetBackup Deduplication Engine credentials
- Managing Media Server Deduplication Pools
- Changing a Media Server Deduplication Pool properties
- Configuring MSDP data integrity checking behavior
- About MSDP storage rebasing
- Managing MSDP servers
- Recovering MSDP
- Replacing MSDP hosts
- Uninstalling MSDP
- Deduplication architecture
- Configuring and using universal shares
- Using the ingest mode
- Enabling a universal share with object store
- Configuring isolated recovery environment (IRE)
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- Managing certificates from the deduplication shell
- Managing NetBackup services from the deduplication shell
- Monitoring and troubleshooting NetBackup services from the deduplication shell
- Managing S3 service from the deduplication shell
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting MSDP installation issues
- Troubleshooting MSDP configuration issues
- Troubleshooting MSDP operational issues
- Trouble shooting multi-domain issues
- Appendix A. Migrating to MSDP storage
- Appendix B. Migrating from Cloud Catalyst to MSDP direct cloud tiering
- About direct migration from Cloud Catalyst to MSDP direct cloud tiering
- Appendix C. Encryption Crawler
IAM workflow
In this section, the typical workflow of IAM is described. You can install AWS CLI to send IAM-related API request to complete the tasks.
IAM workflow
- Reset and get S3 server root user's credentials.
Create root user credentials. You can use the root user to create users with limited permissions.
After S3 interface for MSDP is configured, run the following command to create root user's credentials:
/usr/openv/pdde/vxs3/cfg/script/s3srv_config.sh --reset-iam-root
You can also use this command if you have lost root user's access keys. The new access key and secret key of root user is available in the command output.
- Create a user.
aws --endpoint https://<MSDP_HOSTNAME>:8443 [--ca-bundle <CA_BUNDLE_FILE>] iam create-user --user-name <USER_NAME>
- Attach one or more policies to a user.
aws --endpoint https://<MSDP_HOSTNAME>:8443 [--ca-bundle <CA_BUNDLE_FILE>] iam put-user-policy --user-name <USER_NAME> --policy-name <POLICY_NAME> --policy-document file://<POLICY_DOCUMENT_FILE_PATH>
- Create access key for a user.
aws --endpoint https://<MSDP_HOSTNAME>:8443 [--ca-bundle <CA_BUNDLE_FILE>] iam create-access-key [--user-name <USER_NAME>]
Note:
If you omit the --user-name option, the access key is created under the user who sends the request.
- Delete access key for a user.
aws --endpoint https://<MSDP_HOSTNAME>:8443 [--ca-bundle <CA_BUNDLE_FILE>] iam delete-access-key [--user-name <USER_NAME>] --access-key-id <ACCESS_KEY>
Note:
If you omit the --user-name option, the access key is deleted under the user who sends the request. You cannot delete the last active access key of a root user.
- List access keys for a user.
aws --endpoint https://<MSDP_HOSTNAME>:8443 [--ca-bundle <CA_BUNDLE_FILE>] iam list-access-keys [--user-name <USER_NAME>]
Note:
If you omit the --user-name option, the access key is listed under the user who sends the request.
- Update an access key's status for a user.
aws --endpoint https://<MSDP_HOSTNAME>:8443 [--ca-bundle <CA_BUNDLE_FILE>] iam update-access-key [--user-name <USER_NAME>] --access-key-id <ACCESS_KEY> --status [Active | Inactive]
If you omit the --user-name option, the access key is updated under the user who sends the request.
The option --status must follow Active or Inactive parameter (case sensitive).
You cannot update the last active access key of root user to Inactive status.
- Get a specific user policy.
aws --endpoint https://<MSDP_HOSTNAME>:8443 [--ca-bundle <CA_BUNDLE_FILE>] iam get-user-policy --user-name <USER_NAME> --policy-name <POLICY_NAME>
- List all attached policies for a user.
aws --endpoint https://<MSDP_HOSTNAME>:8443 [--ca-bundle <CA_BUNDLE_FILE>] iam list-user-policies --user-name <USER_NAME>
- Delete a user policy.
aws --endpoint https://<MSDP_HOSTNAME>:8443 [--ca-bundle <CA_BUNDLE_FILE>] iam delete-user-policy --user-name <USER_NAME> --policy-name <POLICY_NAME>
- Get user information.
aws --endpoint https://<MSDP_HOSTNAME>:8443 [--ca-bundle <CA_BUNDLE_FILE>] iam get-user --user-name <USER_NAME>
- List all users.
aws --endpoint https://<MSDP_HOSTNAME>:8443 [--ca-bundle <CA_BUNDLE_FILE>] iam list-users
- Delete a user.
aws --endpoint https://<MSDP_HOSTNAME>:8443 [--ca-bundle <CA_BUNDLE_FILE>] iam delete-user --user-name <USER_NAME>
Note:
Before you delete a user, you must delete the user policies and access keys that are attached to the user. You cannot delete a root user.