Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Deduplication Guide
  3. Configuring deduplication
  4. Running MSDP services with the non-root user
  5. Changing the service user after installation or upgrade
NetBackup™ Deduplication Guide

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

  1. Stop the following services:

    systemctl stop crond.service

    /usr/openv/netbackup/bin/bp.kill_all

    /opt/VRTSpbx/bin/vxpbx_exchanged stop

  2. Run the following command to change the MSDP service user.

    /usr/openv/pdde/pdconfigure/scripts/support/msdpserviceusercmd

  3. 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

  1. Stop the following services:

    /opt/veritas/vxapp-manage/health disable

    systemctl stop crond.service

    /opt/veritas/vxapp-manage/stop

  2. Run the following command to change the MSDP service user.

    /usr/openv/pdde/pdconfigure/scripts/support/msdpserviceusercmd

  3. 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

  1. 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 NetBackup Appliance Commands Reference Guide.

  2. Stop the NetBackup processes from the NetBackup Appliance shell menu.

    Main_Menu > Support > Processes > NetBackup Stop

  3. 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 NetBackup Appliance Security Guide.

  4. Start NetBackup processes from the NetBackup Appliance shell menu.

    Main_Menu > Support > Processes > NetBackup Start

  5. 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.

Feedback

Was this page helpful?
Previous

Running MSDP services with the non-root user

Next

Running MSDP commands with the non-root user

Feedback

Was this page helpful?