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.

Deploy a Standalone MongoDB Instance

On this page

Overview

You can deploy a standalone MongoDB instance managed by Ops Manager. Use standalone instances for testing and development. Do not use these deployments, which lack replication and high availability, for production systems. For all production deployments use replica sets. See Deploy a Replica Set for production deployments.

Prerequisites

You must provision a server to which to deploy. For testing purposes, you can use your localhost.

Procedure

1

Click the Deployment tab, then click the Deployment page.

2

Click the Add button and select New Standalone.

3

Configure the standalone MongoDB instance.

Enter information as required and click Apply.

The Auth Schema Version field determines the schema for storing user data. MongoDB 3.0 uses a different schema for user data than previous versions. For compatibility information, see the MongoDB Release Notes.

If you run MongoDB 3.0 or higher, you can choose a storage engine by selecting Advanced Options and adding the engine option. For information on storage engines, see Storage in the MongoDB manual.

For descriptions of Advanced Options, see Advanced Options for MongoDB Deployments.

4

Click Review & Deploy to review your changes.

5

Review and approve your changes.

Ops Manager displays your proposed changes.

  1. If they are acceptable, click Confirm & Deploy.
  2. If they are unacceptable, click Cancel and you can make additional changes.

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