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

Restoring MongoDB data in a high availability setup to an alternate client

If a client (MongoDBnode-port) that is defined in the backup policy is not available use the following procedure to restore to a different client in the same MongoDB cluster (MongoDBnode-port).

In a high availability setup, you can restore the MongoDB data as follows:

  • Sharded MongoDB cluster

    Restore to an alternate config server in the same MongoDB cluster.

  • Replica set MongoDB cluster

    Restore to an alternate node of the replica set that is in the same MongoDB cluster.

To restore MongoDB data in a high availability setup to an alternate client

  1. Open the web UI.
  2. On the left, click Recovery. On the Regular recovery card, click Start recovery.
  3. Rename the application server and its nodes and set the value for the alternate application server.

    • Select Restore individual directories and files to different locations and click Edit file paths to add the alternate application servers.

    • If the application_server (Host1-port1) is different from the target application_server (Host2:Port2), the rename entry must contain ALT_APPLICATION_SERVER=Host2:Port2.

      In the following example, the Source client that is defined in the backup policy is endu79-26050, and the backup was performed by the MongoDB node endu79-26055. In this scenario, as part of restore and recovery, append endu79:26055 as follows:ALT_APPLICATION_SERVER=endu79:26055.