Details
-
Improvement
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
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.)
Attachments
Issue Links
- backported by
-
DOCS-13190 Backport DOCS-13135 to v4.2
-
- Closed
-