Backup custer MongoDB

Question

Hello, Community.

There is a cluster of three nodes. 1 primary and 2 secondary.

When I make a backup from one of the nodes, I get the following error:
Error Code: [14:109]
Description: Index processing failed on MediaAgent. This may be due to the index cache being full or because of a corrupt index.
Source: 5, Process: MongoDBCtrl

When I make a backup from another node, I get the following error:
Error Code: [7:276]
Description: Failed to start [backup] on node [3]
Source: 4, Process: MongoDB

how to deal with these errors?

Alex Deaconu · Answer

A case should probably be opened. The usual issue is typically that one of the MAs has their IndexCache location filled up.

You can rearrange the order to the MongoDB Nodes, to make one or another the node the backup client. Note that if you are using LVM, you will need space in the Volume Group of the client used for the backup. You can check that with the command ‘vgdisplay’, you should have more than zero Free PE. Generally five to fifteen percent of the logical volume is recommended to be completely free.

--- Please check the space on all the Media Agents in the storage policy.

--- Verify the free space on all the MongoDB Nodes, and the Free PE amount on their volume groups.

Backup custer MongoDB

2 replies

Reply

Reply

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded