Navigation
This version of the documentation is archived and no longer supported. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.

Manage File System Snapshot Storage

On this page

Ops Manager can backup databases to either another database (blockstore), to a local file system or a combination of both. This tutorial covers using file system stores to backup your MongoDB databases.

If you use file system snapshot storage and use multiple Ops Manager instances (including those activated as Backup Daemons), all Ops Manager instances must have the same view of the file system snapshot storage. You can achieve this through a Network File System (NFS) application or something similar. If the Ops Manager instances do not share the same view of file system snapshot storage, Backup restores will not be possible and Ops Manager will not be able to remove expired snapshots.

Note

Use multiple snapshot stores when you must add capacity or when you must meet data localization or other regulatory requirements. Assign Snapshot Stores to Specific Data Centers describes how to assign snapshot stores to different data centers.

Prerequisites

Before creating any file system snapshot stores:

  • Ensure a storage volume with sufficient capacity is attached to the Ops Manager server to store the snapshot files and the oplog MongoDB database.
  • Deploy the dedicated MongoDB instance(s) to host the oplog stores for this snapshot store.
  • If you use multiple Ops Manager instances (including those activated as Backup Backup Daemons), set up a Network File System (NFS) application or something similar to ensure the all instances share the same view of file system snapshot storage.

Important

If the Ops Manager instances do not share the same view of file system snapshot storage, Backup restores will not be possible and Ops Manager will not be able to remove expired snapshots.

Procedures

Add a File System Store

1

Navigate to the Snapshot Storage page.

  1. Click the Admin link.
  2. Click the Backup tab.
  3. Click the Snapshot Storage page.
2

Click Create New File System Store.

3

Complete the File System Store details.

Field Contents
File System Store Name A name for the file system store.
Path The file system path in which the snapshot will be stored.
New Assignment Enabled checkbox This enables the filestore once it has been created. If you leave this unchecked, the filestore is created but no newly started backups can be assigned to it.
6

Click Create.

Edit an Existing File System Store

Once created, file system stores are listed directly on the Snapshot Storage page in a table. Each row contains the settings for each File System Store.

1

Navigate to the Snapshot Storage page.

  1. Click the Admin link.
  2. Click the Backup tab.
  3. Click the Snapshot Storage page.
2

Go to the row for the filestore you want to edit.

3

In the Store Path column, edit the necessary fields:

Field Contents
Store Path The location where file system-based backups are stored on the Ops Manager server.
Assignment Labels A comma-separated list of labels to assign the filestores to specific groups.
Load Factor

A proportional value of how backup jobs are assigned to the given snapshot store compared to other snapshot stores.

By default snapshot stores assign one shard per snapshot store.

If a snapshot store has more than one shard assigned, it would result in one snapshot store being backed up often than the another. This ratio of backup jobs to shards can be changed using the load factor.

An example of how the Load Factor affects backups:

You are backing up a 5 shard cluster. Your deployment has filestore (A) with one shard and blockstore (B) with four shards. These blockstores should not get equally distribution of backup jobs, as B is four times larger than A. B should get a Load Factor of 4 and A should get a Load Factor or 1.
Write Concern Select the proper Write Concern.
4

Check the checkbox in the Assignment Enabled column.

5

Click Save.

6

Restart all the Ops Manager instances, including those running activated Backup Daemons.

Warning

After you save changes to the connection string, you must restart all the Ops Manager instances, including those running activated Backup Daemons, for the changes to take effect.

Delete a File System Store

1

Navigate to the Snapshot Storage page.

  1. Click the Admin link.
  2. Click the Backup tab.
  3. Click the Snapshot Storage page.
2

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.