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. Veritas NetBackup™ Deduplication Guide
  3. Configuring and using universal shares
  4. MSDP build-your-own (BYO) server prerequisites and hardware requirements to configure Universal Shares
Veritas NetBackup™ Deduplication Guide

MSDP build-your-own (BYO) server prerequisites and hardware requirements to configure Universal Shares

The following are prerequisites for using the Universal Share MSDP build-your-own (BYO) server feature:

  • The Universal Share is supported on an MSDP BYO storage server with Red Hat Enterprise Linux 7.6, 7.7, 7.8, or 7.9.

  • NFS services are installed and running if you want to use the share over NFS

  • Samba services are installed and running if you want to use share over CIFS/SMB.

    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, local users are also Samba users. To manage local users, log in to the CLISH and select Main > Settings > Security > Authentication > LocalUser. The Samba password is the same as the local user's login password.

      • 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

  • NGINX is installed and running.

    • Installing NGINX from Red Hat Software Collections:

      • Refer to https://www.softwarecollections.org/en/scls/rhscl/rh-nginx114/ for instructions.

        Because the package name depends on the NGINX version, run yum search rh-nginx to check if a new version is available. (For NetBackup 8.3, an EEB is required if NGINX is installed from Red Hat Software Collections.)

    • Installing NGINX from the EPEL repository:

      • Refer to https://fedoraproject.org/wiki/EPEL for installation instructions of the repository and further information.

        The EPEL repository is a volunteer-based community effort and not commercially supported by Red Hat.

    • The NGINX version must be same as the one in the corresponding official RHEL version release. You need to install it from the corresponding RHEL yum source (epel).

    • Before you start the storage configuration, ensure that the new BYO NGINX configuration entry /etc/nginx/conf.d/byo.conf will be included as part of the HTTP section of the original /etc/nginx/nginx.conf file.

    • If SE Linux has been configured, ensure that the policycoreutils and policycoreutils-python packages are installed from the same RHEL yum source (RHEL server), and then run the following commands:

      • semanage port -a -t http_port_t -p tcp 10087

      • setsebool -P httpd_can_network_connect 1

      Enable the logrotate permission in SE Linux using the following command:

      semanage permissive -a logrotate_t

  • Ensure that the /mnt folder on the storage server is not mounted by any mount points directly. Mount points should be mounted to its subfolders.

If you are configuring the universal share feature on BYO after storage is configured or upgraded without the NGINXx service installed, run the command:

/usr/openv/pdde/vpfs/bin/vpfs_config.sh --configure_byo

Table: Hardware configuration requirements for Universal Shares on a Build Your Own (BYO) server

CPU

Memory

Disk

  • Minimum 2.2-GHz clock rate.

  • 64-bit processor.

  • Minimum 4 cores; 8 cores recommended. For 64 TBs of storage, the Intel x86-64 architecture requires eight cores.

  • Enable the VT-X option in the CPU configuration.

  • 16 GB (For 8 TBs to 32 TBs of storage - 1GB RAM for 1TB of storage).

  • 32 GBs of RAM for more than 32 TBs storage.

  • An additional 500MB of RAM for each live mount.

Disk size depends on the size of your backup. Refer to the hardware requirements for NetBackup and Media Server Deduplication Pool (MSDP).

Feedback

Was this page helpful?
Previous

Configuring and using an MSDP build-your-own (BYO) server for Universal Shares

Next

Mounting a Universal Share created from the NetBackup web UI

Feedback

Was this page helpful?