(DOCSP-44418) [OM] Backport DOCSP-43740 to v7.0 (#470) (#476)

Standardizing FCV:
- Replacing all instances of fCV or FCV with substitution |fcv|
- Replacing all instances of "|fcv| of \<ver-num\>" with "|fcv|
\<ver-num\>"

------------------------------------------------------

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

[STAGING](https://deploy-preview-470--10gen-docs-ops-manager.netlify.app/)
- [LATEST BUILD
LOG](https://app.netlify.com/sites/10gen-docs-ops-manager/deploys/67095bb9c4044c000895880c)

- [ ]
[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).
- [x] Resolve any new warnings or errors in the build.
- [x] Proofread for spelling and grammatical errors.
- [x] Check staging for rendering issues.
- [x] Confirm links are working.

---------

Backport DOCSP-43740 to v7.0 

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

### 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: Elyse Foreman <[email protected]>

Author: elyse-mdb

source/application.txt

@@ -81,20 +81,20 @@ 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
+one version earlier. For MongoDB 4.2, the |fcv| can be ``4.0`` or
 ``4.2``.
 
 .. tabs::
 
-   .. tab:: FCV 4.2 or later
+   .. 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
+   .. tab:: |fcv| 4.0 or earlier
       :tabid: fcv40
 
       Once backup has started, |mms| backs up the data as an ongoing
@@ -127,7 +127,7 @@ appear in the snapshot data.
 .. tabs::
    :hidden:
 
-   .. tab:: FCV 4.2 or later
+   .. tab:: |fcv| 4.2 or later
       :tabid: fcv42
 
       |mms| can back up data as a full or incremental backup. |mms|
@@ -139,7 +139,7 @@ appear in the snapshot data.
 
       Incremental backups reduce network transfer and storage costs.
 
-   .. tab:: FCV 4.0 or earlier
+   .. tab:: |fcv| 4.0 or earlier
       :tabid: fcv40
 
       How much storage capacity you need depends on both the number
@@ -187,13 +187,13 @@ a selected point between snapshots.
 .. tabs::
    :hidden:
 
-   .. tab:: FCV 4.2 or later
+   .. 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
+   .. tab:: |fcv| 4.0 or earlier
       :tabid: fcv40
 
       - For :manual:`sharded clusters </reference/glossary/#std-term-sharded-cluster>`, you can restore
@@ -211,7 +211,7 @@ the snapshot storage. You can restore the snapshot:
 .. tabs::
    :hidden:
 
-   .. tab:: FCV 4.2 or later
+   .. tab:: |fcv| 4.2 or later
       :tabid: fcv42
 
       When you restore from a point in time, |mms| does the following:
@@ -226,7 +226,7 @@ the snapshot storage. You can restore the snapshot:
       backup. This affects the amount of time a point-in-time restore
       can cover.
 
-   .. tab:: FCV 4.0 or earlier
+   .. tab:: |fcv| 4.0 or earlier
       :tabid: fcv40
 
       When you restore from a checkpoint or point in time, |mms| does the following:

source/core/requirements.txt

@@ -54,7 +54,7 @@ for all |onprem| components that it serves:
    You want to serve both the |onprem| application and a
    :opsmgr:`Backup Daemon </reference/glossary/#std-term-backup-daemon>` on one host. 
    This |onprem| configuration will manage and monitor 300 MongoDB hosts,
-   back up 200 hosts, and run FCV 4.2 or later. The
+   back up 200 hosts, and run |fcv| 4.2 or later. The
    total disk capacity of all databases being backed up is 4 TB. 
    The total requirements would be:
 

source/includes/fact-index-rolling-build.rst

@@ -30,8 +30,7 @@ availability, |mms| removes one node from the cluster at a time
 starting with a :manual:`secondary </reference/glossary/#std-term-secondary>`.
 
 After you build an index in a rolling fashion, if your MongoDB database
-runs with an :manual:`FCV 
-</reference/command/setFeatureCompatibilityVersion>`
+runs with an |fcv-link|
 less than ``4.2``, :doc:`resync the head database 
 </tutorial/resync-backup>` to ensure that the head database takes the 
 new index into account.

source/includes/setting-fileConf-mms.backup.journal.heads.rst

@@ -10,7 +10,7 @@
    enable or disable journaling for the :opsmgr:`head database </reference/glossary/#std-term-head-database>` of a
    single backup job.
 
-   FCV |fcv-link| ``4.2`` and later use :term:`backup cursors 
+   |fcv-link| ``4.2`` and later use :term:`backup cursors 
    <backup cursor>` instead of :opsmgr:`head databases </reference/glossary/#std-term-head-database>` 
    for backups.
 

source/index.txt

@@ -73,20 +73,20 @@ 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
+one version earlier. For MongoDB 4.2, the |fcv| can be ``4.0`` or
 ``4.2``.
 
 .. tabs::
 
-   .. tab:: FCV 4.2 or later
+   .. 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
+   .. tab:: |fcv| 4.0 or earlier
       :tabid: fcv40
 
       Once backup has started, |mms| backs up the data as an ongoing
@@ -119,7 +119,7 @@ appear in the snapshot data.
 .. tabs::
    :hidden:
 
-   .. tab:: FCV 4.2 or later
+   .. tab:: |fcv| 4.2 or later
       :tabid: fcv42
 
       |mms| can back up data as a full or incremental backup. |mms|
@@ -131,7 +131,7 @@ appear in the snapshot data.
 
       Incremental backups reduce network transfer and storage costs.
 
-   .. tab:: FCV 4.0 or earlier
+   .. tab:: |fcv| 4.0 or earlier
       :tabid: fcv40
 
       How much storage capacity you need depends on both the number
@@ -175,13 +175,13 @@ a selected point between snapshots.
 .. tabs::
    :hidden:
 
-   .. tab:: FCV 4.2 or later
+   .. 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
+   .. tab:: |fcv| 4.0 or earlier
       :tabid: fcv40
 
       - For :manual:`sharded clusters </reference/glossary/#std-term-sharded-cluster>`, you can restore
@@ -199,7 +199,7 @@ the snapshot storage. You can restore the snapshot:
 .. tabs::
    :hidden:
 
-   .. tab:: FCV 4.2 or later
+   .. tab:: |fcv| 4.2 or later
       :tabid: fcv42
 
       When you restore from a point in time, |mms| does the following:
@@ -214,7 +214,7 @@ the snapshot storage. You can restore the snapshot:
       backup. This affects the amount of time a point-in-time restore
       can cover.
 
-   .. tab:: FCV 4.0 or earlier
+   .. tab:: |fcv| 4.0 or earlier
       :tabid: fcv40
 
       When you restore from a checkpoint or point in time, |mms| does the following:

source/reference/faq/faq-backup.txt

@@ -56,7 +56,7 @@ Does Backup Work with All Types of Deployments?
 
 - For MongoDB 4.2 and later, see
   :ref:`Backup Considerations for Databases <4.2-backup-considerations>`.
-- For any MongoDB with |fcv| of ``4.0`` and earlier databases, Backup
+- For any MongoDB with |fcv| ``4.0`` and earlier databases, Backup
   doesn't support standalone deployments. Backup has full
   support for replica sets and sharded clusters.
 
@@ -87,7 +87,7 @@ Will Backup Impact My Production Databases?
 .. note::
 
    This answer applies only to databases running MongoDB with |fcv|
-   of ``4.0`` and earlier
+   ``4.0`` and earlier
 
 The Backup feature typically has minimal impact on production MongoDB
 deployments. This impact performs similar to that of adding a new
@@ -152,7 +152,7 @@ Legacy Backup Agent
 Backup capability has been moved to the {+mdbagent+} with Backup
 activated. This replaces the individual Backup Agent. This information
 covers issues unique to the legacy Backup Agent. All of this
-information applies to MongoDB databases running |fcv| of ``4.0`` or
+information applies to MongoDB databases running |fcv| ``4.0`` or
 earlier.
 
 Where Should I Run The Backup Agent?
@@ -263,8 +263,7 @@ How Does |mms| Provide Point-in-Time Restores?
 
 .. important::
 
-   |onprem| 4.2.13 and later supports this feature with |fcv| of
-   ``4.2`` or later.
+   |onprem| 4.2.13 and later supports this feature with |fcv| ``4.2`` or later.
 
 When you trigger the restore, |mms| creates a link to this snapshot.
 Once clicked, |mms| retrieves chunks from the Snapshot Store and
@@ -377,7 +376,7 @@ What Conditions Require a Resync?
 
 .. important::
 
-   This feature is incompatible with MongoDB 4.2 with |fcv| of ``4.2``.
+   This feature is incompatible with MongoDB 4.2 with |fcv| ``4.2``.
 
 If the Backup Agent's :term:`tailing cursor <tailable cursor>` cannot
 keep up with your deployment's :manual:`oplog </reference/glossary/#std-term-oplog>`, then you must

source/tutorial/enable-backup.txt

@@ -20,10 +20,10 @@ You can back up your MongoDB deployment.
 
 .. tabs::
 
-   .. tab:: FCV 4.2 or later
+   .. tab:: |fcv| 4.2 or later
       :tabid: fcv42
 
-   .. tab:: FCV 4.0 or earlier
+   .. tab:: |fcv| 4.0 or earlier
       :tabid: fcv40
 
 Prerequisites
@@ -44,26 +44,20 @@ A Replica Set must:
 .. tabs::
    :hidden:
 
-   .. tab:: FCV 4.2 or later
+   .. tab:: |fcv| 4.2 or later
       :tabid: fcv42
 
-      - Be monitored by |mms|.
-
-      - Run MongoDB Enterprise with an |fcv| of 4.2 or later.
-
-      - Have an active :manual:`primary </reference/glossary/#std-term-primary>` node.
-
-      - Have one node with :manual:`WiredTiger </core/wiredtiger>` set
-        as its :ref:`storage engine <considerations-backup-storage-engine>`.
-
-   .. tab:: FCV 4.0 or earlier
-      :tabid: fcv40
-
-      - Be monitored by |mms|.
+.. tabs::
+   :hidden:
 
-      - Run MongoDB version 2.6 to 4.0.
+   .. tab:: |fcv| 4.2 or later
+      :tabid: fcv42
 
-      - Have an active :manual:`primary </reference/glossary/#std-term-primary>` node.
+- Be monitored by |mms|.
+- Run MongoDB Enterprise with an |fcv| of 4.2 or later.
+- Have an active :manual:`primary </reference/glossary/#std-term-primary>` node.
+- Have one node with :manual:`WiredTiger </core/wiredtiger>` set as its
+  :ref:`storage engine <considerations-backup-storage-engine>`. 
 
 Sharded Cluster Requirements
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -73,39 +67,27 @@ A Sharded Cluster must:
 .. tabs::
    :hidden:
 
-   .. tab:: FCV 4.2 or later
+   .. tab:: |fcv| 4.2 or later
       :tabid: fcv42
 
-      - Be monitored by |mms|.
-
-      - Run MongoDB Enterprise with an |fcv| of 4.2 or later on all
-        nodes including the config server.
-
-      - Have an active :manual:`primary </reference/glossary/#std-term-primary>` node of each shard and the
-        config server.
-
-      - Have one node per shard or config server with
-        :manual:`WiredTiger </core/wiredtiger>` set as its
-        :ref:`storage engine <considerations-backup-storage-engine>`.
-        
-   .. tab:: FCV 4.0 or earlier
-      :tabid: fcv40
-
-      - Be monitored by |mms| including at least one |mongos| in the
-        cluster.
-
-      - Run MongoDB version 2.6 to 4.0.
+.. tabs::
+   :hidden:
 
-      - Have all :manual:`config servers  </reference/glossary/#std-term-config-server>` running. The
-        config server |mongod| processes must be started with either
-        the ``--configsvr`` command line option or the
-        ``{ "clusterRole": "configsvr" }`` setting in the ``mongod``
-        configuration file.
+   .. tab:: |fcv| 4.2 or later
+      :tabid: fcv42
 
-      - Complete the balancing round in less than one hour.
+- Be monitored by |mms|.
+- Run MongoDB Enterprise with an |fcv| of 4.2 or later on all nodes
+  including the config server. 
+- Have an active :manual:`primary
+  </reference/glossary/#std-term-primary>` node of each shard and the
+  config server.
+- Have one node per shard or config server with :manual:`WiredTiger
+  </core/wiredtiger>` set as its :ref:`storage engine
+  <considerations-backup-storage-engine>`.
 
-MongoDB FCV 4.2 Compatibility
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+MongoDB Compatibility
+~~~~~~~~~~~~~~~~~~~~~
 
 All |fcv| 4.2 and later databases must fulfill the appropriate
 :ref:`backup considerations <4.2-backup-considerations>`.
@@ -126,7 +108,7 @@ Procedure
 .. tabs::
    :hidden:
 
-   .. tab:: FCV 4.2 or later
+   .. tab:: |fcv| 4.2 or later
       :tabid: fcv42
 
       You can back up your entire MongoDB deployment.
@@ -139,7 +121,7 @@ Procedure
 
       .. include:: /includes/steps/create-backup-wt.rst
 
-   .. tab:: FCV 4.0 or earlier
+   .. tab:: |fcv| 4.0 or earlier
       :tabid: fcv40
 
       You can choose to back up all databases and collections in your

source/tutorial/nav/restore-overview.txt

@@ -97,7 +97,7 @@ To perform automated restores:
      :manual:`setFeatureCompatibilityVersion </reference/command/setFeatureCompatibilityVersion>`.
 
 - Review the following compatibility matrix for the supported source cluster
-  |fcv| of each MongoDB version. The MongoDB version of each host in
+  each MongoDB version. The MongoDB version of each host in
   the target cluster *must* support the |fcv| of the snapshot of the
   source cluster.