[SERVER-7836] Upgrade path from 2.0.X to 2.2.X Created: 04/Dec/12  Updated: 15/Feb/13  Resolved: 04/Dec/12

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 2.0.2, 2.0.4, 2.0.6, 2.0.7, 2.2.1
Fix Version/s: None

Type: Question Priority: Minor - P4
Reporter: Darren Gruber Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

https://mms.10gen.com/host/chartReplicaSetHosts/4e56a70014587819403c93d0/fileproxy (2.0.2)
https://mms.10gen.com/host/chartReplicaSetHosts/4e56a70014587819403c93d0/tmg (2.0.4)


Participants:

 Description   

We're starting a project to upgrade all our instances to the latest stable version (2.2.2). I've been told that the upgrade process is as simple as replacing the mongod binary and restarting the server but we wanted to verify with you first that this would have no adverse effects on the data/indexes/etc. All our boxes are at least 2.0.X so I wouldn't imagine there would be a huge problem jumping a minor version but it doesn't hurt to check.

Thanks!
Darren



 Comments   
Comment by Scott Hernandez (Inactive) [ 04/Dec/12 ]

Here are the release notes for 2.2 to get you started: http://docs.mongodb.org/manual/release-notes/2.2/

Please let us know if you have any issues.

Generated at Thu Feb 08 03:15:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.