[DOCS-9114] Migration from 2.6 to 3.2 Created: 07/Oct/16  Updated: 30/Oct/23  Resolved: 14/Oct/16

Status: Closed
Project: Documentation
Component/s: dochub, drivers, manual, production
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Critical - P2
Reporter: Informatica Venca Assignee: Ravind Kumar (Inactive)
Resolution: Done Votes: 0
Labels: needs_info
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Test - Pre - Prod


Participants:
Days since reply: 7 years, 17 weeks, 5 days ago

 Description   

Hi,
We have a ReplicaSet with 3 members in our production environment and two stand alone for test and pre-production environments with 2.6 version installed.
We'll going to migrate our mongoDB this environments to 3.2 (current version).
We need some documentation or information for to do this change safely and securely.
We see some diferences in the security schema and obiously in the storage with WireTiger. We need to pay atention from some aspect, or we only need to do a backup, and restore in the new servers.

Thanks!



 Comments   
Comment by Ravind Kumar (Inactive) [ 14/Oct/16 ]

I hope the information provided was useful to you. I see there is a support ticket now for helping you track the issue. I am certain our engineers can help you resolve any remaining issues you may have regarding your upgrade.

If you have any other questions or comments regarding our documentation specifically, please feel free to file a new ticket.

Comment by Ravind Kumar (Inactive) [ 07/Oct/16 ]

Hello!

Thank you for filing a DOCS ticket. The documentation project is primarily for issues concerning the MongoDB Documentation. I would be happy to provide you links to some relevant documentation, but your questions would be best answered by contacting one of our support groups.

Our community support engineers at the MongoDB Google Group can provide you with more guidance depending on your organizations MongoDB deployment.

Depending on your organizations service level agreements / objectives, or the complexity of your deployment, it may be helpful to reach out to MongoDB's Professional Services. They can provide specialized assistance for major version upgrades such as the one you are planning for.

As far as documentation goes, please consider the following:

In order to upgrade to MongoDB 3.2, you must first upgrade your 2.6 installation to 3.0.

You can find the upgrade procedures here.

The release notes for MongoDB 3.0 are here.

Consider especially the following sections of the 3.0 release notes:

Once you have upgraded to MongoDB 3.0, you can then proceed to upgrade to MongoDB 3.2

You can find the upgrade procedures here

The release notes for MongoDB 3.2 are here

Consider especially the following sections of the 3.2 release notes:

As far as your questions regarding how best to perform the upgrade, the documentation team cannot provide specific guidance, as every deployment has its own unique needs and requirements. While the provided documentation is a good place to start, I do recommend seeking support through either our community or professional services to fully capture your organizations needs and pain points, and to prevent possible issues from arising during the upgrade process. I can say for certain that backups are an essential step, and should be taken prior to performing the upgrade procedure. You can find our documentation on performing backups here

Please also note that any applications that are using the MongoDB drivers may need to be upgraded to fully support features introduced or deprecated as a part of MongoDB 3.0 or 3.2. Please visit our drivers documentation page to check the driver your application uses. You may also want to audit the methods or commands your application uses and check the documentation for them to see if there have been changes to usage or behavior.

Let me know if you have any questions regarding the provided documentation. Thank you.

Generated at Thu Feb 08 07:57:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.