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 Key Management Server 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
- Running MSDP services with the non-root user
- 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 bucket-level immutable storage support for Google Cloud Storage
- About object-level immutable storage support for Google Cloud Storage
- About AWS IAM Role Anywhere support
- About Azure service principal support
- About NetBackup support for AWS Snowball Edge
- 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
- Disaster recovery in S3 interface for MSDP
- Monitoring deduplication activity
- Viewing MSDP job details
- 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
- Configuring universal share user authentication
- Using the ingest mode
- Enabling a universal share with object store
- Configure a universal share accelerator
- About the universal share accelerator quota
- Configuring isolated recovery environment (IRE)
- Configuring an isolated recovery environment using the web UI
- Configuring an isolated recovery environment using the command line
- Using the NetBackup Deduplication Shell
- Managing users from the deduplication shell
- About the external MSDP catalog backup
- 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 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
Local user-based authentication
You must configure SMB users on the corresponding storage server and enter the credentials on the client.
If the SMB service is part of a Windows domain, the Windows domain users can use the SMB share. In this scenario, credentials are not required to access the share.
For Azure Kubernetes Service (AKS) and Amazon Elastic Kubernetes Service (EKS) cloud platforms, only a SMB local user can access the SMB share. You must add SMB users to access the SMB share.
If the SMB service is not part of Windows domain, perform the following steps:
For a NetBackup Appliance:
For a NetBackup Appliance, local users are also SMB users. To manage local users, log in to the CLISH and select
. The SMB password is the same as the local user's login password.For an MDSP BYO server:
For an MDSP BYO server, create a Linux user (if one does not exist). Then, add the user to SMB.
For example, the following commands create a test_smb_user use for the SMB service only:
# adduser --no-create-home -s /sbin/nologin test_smb_user
# smbpasswd -a test_smb_user
To add an existing user to the SMB service, run the following command:
# smbpasswd -a username
For a Flex Appliance primary or media server application instance:
For a Flex Appliance primary or media server application instance, log in to the instance and add any local user to the SMB service as follows:
If desired, create a new local user with the following commands:
#useradd <username> #passwd <username>
You can also use an existing local user.
Run the following commands to create user credentials for the SMB service and enable the user:
smbpasswd -a <username> smbpasswd -e <username>
For a WORM storage server application instance:
For a WORM storage server instance, log in to the instance and add a local SMB user with the following command: setting smb add-user username=<username> password=<password>
You can view the new user with the setting smb list-users command. To remove a user, run the setting smb remove-user username=<username> command.
For the AKS and the EKS cloud platform:
Log in to the MSDP engine pod in a cluster using kubectl.
Run the following command to log in to RShell in the MSDP engine.
su - msdpadm
Run the following RShell command to add a SMB user.
setting smb add-user username=[samba user name]
For example,
msdp-16.1] > setting smb add-user username=test_samba_user
You can use the same command to update the password for an existing user.
In AKS and EKS cloud platforms, the SMB RShell command configures SMB servers in all MSDP engines in a cluster.