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 and managing universal shares
  4. Prerequisites to configure universal shares
  5. Configuring universal share user authentication
  6. Local user-based authentication
NetBackup™ Deduplication Guide

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.

Note:

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 Main > Settings > Security > Authentication > LocalUser. 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 username for the SMB service only:

    adduser --no-create-home -s /sbin/nologin <username>

    smbpasswd -a <username>

    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 Restricted Shell in the MSDP engine.

      su - msdpadm

    • Run the following Restricted Shell command to add a SMB user.

      setting smb add-user username=<username>

      For example,

      msdp-16.1] > setting smb add-user username=<username>

      You can use the same command to update the password for an existing user.

      In AKS and EKS cloud platforms, the SMB Restricted Shell command configures SMB servers in all MSDP engines in a cluster.

Feedback

Was this page helpful?
Previous

Active Directory-based authentication

Next

Kerberos-based authentication

Feedback

Was this page helpful?