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
Changing the service user after installation or upgrade
After NetBackup is installed, you create MSDP storage server. If NetBackup is configured to run with the non-root service user before MSDP storage server is created, MSDP can also be run with the service user automatically.
If MSDP services are not running as the service user, you can manually change the service user by using the msdpserviceusercmd command.
Following are the prerequisites to run MSDP with the non-root service user:
Check if NetBackup services can be run with the non-root user. If NetBackup services cannot be run with the non-root user, change the NetBackup service user account. For more information, see the NetBackup Security and Encryption Guide.
On the NetBackup BYO, run the following command to check the maximum number of files that service user can open:
ulimit -Hn
Set the limit to 1048576 in
/etc/security/limits.conf
file.
To change the MSDP service user on NetBackup BYO
- Stop the following services:
systemctl stop crond.service
/usr/openv/netbackup/bin/bp.kill_all
/opt/VRTSpbx/bin/vxpbx_exchanged stop
- Run the following command to change the MSDP service user.
/usr/openv/pdde/pdconfigure/scripts/support/msdpserviceusercmd
- Start the following services:
/opt/VRTSpbx/bin/vxpbx_exchanged start
/usr/openv/netbackup/bin/bp.start_all
systemctl start crond.service
To change the MSDP service user on the media server on Flex Appliance
- Stop the following services:
/opt/veritas/vxapp-manage/health disable
systemctl stop crond.service
/opt/veritas/vxapp-manage/stop
- Run the following command to change the MSDP service user.
/usr/openv/pdde/pdconfigure/scripts/support/msdpserviceusercmd
- Start the following services:
/opt/veritas/vxapp-manage/start
systemctl start crond.service
/opt/veritas/vxapp-manage/health enable
To change the MSDP service user on NetBackup Appliance
- Stop the crond service from the NetBackup Appliance shell menu.
Main_Menu > Support > Service Stop crond
For the usage of NetBackup Appliance Shell Menu, see the Veritas NetBackup Appliance Commands Reference Guide.
- Stop the NetBackup processes from the NetBackup Appliance shell menu.
Main_Menu > Support > Processes > NetBackup Stop
- Run the following command from the NetBackup CLI to change the MSDP service user.
nbucliuser-!> msdpserviceusercmd
For the usage of NetBackup CLI, see About the NetBackupCLI user role topic of the Veritas NetBackup Appliance Security Guide.
- Start NetBackup processes from the NetBackup Appliance shell menu.
Main_Menu > Support > Processes > NetBackup Start
- Start the crond service from the NetBackup Appliance shell menu.
Main_Menu > Support > Service Restart crond
Note:
MSDP service user is same as NetBackup service user.
msdpserviceusercmd can take long time depending on the MSDP storage data size. If you think that the command may be interrupted (for example, you turn off the laptop), run msdpserviceusercmd command in the background using Linux command nohup.
If msdpserviceusercmd is interrupted, MSDP service fails to start. In that case, run the command again to restart the process to change the service user.
When you add an additional MSDP storage volume using the command crcontrol --dsaddpartition [volume path], ensure that the MSDP service user has the read and write permissions on the new storage volume path.
The services spad, spoold, ocsd, and s3srv are the MSDP services that run with the service user. MSDP web service spws always runs with the spws user.