DOCSP-43363 EOL MongoDB 4.2 and below in Ops Manager 8.0 (#368)

<!-- Add a description of your PR here (optional) -->

- [DOCSP-43363](https://jira.mongodb.org/browse/DOCSP-43363)

### Self-Review Checklist

- [ ]
[Define](https://wiki.corp.mongodb.com/display/DE/Taxonomy+tagging+instructions)
taxonomy
[values](https://wiki.corp.mongodb.com/display/DE/Docs+Taxonomy) at top
of page.
- [ ] Add genre facets (tutorial or reference), as in this [example
PR](10gen/cloud-docs#5042).
- [ ] Add programmingLanguage (if necessary).
- [ ] Add meta keywords (if necessary).
- [ ] Resolve any new warnings or errors in the build.
- [ ] Proofread for spelling and grammatical errors.
- [ ] Check staging for rendering issues.
- [ ] Confirm links are working.

---------

Co-authored-by: John Williams <[email protected]>

Author: kanchana-mongodb

config/redirects

@@ -1077,3 +1077,6 @@ raw: ${bucket_prefix}/v3.5/troubleshooting -> ${base}/master/troubleshooting/
 [v5.0-*]: ${bucket_prefix}/${version}/reference/api/whitelist-get-for-current-user -> ${base}/${version}/reference/api/access-list-get-for-current-user
 [v5.0-*]: ${bucket_prefix}/${version}/reference/api/whitelist-get-for-ip-address -> ${base}/${version}/reference/api/access-list-get-for-ip-address
 [v5.0-*]: ${bucket_prefix}/${version}/reference/api/whitelist -> ${base}/${version}/reference/api/access-list
+
+# DOCSP-43363 EOL of MDB versions less than and equal to v4.2
+[v8.0-*]: ${bucket_prefix}/${version}/reference/api/checkpoints -> ${base}/${version}/reference/api/nav/backup-and-restore

source/admin/backup/resource-usage-page.txt

@@ -26,16 +26,6 @@ basis for all projects for which you enabled backup.
    * - Column Title
      - Content
 
-   * - HEAD Usage
-     - Displays the following statistics for the :opsmgr:`head database </reference/glossary/#std-term-head-database>`
-       of any backup job with |fcv-link| 4.0 or earlier:
-
-       - :dbcommand:`Data Size <dbStats>`
-       - :dbcommand:`Storage Size <dbStats>`
-       - File Size: The sum of the uncompressed size of each file in
-         the HEAD database
-       - :manual:`Storage Engine </core/storage-engines>`
-
    * - Oplog Receiving (last 24 hours)
      - Displays statistics for oplog throughput over the past 24 hours.
 

source/application.txt

@@ -77,39 +77,14 @@ snapshots of data from the MongoDB processes you have specified.
 Backup Workflow
 ~~~~~~~~~~~~~~~
 
-Backups rely upon the
-:manual:`MongoDB version compatibility</reference/command/setFeatureCompatibilityVersion>`
-of your database.
-This Feature Compatibility Version ranges from the current version to
-one version earlier. For MongoDB 4.2, the FCV can be ``4.0`` or
-``4.2``.
+Backups rely upon the :manual:`MongoDB version compatibility
+</reference/command/setFeatureCompatibilityVersion>` of your database.
+For MongoDB 4.4, the FCV can be ``4.2`` or ``4.4``. 
 
-.. tabs::
+.. include:: /includes/backup/wtchk-process-overview-main-om.rst
 
-   .. tab:: FCV 4.2 or later
-      :tabid: fcv42
-
-      .. include:: /includes/backup/wtchk-process-overview-main-om.rst
-
-      The {+mdbagent+} uses WiredTiger's incremental backup cursor to
-      capture the incremental changes.
-
-   .. tab:: FCV 4.0 or earlier
-      :tabid: fcv40
-
-      Once backup has started, |mms| backs up the data as an ongoing
-      and continuous process. This process continues creating snapshots
-      as long as the head database remains synchronized with the
-      database.
-
-      .. include:: /includes/backup/legacy-process-overview-main-om.rst
-
-      The {+mdbagent+} then tails each replica set's :manual:`oplog </reference/glossary/#std-term-oplog>`
-      to maintain on disk a standalone database, called a
-      :opsmgr:`head database </reference/glossary/#std-term-head-database>`. |mms| maintains one
-      head database for each backed-up replica set. The head
-      database stays consistent with the original :manual:`primary </reference/glossary/#std-term-primary>` up
-      to the last oplog that the {+mdbagent+} supplies.
+The {+mdbagent+} uses WiredTiger's incremental backup cursor to capture
+the incremental changes.  
 
 The backup process works in this manner regardless of how snapshots are
 stored.
@@ -121,57 +96,47 @@ Backup takes and stores snapshots based on a user-defined
 :ref:`snapshot retention policy <snapshot-frequency-and-retention>`.
 Sharded cluster snapshots temporarily stop the balancer. The snapshots
 then can insert a marker token into all shards and config servers in
-the cluster. |mms| takes a :manual:`snapshot </reference/glossary/#std-term-snapshot>` when the marker tokens
+the cluster. |mms| takes a :manual:`snapshot
+</reference/glossary/#std-term-snapshot>` when the marker tokens 
 appear in the snapshot data.
 
-.. tabs::
-   :hidden:
-
-   .. tab:: FCV 4.2 or later
-      :tabid: fcv42
-
-      |mms| can back up data as a full or incremental backup. |mms|
-      requires a full backup:
-
-      - For your first backup.
-      - After a snapshot has been deleted.
-      - If the blockstore block size has been changed.
+How much storage capacity you need depends on both the number of
+snapshots and the type of snapshot storage you choose. The following
+table outlines the differences in snapshot stores: 
 
-      Incremental backups reduce network transfer and storage costs.
+.. list-table::
+   :header-rows: 1
+   :widths: 25 75
 
-   .. tab:: FCV 4.0 or earlier
-      :tabid: fcv40
+   * - Snapshot Store
+     - Description
 
-      How much storage capacity you need depends on both the number
-      of snapshots and the type of snapshot storage you choose. The
-      following table outlines the differences in snapshot stores:
+   * - MongoDB blockstore
+     - Only the differences between each successive :manual:`snapshot
+       </reference/glossary/#std-term-snapshot>` are stored. Compression
+       and block-level :term:`deduplication` reduce the size of snapshot
+       data. 
 
-      .. list-table::
-         :header-rows: 1
-         :widths: 25 75
+   * - |aws| |s3| bucket
+     - Only the differences between each successive :manual:`snapshot
+       </reference/glossary/#std-term-snapshot>` are stored. Compression
+       and block-level :term:`deduplication` reduce the size of snapshot
+       data. 
 
-         * - Snapshot Store
-           - Description
+   * - |s3| bucket
+     - Only the differences between each successive :manual:`snapshot
+       </reference/glossary/#std-term-snapshot>` are stored. Compression
+       and block-level :term:`deduplication` reduce the size of snapshot
+       data. 
 
-         * - MongoDB blockstore
-           - Only the differences between each successive
-             :manual:`snapshot </reference/glossary/#std-term-snapshot>` are stored. Compression and
-             block-level :term:`deduplication` reduce the size of
-             snapshot data.
+All snapshots represent a full backup. |mms| can back up data as a full
+or incremental backup. |mms| requires a full backup:  
 
-         * - |aws| |s3| bucket
-           - Only the differences between each successive
-             :manual:`snapshot </reference/glossary/#std-term-snapshot>` are stored. Compression and
-             block-level :term:`deduplication` reduce the size of
-             snapshot data.
+- For your first backup.
+- After a snapshot has been deleted.
+- If the blockstore block size has been changed.
 
-         * - |s3| bucket
-           - Only the differences between each successive
-             :manual:`snapshot </reference/glossary/#std-term-snapshot>` are stored. Compression and
-             block-level :term:`deduplication` reduce the size of
-             snapshot data.
-
-      All snapshots represent a full backup.
+Incremental backups reduce network transfer and storage costs.
 
 To learn more about how to configure backups, see
 :doc:`Backup Configuration Options </core/backup-preparations>`.
@@ -184,61 +149,25 @@ Restore Data
 Backup can restore data from a complete scheduled snapshot or from
 a selected point between snapshots.
 
-.. tabs::
-   :hidden:
-
-   .. tab:: FCV 4.2 or later
-      :tabid: fcv42
-
-      You can restore :manual:`sharded clusters </reference/glossary/#std-term-sharded-cluster>` and
-      :manual:`replica sets </reference/glossary/#std-term-replica-set>` from selected points in time.
-
-   .. tab:: FCV 4.0 or earlier
-      :tabid: fcv40
-
-      - For :manual:`sharded clusters </reference/glossary/#std-term-sharded-cluster>`, you can restore
-        from :ref:`checkpoints <checkpoint>` between snapshots.
-
-      - For :manual:`replica sets </reference/glossary/#std-term-replica-set>`, you can restore from
-        selected points in time.
+You can restore :manual:`sharded clusters
+</reference/glossary/#std-term-sharded-cluster>` and :manual:`replica
+sets </reference/glossary/#std-term-replica-set>` from selected points
+in time.
 
 When you restore from a :manual:`snapshot </reference/glossary/#std-term-snapshot>`, |mms| reads directly from
 the snapshot storage. You can restore the snapshot:
 
 - To another cluster.
 - To download the snapshot files from an |https| link.
 
-.. tabs::
-   :hidden:
-
-   .. tab:: FCV 4.2 or later
-      :tabid: fcv42
-
-      When you restore from a point in time, |mms| does the following:
+When you restore from a point in time, |mms| does the following:
 
-      1. Restores a full snapshot from the snapshot storage.
-      #. Applies stored :manual:`oplogs </reference/glossary/#std-term-oplog>` until it reaches the 
-         specified point.
-      #. Delivers the snapshot and oplog updates using the same
-         |https| mechanisms.
-
-      You can configure how much of the oplog you want to keep per
-      backup. This affects the amount of time a point-in-time restore
-      can cover.
-
-   .. tab:: FCV 4.0 or earlier
-      :tabid: fcv40
-
-      When you restore from a checkpoint or point in time, |mms| does the following:
-
-      1. Restores a full snapshot from the snapshot storage. 
-      #. Applies stored :manual:`oplogs </reference/glossary/#std-term-oplog>` until it reaches the
-         specified point. 
-      #. Delivers the snapshot and oplog updates using the same |https| mechanisms. 
-         To enable checkpoints, see :ref:`enable-cluster-checkpoints`.
-
-      You can configure how much of the oplog you want to keep per
-      backup. This affects how much time a checkpoint and
-      point-in-time restore can cover.
+1. Restores a full snapshot from the snapshot storage.
+#. Applies stored :manual:`oplogs </reference/glossary/#std-term-oplog>`
+   until it reaches the specified point.
+#. Delivers the snapshot and oplog updates using the same |https| mechanisms.
+
+You can configure how much of the oplog you want to keep per backup.
+This affects the amount of time a point-in-time restore can cover.
 
 .. include:: /includes/extracts/toc-application-introduction.rst

source/core/backup-overview.txt

@@ -11,25 +11,10 @@ Backup Process
    :class: singlecol
 
 Backups depend upon which :manual:`version of MongoDB your database is
-compatible </reference/command/setFeatureCompatibilityVersion>`.  This
-Feature Compatibility Version ranges from the current version to one
-version earlier. For MongoDB 4.2, the FCV can be ``4.0`` or ``4.2``.
+compatible </reference/command/setFeatureCompatibilityVersion>`. For
+MongoDB 4.4, the FCV can be ``4.2`` or ``4.4``. 
 
-.. tabs::
-
-   .. tab:: FCV 4.2 or later
-      :tabid: fcv42
-
-      .. include:: /includes/backup/wtchk-process-overview.rst
-         
-   .. tab:: FCV 4.0 or earlier
-      :tabid: fcv40
-
-      Once backup has started, |mms| backs up the data as a ongoing and
-      continuous process. This process continues creating snapshots as
-      long as the head database remains synchronized with the database.
-
-      .. include:: /includes/backup/legacy-process-overview.rst
+.. include:: /includes/backup/wtchk-process-overview.rst
 
 .. _backup-stages:
 
@@ -45,66 +30,33 @@ Operational States
 
 The following table lists the states of a backup job:
 
-.. tabs::
-   :hidden:
-
-   .. tab:: FCV 4.2 or later
-      :tabid: fcv42
-
-      .. list-table::
-         :widths: 60 20 20
-         :header-rows: 1
-
-         * - State
-           - Retain Old Snapshots
-           - Create New Snapshots
-
-         * - ``Active``
-           - Yes
-           - Yes
-
-         * - ``Stopped``
-           - Yes
-           - No
-
-         * - ``Inactive``
-           - No
-           - No
-
-         * - ``Misconfigured``
-	   - Yes
-	   - No
-
-      .. note::
+.. list-table::
+   :widths: 60 20 20
+   :header-rows: 1
 
-         The ``Misconfigured`` state applies only to :ref:`regional-backup`.
+   * - State
+     - Retain Old Snapshots
+     - Create New Snapshots
 
-   .. tab:: FCV 4.0 or earlier
-      :tabid: fcv40
+   * - ``Active``
+     - Yes
+     - Yes
 
-      .. list-table::
-         :widths: 20 27 27 26
-         :header-rows: 1
+   * - ``Stopped``
+     - Yes
+     - No
 
-         * - State
-           - Retain Old Snapshots
-           - Create New Snapshots
-           - Apply Oplogs
+   * - ``Inactive``
+     - No
+     - No
 
-         * - ``Active``
-           - Yes
-           - Yes
-           - Yes
+   * - ``Misconfigured``
+     - Yes
+     - No
 
-         * - ``Stopped``
-           - Yes
-           - No
-           - No
+.. note::
 
-         * - ``Inactive``
-           - No
-           - No
-           - No
+   The ``Misconfigured`` state applies only to :ref:`regional-backup`.
 
 Change Operational States
 ~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -113,18 +65,7 @@ Once backup jobs are active for a :opsmgr:`project </reference/glossary/#std-ter
 further intervention until they are stopped or terminated. The operator
 can change the state of a backup in the following ways:
 
-.. tabs::
-   :hidden:
-
-   .. tab:: FCV 4.2 or later
-      :tabid: fcv42
-
-      .. include:: /includes/backup/wtchk-process-change-op-state.rst
-
-   .. tab:: FCV 4.0 or earlier
-      :tabid: fcv40
-
-      .. include:: /includes/backup/legacy-process-change-op-state.rst
+.. include:: /includes/backup/wtchk-process-change-op-state.rst
 
 .. _backup-initial-sync:
 
@@ -133,25 +74,7 @@ Backup Process Flows
 
 Once created, a backup job goes through the following process flow:
 
-.. tabs::
-   :hidden:
-
-
-   .. tab:: FCV 4.2 or later
-      :tabid: fcv42
-
-      .. include:: /includes/backup/wtchk-process-initial-backup.rst
-
-   .. tab:: FCV 4.0 or earlier
-      :tabid: fcv40
-
-      **Initial Backup**
-
-      .. include:: /includes/backup/legacy-process-initial-backup.rst
-
-      **Subsequent Backups**
-
-      .. include:: /includes/backup/legacy-process-subsequent-backup.rst
+.. include:: /includes/backup/wtchk-process-initial-backup.rst
 
 .. _regional-backup: