Veritas NetBackup for MongoDB Administrator's Guide
- Overview of protecting MongoDB using NetBackup
- Installing and deploying MongoDB plug-in for NetBackup
- Deploying the MongoDB plug-in
- Operating system and platform compatibility
- Downloading the plug-in
- Installing the MongoDB plug-in and the required EEBs
- Prerequisites and the best practices for deploying the MongoDB plug-in
- Post installation procedures
- Verifying the installation of the MongoDB plug-in
- 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
About restoring MongoDB data in a high availability setup on an alternate client
Use this information when the client (MongoDBnode-port) that is defined in the Clients tab of the backup policy is not available and you want 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 in the same MongoDB cluster
Complete the following steps:
Rename the application server and its nodes and set the value for the alternate application server.
In the BAR UI select the tab > and use or 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 done from the MongoDB node endu79-26055. In this scenario, as part of restore and recovery, append endu79:26055 as follows:ALT_APPLICATION_SERVER=endu79:26055.