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™ for MongoDB Administrator's Guide
  3. Verify the pre-requisites for the MongoDB plug-in for NetBackup
  4. Prerequisites for configuring the MongoDB plug-in
NetBackup™ for MongoDB Administrator's Guide

Prerequisites for configuring the MongoDB plug-in

Consider the following when you configure NetBackup for MongoDB:

Prerequisites:

  • Add the MongoDB thin client package that is part of vxupdate_nb_version SJA to the package repository on the NetBackup primary server.

    Note:

    The required package should correspond to the NetBackup version of the backup host and the operating system of the MongoDB host.

    To add the package, run the nbrepo command on the NetBackup primary server:

    ./nbrepo -add vxupdate_nb_version_suse_x64.sja

    ./nbrepo -add vxupdate_nb_version_redhat_x64.sja

    ./nbrepo -add vxupdate_nbclient_version_redhat_zseries.sja

    For a MongoDB host with CentOS operating system, add the Linux RHEL VxUpdate package of the NetBackup version of the backup host in the package repository on the NetBackup primary server.

    Note:

    If the package is not added, the MongoDB backups can fail with error - 6729: "Unable to download the thin client from the package repository."

  • Use consistent conventions for host names of backup hosts, media servers, and primary server. For example, if you are using the host name as MongoDB.veritas.com (FQDN format) use the same everywhere, specially while running the tpconfig command.

  • Ensure that the backup host can communicate with all the MongoDB nodes.

  • Ensure that the bindIp setting in the configuration file of mongod instance on the MongoDB hosts has value 0.0.0.0.

Best practices:

  • Add the entries of all the nodes of the MongoDB cluster to the/etc/hosts file on all the backup hosts. You must add the host name in FQDN format.

    Or

    Add the appropriate DNS entries in the /etc/resolv.conf file.

Feedback

Was this page helpful?
Previous

Operating system and platform compatibility

Next

Configuring NetBackup for MongoDB

Feedback

Was this page helpful?