Veritas 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
- About the disaster recovery for cloud LSU
- About Image Sharing using MSDP cloud
- About MSDP cloud immutable (WORM) storage support
- 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
- 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
Configuring Universal Share user authentication
The universal share feature supports two methods of user authentication:
Active Directory-based user authentication
Local user-based authentication
If the appliance, Flex Appliance application instance, or MSDP BYO server is part of the Active Directory domain, you can use this approach.
When you create a universal share from the NetBackup web GUI, you can specify Active Directory users or groups. This approach restricts access to only specified users or groups. You can also control permissions from the Windows client where you are mounting the universal share. See the NetBackup Web UI Administrator's Guide for more information.
For information about setting up Active Directory users or groups with an appliance or Flex Appliance application instance, see the NetBackup Application Guide for Flex Appliance.
You must configure Samba users on the corresponding storage server and enter the credentials on the client.
If the Samba service is part of a Windows domain, the Windows domain users can use the Samba share. In this scenario, credentials are not required to access the share.
If the Samba service is not part of Windows domain, perform the following steps:
For a NetBackup Appliance:
For a NetBackup Appliance, local users are also Samba users. To manage local users, log in to the CLISH and select
. The Samba 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 Samba.
For example, the following commands create a test_samba_user use for the Samba service only:
# adduser --no-create-home -s /sbin/nologin test_samba_user
# smbpasswd -a test_samba_user
To add an existing user to the Samba service, run the following command:
# smbpasswd -a username
For a Flex Appliance application instance:
For a Flex Appliance application instance, log in to the instance and add any local user to Samba, 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 Samba and enable the user:
smbpasswd -a <username> smbpasswd -e <username>