[DOCS-13135] Add What's supported for MongoDB 4.2 backup and what's not. Created: 18/Oct/19  Updated: 29/Oct/23  Resolved: 30/Oct/19

Status: Closed
Project: Documentation
Component/s: Ops Manager
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Joshua Maag Assignee: Anthony Sansone (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Backports
backported by DOCS-13190 Backport DOCS-13135 to v4.2 Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
DOCS-13190 Backport DOCS-13135 to v4.2 Backport Sub-Task Closed Anthony Sansone  
Participants:
Days since reply: 4 years, 14 weeks, 5 days ago
Epic Link: DOCSP-5050
Story Points: 2

 Description   

Description

There is a rather large gap here for clients on what is currently supported in Ops Manager Backups for 4.2. Since it's being rolled out in chunks we need a better way to understand what's supported when.

We should have more detail here than:

Backup support for MongoDB 4.2 with "featureCompatibilityVersion" : 4.2 is currently extremely limited. Support will be extended in future releases of Ops Manager.

What's missing here is what is current supported. It would be good to have a table of sorts with a list of supported features and the minor point release as it's released. Examples of this would be: Replica Set snapshot - 4.2.0, Sharded cluster snapshots - 4.2.4(this probably needs to be verified)

The next section discusses some requires and some non-supported lists. This is quite confusing to the customer. It might be better to do something like this:

Feature MongoDB 4.2 MongoDB 4.2 with featureCompatibilityVersion < 4.2 <= MongoDB 4.0
New Backup x    
Backup with Daemons   x x
Replica Set Snapshots x x x
Enterprise Support x x x
Community Support   x x

This is a crude example above, but would give the customers a better quick glance of what they need for backup.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Anthony Sansone (Inactive) [ 01/Nov/19 ]

Awaiting backport.

Comment by Githook User [ 30/Oct/19 ]

Author:

{'username': 'atsansone', 'email': 'tony.sansone@mongodb.com', 'name': 'Anthony Sansone'}

Message: (DOCS-13135): Added Backup Current Capability Table.
Branch: master
https://github.com/10gen/mms-docs/commit/51f8919b982da7bcf81fe239e87b3c9a0941885a

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