[DOCS-12311] Compatibility between dumps/restores using different versions Created: 02/Jan/19 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | tools |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Arnie Listhaus | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 3 |
| Labels: | docs-backup, docs-restore | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 1 year, 14 weeks, 2 days ago | ||||||||
| Epic Link: | DOCSP-1769 | ||||||||
| Story Points: | 0.5 | ||||||||
| Description |
DescriptionSome of our customer have retention requirements to meet that cause them to need to store N years of backups. Many of our larger customers are unable to keep up with our release schedule and stay on older versions of our software. In both cases, customers have an expectation that they can restore dumps of databases taken from earlier versions into the current version. Our current stance from a support perspective, is that we do not guarantee that dumps from previous releases will be compatible with current versions. But that does not appear to actually be stated anywhere in the documentation. This ticket is a request to formalize our expectation with respect to compatibility between dumps taken on older server versions and being able to restore them to current versions.
Scope of changes
Impact to Other DocsThis may have some impact on the Atlas docs, as mongodump -> mongorestore acts as a sort of catch-all vector for users that cannot use the other available import methods. We do not currently speak to versioning on the import docs. cc jonathan.destefano@10gen.com MVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |
| Comment by Arnie Listhaus [ 15/Jan/19 ] |
|
The metadata files created by 2.4 can contain the keyword create e.g. {{ { "options" : }}. This keyword is incompatible with current releases. Unfortunately, there is no fix we can provide for the 2.4 release. That said, you could modify the metadata files to remove the create keyword (and the associated value) and that would bypass this particular issue. |
| Comment by Shannon Bradshaw (Inactive) [ 03/Jan/19 ] |
|
benjamin.cefalo what's your take on this? |