NetBackup™ for MongoDB Administrator's Guide

Last Published:
Product(s): NetBackup (10.0)
  1. Overview of protecting MongoDB using NetBackup
    1.  
      About protecting a sharded, replica set, or standalone MongoDB cluster using NetBackup
    2.  
      Protecting MongoDB data using NetBackup
    3.  
      NetBackup for MongoDB terminologies
    4.  
      Limitations
    5.  
      Prerequisites and the best practices for protecting MongoDB
  2. Verify the pre-requisites for the MongoDB plug-in for NetBackup
    1.  
      Operating system and platform compatibility
    2.  
      Prerequisites for configuring the MongoDB plug-in
  3. Configuring NetBackup for MongoDB
    1.  
      About the MongoDB configuration tool
    2.  
      Prerequisites for manually creating the mongodb.conf file
    3. Configuring backup options for MongoDB using the mongodb.conf file
      1.  
        Including the configuration file path on NetBackup master server allowed list
    4.  
      Obtaining the RSA key of the MongoDB nodes
    5. Adding MongoDB credentials in NetBackup
      1.  
        About the credential configuration file
      2.  
        How to add the MongoDB credentials in NetBackup
      3.  
        About the MongoDB roles for protecting the data
    6.  
      Using a non-root user as a host user
    7. Managing backup hosts
      1.  
        Including a NetBackup client on NetBackup master server allowed list
  4. Backing up MongoDB using NetBackup
    1. Backing up MongoDB data
      1.  
        Backing up a MongoDB cluster
    2.  
      Prerequisites for backing up a MongoDB cluster
    3. Configuring NetBackup policies for MongoDB plug-in
      1.  
        Creating a BigData backup policy
      2.  
        Creating BigData policy using the NetBackup Administration Console
      3.  
        Using the Policy Configuration Wizard to create a BigData policy for MongoDB clusters
      4.  
        Using the NetBackup Policies utility to create a BigData policy for MongoDB clusters
      5.  
        Using NetBackup Command Line Interface (CLI) to create a BigData policy for MongoDB clusters
  5. Restoring or recovering MongoDB data using NetBackup
    1.  
      Restoring MongoDB data
    2.  
      Prerequisites for MongoDB restore and recovery
    3. About the restore scenarios for MongoDB database from the BAR interface
      1.  
        High-level steps involved in the Restore and Recovery process
    4.  
      Using the BAR interface to restore the MongoDB data on the same cluster
    5.  
      Using the BAR interface to restore the MongoDB data on an alternate cluster
    6.  
      About restoring MongoDB data in a high availability setup on an alternate client
    7. Recovering a MongoDB database using the command line
      1.  
        Creating or modifying the rename file
      2.  
        Using the command line to recover a MongoDB database
    8.  
      Manual steps after the recovery process
  6. Troubleshooting
    1.  
      About NetBackup for MongoDB debug logging
    2.  
      Known limitations for MongoDB protection using NetBackup
  7. Appendix A. Additional information
    1.  
      Sample MongodB configuration utility workflow to add and update MongodB credentials
  8.  
    Index

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 version number must be the same as the backup 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

    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.