Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments. Click here to view the documentation for the current version.

Upgrading MongoDB

Review the following topics

Supported versions

With Smart IT 1.4 and BMC My IT 3.1, Mongo DB 2.6, 3.0.xx and 3.2.xx are supported. BMC recommends that you upgrade to version 3.2.x. 

If your current environment is using Mongo DB 2.4, you must upgrade to the latest version.

When to upgrade

The bundled MongoDB version can only be used for a fresh installation. In an upgrade scenario, the MongoDB is not upgraded automatically by the installer. In an upgrade scenario, you must manually upgrade the MongoDB.

  • If your existing MongoDB version is 2.4.x, upgrade the MongoDB as part of the pre-installation activities.
  • If your existing MongoDB version is 2.6.x, upgrade the MongoDB as part of the post-installation activities.

Upgrade paths

To upgrade to Mongo DB 3.2.xx, the following upgrade paths are available

  • You can directly upgrade to Mongo DB 3.2.xx from version 3.0.xx.
  • To upgrade from a version earlier to 2.6, you must first upgrade to 2.6 and then upgrade to 3.0.xx. See  Upgrading MongoDB to version 2.6 in the BMC Remedy with Smart IT online documentation.

Upgrade process for different deployments

Depending on you deployment, click on the following links:

DeploymentUpgrade process
Upgrade MongoDB replica setYou can upgrade from MongoDB 3.0 replica set to 3.2.xx by upgrading the members individually while the other members are available.

Replica set failover is not instant and will render the set unavailable to accept writes until the failover process completes. This usually takes no more than 3-5 minutes, schedule the upgrade procedure during a scheduled maintenance window.

Upgrade standalone MongoDBWhen you upgrade a standalone MongoDB, the MongoDB server is down during the upgrade process.

Related topics

Deploying MongoDB as a replica set for fresh installation.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Ajit Singh

    Under Upgrade Path, I don't see upgrade from 2.6 to 3.2.xx. Can we please include it here?

    Apr 14, 2016 12:09
    1. Michele Marques

      I will confirm whether you can go directly from 2.6 to 3.2.xx.

      Apr 19, 2016 04:34
    1. Amit Durgapal

      Hi Ajit,

      You cannot directly upgrade from MongoDB 2.6 to MongoDB 3.2.xx. You first need to upgrade to 3.0 before you proceed to upgrade to 3.2.

       Regards,

      Amit

      May 16, 2016 05:44