Veritas NetBackup™ for MongoDB Administrator's Guide

Last Published:
Product(s): NetBackup (9.0.0.1, 9.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.  
        Whitelisting the configuration file path on NetBackup master 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.  
      Using a non-root user as a host user
    7. Managing backup hosts
      1.  
        Whitelisting a NetBackup client on NetBackup master server
  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

NetBackup for MongoDB terminologies

The following table defines the terms you come across when using NetBackup for protecting MongoDB cluster.

Table: NetBackup terminologies

Terminology

Definition

Compound job

A backup job for MongoDB data is a compound job.

  • The backup job runs a discovery job for getting information of the data to be backed up.

  • Child jobs are created for each backup host that performs the actual data transfer.

  • After the backup is complete, the job cleans up the snapshots on the backup nodes, removes the thin client and is marked complete.

Discovery job

When a backup job is executed, first a discovery job is created. The discovery job communicates with the config server and gathers information of the shards that need to be backed up and the associated nodes.

At the end of the discovery, the job populates a workload discovery file that NetBackup then uses to distribute the workload amongst the backup hosts.

Child job

For backup, a separate child job is created for each backup host to transfer data to the storage media. A child job can transfer data blocks from multiple secondary nodes.

Workload discovery file

During discovery, when the backup host communicates with the config server, a workload discovery file is created. The file contains information about the data files to be backed up and the associated data nodes.

Workload distribution file

After the discovery is complete, NetBackup creates a workload distribution file for each backup host. These files contain information of the data that is backed up by the respective backup host.

Parallel streams

The NetBackup parallel streaming framework allows data blocks from multiple secondary nodes to be backed up using multiple backup hosts simultaneously.

Backup host

The backup host acts as a proxy client. All the backup and the restore operations are executed through the backup host.

You can configure media servers, clients, or a master server as a backup host.

The backup host is also used as destination client during restores.

BigData policy

The BigData policy is introduced to:

  • Specify the application type.

  • Allow backing up distributed multi-node environments.

  • Associate backup hosts.

  • Perform workload distribution.

Application server

  • Sharded MongoDB cluster:

    Application server is the MongoDB primary config server.

  • Replica set MongoDB cluster:

    Application server is the primary node of MongoDB.

  • Standalone cluster:

    Application server is the standalone node.

Primary config server

In a high-availability scenario, the primary config server is the MongoDB instance running in a primary role on a config server replica set. The primary config server must have at least one associated mongos service running on the same host.

Fail-over config server

In a high-availability scenario, the config server other than the primary config server that is specified as alternate_config_server in the mongodb.conf file is referred as the fail-over config server.