NetBackup™ for MongoDB Administrator's Guide

Last Published:
Product(s): NetBackup & Alta Data Protection (10.4)
  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 in the allowed list on the NetBackup primary server
    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.  
      Host user requirements
    7. Managing backup hosts
      1.  
        Including a NetBackup client on NetBackup primary server allowed list
  4. Backing up MongoDB using NetBackup
    1. About 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 for MongoDB clusters with web UI
  5. Restoring or recovering MongoDB data using NetBackup
    1.  
      About restoring MongoDB data
    2.  
      Prerequisites for MongoDB restore and recovery
    3.  
      Restore the MongoDB data on the same cluster
    4.  
      Restore the MongoDB data on an alternate cluster
    5.  
      Restoring MongoDB data in a high availability setup to an alternate client
    6.  
      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

Manual steps after the recovery process

  • After you recover the backup images that were taken from the hidden MongoDB nodes, the hidden nodes become primary nodes. Update all such primary nodes in the shard list and restart the mongos process using the following command:

    db.getSiblingDB('config').shards.updateOne({ "_id" : "shard1" },{ $set : { "host" : "ShardName/repl1.example.net:27018,repl2.example.net:27018,repl3.example.net:27018" } })

  • After the recovery process is complete, manually add the secondary nodes to the cluster. Before adding the nodes, ensure that ownership and permissions on the MongoDB data path on secondary nodes are set properly.

    For more information, refer to the following article: add-members-to-the-replica-set

  • After the recovery operation, the mongod or mongos process is started using the configuration files from the /tmp location. Ensure that you move the configuration files to a selected location and restart the services from that location.

    Remove the configuration files from the /tmp location so that the restore or recovery operations can restore files at the /tmp location with the same name for different users. If you do not remove the files, the subsequent recovery operation using a different user fails with error 2850 because the configuration files cannot be restored at the /tmp location.

    You can add more MongoDB configuration parameters if there are any changes from the backup data that is restored.

  • Before recovery, if you start the MongoDB services with systemctl command, then systemctl status mongod command may show the mongod status as dead after recovery. This happens because after recovery, the mongod services are brought up with the config file under /tmp location.

    In such scenarios, bring up the service again with a use of systemctl start mongod commands.