Veritas NetBackup™ for MongoDB Administrator's Guide
- Overview of protecting MongoDB using NetBackup
- Verify the pre-requisites for the MongoDB plug-in for NetBackup
- Configuring NetBackup for MongoDB
- About the MongoDB configuration tool
- Prerequisites for manually creating the mongodb.conf file
- Configuring backup options for MongoDB using the mongodb.conf file
- Obtaining the RSA key of the MongoDB nodes
- Adding MongoDB credentials in NetBackup
- Using a non-root user as a host user
- Managing backup hosts
- Backing up MongoDB using NetBackup
- Backing up MongoDB data
- Prerequisites for backing up a MongoDB cluster
- Configuring NetBackup policies for MongoDB plug-in
- Creating a BigData backup policy
- Creating BigData policy using the NetBackup Administration Console
- Using the Policy Configuration Wizard to create a BigData policy for MongoDB clusters
- Using the NetBackup Policies utility to create a BigData policy for MongoDB clusters
- Using NetBackup Command Line Interface (CLI) to create a BigData policy for MongoDB clusters
- Restoring or recovering MongoDB data using NetBackup
- Restoring MongoDB data
- Prerequisites for MongoDB restore and recovery
- About the restore scenarios for MongoDB database from the BAR interface
- Using the BAR interface to restore the MongoDB data on the same cluster
- Using the BAR interface to restore the MongoDB data on an alternate cluster
- About restoring MongoDB data in a high availability setup on an alternate client
- Recovering a MongoDB database using the command line
- Manual steps after the recovery process
- Troubleshooting
- Appendix A. Additional information
- Index
Adding MongoDB credentials in NetBackup
Note:
If you use the MongoDB configuration tool, these manual steps are not required.
To establish a seamless communication between MongoDB clusters and NetBackup for successful backup and restore operations, you must add and update MongoDB credentials to the NetBackup master server.
NetBackup supports the following authentication types for protecting the MongoDB data:
No authentication
Simple - Salted Challenge Response Authentication Mechanism (SCRAM)
Certificate-based - x.509
Different options are required for each of the authentication types when you add the credentials using the tpconfig command.
The following table describes the options that are required for each authentication type:
Table: Required options for authentication types
Options | Option description | No authentication | Simple authentication | Certificate-based authentication |
|---|---|---|---|---|
AppUserId | Specifies the user name that is required to log into the application server. | ✖ | ✔ | ✖ |
AppUserPassword | Specifies the user password that is required to log into the application server. | ✖ | ✔ | ✖ |
HostUser | Specify the host's user ID for SSH implementation. If the host user that you want to use is a non-root user or does not have root permissions for the MongoDB server then: | ✔ | ✔ | ✔ |
HostPassword | Specify the host's user password for SSH implementation. | ✔ | ✔ | ✔ |
HostRSAKey | RSA key is required to perform password-less remote operations. | ✔ | ✔ | ✔ |
ServerPemPath | Path to the PEM certificate file on the MongoDB node. | ✖ | ✖ | ✔ |
CAPemPath | Path to the CA PEM certificate file on the MongoDB node. | ✖ | ✖ | ✔ |
Passkey | Password of CA certificate. | ✖ | ✖ | ✔ |
CADir | Path to the CA certificate. | ✖ | ✖ | ✔ |
CARole | User role that is defined in the CA. | ✖ | ✖ | ✔ |
CertificateUser | Specifies the details fo the certificate user. | ✖ | ✖ | ✔ |
application_server_conf | Specifies a path to the credential configuration file that contains the authentication type, user details, and the directory paths for the CA security certificates. | ✔ | ✔ | ✔ |