MongoDB Ops Manager cluster recovery
Recovery typically refers to the process of restoring data and service after a failure or disaster. Ensure that the Configuration parameters are configured for recovery. See MongoDB Ops Manager configuration file settings. for more details.
Note:
Taking a snapshot while a restore operation is in progress is not supported.
During a restore, the database process is stopped and existing data on the cluster is removed before data from the selected snapshot is copied back. At this time, there is no stable data available on disk to create a snapshot.
Any snapshot request started during a restore will fail or may remain stuck and will not generate a Snapshot ID. Snapshot requests are not queued or retried automatically.
Start snapshot operations only after the restore has completed successfully and the cluster is fully running and healthy.
TLOG backups must be configured and available for the target time.
If TLOG backups are missing or contain gaps for the selected interval, PIT restore cannot be performed and recovery is limited to snapshot restore points.
Log on to NetBackup Web UI.
On the left pane, select .
Click from the Regular recovery option.
Specify the Basic properties details as follows:
Select MongoDB Ops Manager as the type.
Select Normal backups as type.
Click . Source clusters list is displayed. The list displays the clusters which are discovered and added as asset. Select the required source cluster to recover and then click .
Note:
If a cluster has been renamed after taking a backup, new name of the cluster is displayed.
Specify the such as date range, files, and folders.
Specify the such as Restore target, MongoDB options, and number of streams. The default stream is configured to One.
Note:
Restore to an alternate cluster is supported only when both the source and target clusters are managed by the same MongoDB Ops Manager. Restoring data across different Ops Manager hosts is NOT supported.
the recovery options provided and then click .
Note:
Post recovery, the files and folders permission will be 777.
Note:
The 'max stream count per node' provided by the user for recovery is the maximum number of streams that NetBackup is allowed to create per node for data transfer. The actual number of streams to create and amount of data allocated to each stream will be decided at runtime based on the total data size and the number of files. The actual number of streams will always be less than or equal to the max number specified by user. NetBackup has enforced a max stream count limit capped at 32 which is user can specify any value between 1 and 32.
During MongoDB restore operations, NetBackup creates additional directories under the NetBackupCopiedOplogs path. These directories are created for each restore job and are named using the restore job ID.
After the restore operation completes successfully, these directories are not removed automatically. If the restore job is completed and the data is no longer required, you can safely delete the directories related to those completed restore jobs.
Removing these directories helps free up disk space on the system.