(DOCSP-43830) [OM] Backport DOCSP-43010 to v7.0 (#384)

elyse-mdb · web-flow · commit 57be180ab1d5 · 2024-09-25T11:35:16.000-04:00
## Backport [DOCSP-43010](https://jira.mongodb.org/browse/DOCSP-43010) to v7.0 [This spreadsheet](https://docs.google.com/spreadsheets/d/1M2IlsyV0-6mY-AvBBrX-4uSDtQrbt9zuoXsqIJaVqlk/edit?gid=0#gid=0) tracks the number of nested components on each page, and [this doc](https://docs.google.com/document/d/1yMbng-EPOQ82bAzBTC2VJwIvsUBOSCJh21cGbDoe1a8/edit#heading=h.7hxlffls9cx6) provides guidelines for fixing nested components. ## [DOCSP-43830](https://jira.mongodb.org/browse/DOCSP-43830) ## STAGING 1. [docs/ops-manager/current/admin/backup/daemons-page/ ](https://deploy-preview-374--10gen-docs-ops-manager.netlify.app/admin/backup/daemons-page/)— Unnested 2 notes and 1 example in table. Note: another nested note was in the document under delete-daemon but was not present in the active page. Unnested this, too. 2. [docs/ops-manager/current/admin/backup/groom-priority-page/](https://deploy-preview-374--10gen-docs-ops-manager.netlify.app/admin/backup/groom-priority-page/) — Unnested 1 tip in table 3. [docs/ops-manager/current/admin/backup/jobs-page/](https://deploy-preview-374--10gen-docs-ops-manager.netlify.app/admin/backup/jobs-page/) — Unnested 3 notes and 1 warning in tables. Converted part of 1 note into a bulleted list. 4. [docs/ops-manager/current/admin/backup/restores-page/ ](https://deploy-preview-374--10gen-docs-ops-manager.netlify.app/admin/backup/restores-page/)— No changes, left 1 ``important`` admonition in table. 5. 5. [docs/ops-manager/current/admin/general/global-access-list-page/](https://deploy-preview-374--10gen-docs-ops-manager.netlify.app/admin/general/global-access-list-page/) — Unnested 2 notes in table 6. [docs/ops-manager/current/core/backup-overview/](https://deploy-preview-374--10gen-docs-ops-manager.netlify.app/core/backup-overview/) — Unnested 2 ``warning`` admonitions in tables. 7. [docs/ops-manager/current/core/requirements/](https://deploy-preview-374--10gen-docs-ops-manager.netlify.app/core/requirements/) — No changes, left 1 ``important`` admonition 8. [docs/ops-manager/current/core/system-alerts/](https://deploy-preview-374--10gen-docs-ops-manager.netlify.app/core/system-alerts/) — Couldn't find the reported 1 nested admonition in table. But did notice incorrect include in table, where the correct include contains a note. Will address in [DOCSP-43763](https://jira.mongodb.org/browse/DOCSP-43763). - [ ] [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. - [x] Proofread for spelling and grammatical errors. - [x] Check staging for rendering issues. - [x] Confirm links are working.
diff --git a/source/admin/backup/daemons-page.txt b/source/admin/backup/daemons-page.txt
@@ -60,6 +60,9 @@ configure daemons:
    * - Delete Daemon
      - Click this link to delete the Backup Daemon.
 
+       You must restart the daemon to reconfigure the daemon after
+       deletion.
+
    * - Assignment
      - Select this to allow the daemon to process more jobs. If the
        daemon's disk fills, clear this so the host is not overloaded.
@@ -71,11 +74,9 @@ configure daemons:
    * - Queryable Restore Jobs
      - Select this to allow the daemon to process :opsmgr:`queryable backups </reference/glossary/#std-term-queryable-backup>`.
 
-       .. note::
-
-          For the fastest possible restore time, configure a dedicated queryable restore
-          daemon by selecting :guilabel:`Queryable Restore Jobs` and clearing the checkboxes
-          for the other daemon roles, for example, :guilabel:`Garbage Collection` and :guilabel:`Resource Usage`.
+       For the fastest possible restore time, configure a dedicated queryable restore
+       daemon by selecting :guilabel:`Queryable Restore Jobs` and clearing the checkboxes
+       for the other daemon roles, for example, :guilabel:`Garbage Collection` and :guilabel:`Resource Usage`.
 
    * - Resource Usage
      - Select this to collect data for this daemon. This includes the
diff --git a/source/admin/backup/groom-priority-page.txt b/source/admin/backup/groom-priority-page.txt
@@ -38,10 +38,7 @@ their blockstores. |onprem| maintains a blockstore using three jobs:
      - Runs when the percentage of living block bytes drops
        to drops below a given threshold.
 
-       .. seealso::
-
-          To learn more about grooming, see
-          :ref:`Groom page <grooms-page>`
+       To learn more, see :ref:`Grooms <grooms-page>`.
 
    * - Integrity Check
      - Verify that the blockstore has no data integrity issues.
diff --git a/source/admin/backup/job-timeline-page.txt b/source/admin/backup/job-timeline-page.txt
@@ -18,7 +18,9 @@ page. The :guilabel:`Job Timeline` page displays critical timestamps
 (:opsmgr:`head </reference/glossary/#std-term-head-database>`, last snapshot, next snapshot) and
 offers a way to assign a :opsmgr:`daemon </reference/glossary/#std-term-Backup-Daemon>` to a given job.
 
-.. include:: /includes/head-database-backup-deprecated.rst
+.. note:: 
+
+   .. include:: /includes/head-database-backup-deprecated.rst
 
 Click the :guilabel:`Auto refresh` checkbox to update the list
 automatically every 10 seconds. Click the :guilabel:`Refresh` button
diff --git a/source/admin/backup/jobs-page.txt b/source/admin/backup/jobs-page.txt
@@ -83,10 +83,8 @@ From the :guilabel:`Jobs` page, you can do the following:
      - Select or clear :guilabel:`Journal Head` to turn on or off
        journaling for your head database.
 
-       .. note::
-
-          Changing this setting at the job level overrides the
-          deployment-wide setting.
+       Changing this setting at the job level overrides the
+       deployment-wide setting.
 
        See :setting:`mms.backup.journal.heads` for how to enable or
        disable journaling for all head databases in your project.
@@ -145,27 +143,24 @@ procedural information, see
           field.
 
        4. Click :guilabel:`Save Changes`.
-
-       .. warning::
-
-          After you change the labels applied to this backup job,
-          :ref:`stop and then restart backups <restart-backup>` for this
-          deployment. Once Backup restarts, |onprem| changes the
-          :opsmgr:`oplog store  </reference/glossary/#std-term-Oplog-Store-Database>` assigned to this
-          Backup job. The oplog store matches the job's assigned
-          labels to an oplog store with the same
-          :ref:`assigned labels <edit-oplogstore>`. This change halts
-          new and removes existing
-          :opsmgr:`point-in-time restores </reference/glossary/#std-term-point-in-time-restore>` until
-          |onprem| takes the next snapshot after reassigning the oplog
-          store.
-
-       .. note::
         
-          Some label changes do not require stopping and restarting backups.
-          Changes that only affect Oplogs only require stoping and restarting running jobs.
-          Changes that only affect Daemons only need a :doc:`move head </tutorial/move-jobs-to-new-backup-daemon>` to move the existing data.
-          Changes that only affect blockstores only need an :ref:`inter groom job <inter-blockstore-groom-job>`.
+       Some label changes do not require stopping and restarting backups: 
+       
+       - Changes that only affect Oplogs only require stopping and restarting running jobs.
+       - Changes that only affect Daemons only need a :doc:`move head </tutorial/move-jobs-to-new-backup-daemon>` to move the existing data.
+       - Changes that only affect blockstores only need an :ref:`inter groom job <inter-blockstore-groom-job>`.
+
+       :red:`WARNING:` After you change the labels applied to this backup job,
+       :ref:`stop and then restart backups <restart-backup>` for this
+       deployment. Once Backup restarts, |onprem| changes the
+       :opsmgr:`oplog store  </reference/glossary/#std-term-Oplog-Store-Database>` assigned to this
+       Backup job. The oplog store matches the job's assigned
+       labels to an oplog store with the same
+       :ref:`assigned labels <edit-oplogstore>`. This change halts
+       new and removes existing
+       :opsmgr:`point-in-time restores </reference/glossary/#std-term-point-in-time-restore>` until
+       |onprem| takes the next snapshot after reassigning the oplog
+       store.
 
    * - :ref:`Configure a project to use KMIP <configure-group-kmip>`.
      - Specify the |kmip| fields and click :guilabel:`Save Changes`.
diff --git a/source/admin/general/global-access-list-page.txt b/source/admin/general/global-access-list-page.txt
@@ -42,11 +42,9 @@ Add an Access List Entry
         - Type the |ipv4| address, |ipv6| address, or |cidr| block that
           you want to allow to use the |onprem| |api|.
 
-          .. note::
-
-             You can click :guilabel:`Use Current IP Address` to add
-             the public IP address of the host you are using to access
-             |onprem|.
+          You can click :guilabel:`Use Current IP Address` to add
+          the public IP address of the host you are using to access
+          |onprem|.
 
       * - Description
         - Type the purpose this IP address serves.
@@ -80,12 +78,10 @@ Edit an Access List Entry
       * - Access List Entry
         - Type the  |ipv4| address, |ipv6| address, or |cidr| block
           that you want to allow to use the |onprem| |api|.
-
-          .. note::
             
-             You can click :guilabel:`Use Current IP Address` to add
-             the public IP address of the host you are using to access
-             |onprem|.
+          You can click :guilabel:`Use Current IP Address` to add
+          the public IP address of the host you are using to access
+          |onprem|.
 
       * - Description
         - Type the purpose this IP address serves.
diff --git a/source/includes/backup/legacy-process-change-op-state.rst b/source/includes/backup/legacy-process-change-op-state.rst
@@ -32,9 +32,7 @@
 
      - Click :guilabel:`Terminate`.
 
-       .. warning::
-        
-          :guilabel:`Terminate` deletes all retained backups.
+       :red:`WARNING:` :guilabel:`Terminate` deletes all retained backups.
 
 .. important::
 
diff --git a/source/includes/backup/wtchk-process-change-op-state.rst b/source/includes/backup/wtchk-process-change-op-state.rst
@@ -32,7 +32,5 @@
 
      - Click :guilabel:`Terminate`.
 
-       .. warning::
-        
-          :guilabel:`Terminate` deletes all retained backups.
+       :red:`WARNING:` :guilabel:`Terminate` deletes all retained backups.
 
diff --git a/source/includes/extracts-queryable-backups.yaml b/source/includes/extracts-queryable-backups.yaml
@@ -26,18 +26,16 @@ content: |
   To query a snapshot of a :manual:`replica set </reference/glossary/#std-term-replica-set>`, the Backup Daemon
   requires at least one worker for the replica set.
 
-  .. example::
+  For example, if you restore a queryable backup from a 3-shard cluster with 1 shard router 
+  (:manual:`mongos </reference/program/mongos/#mongodb-binary-bin.mongos>`), you need 
+  this value to be at least ``5``:
 
-     If you restore a queryable backup from a 3-shard cluster with
-     1 shard router (:manual:`mongos </reference/program/mongos/#mongodb-binary-bin.mongos>`), you would need this value to
-     be at least ``5``:
+  - 1 per shard (``3``) +
+  - 1 for the config server (``1``) +
+  - 1 for the :binary:`~bin.mongos`
 
-     - 1 per shard (``3``) +
-     - 1 for the config server (``1``) +
-     - 1 for the :binary:`~bin.mongos`
-
-     When the queryable backup begins, the Backup Daemon spins
-     up 5 or more workers to manage these components.
+  When the queryable backup begins, the Backup Daemon spins
+  up 5 or more workers to manage these components.
 
 ---
 ref: queryable-backup-pem-restriction
diff --git a/source/includes/head-database-backup-deprecated.rst b/source/includes/head-database-backup-deprecated.rst
@@ -1,6 +1,4 @@
-.. note::
-
-   FCV |fcv-link| ``4.2`` and later use 
-   :manual:`backup cursors </reference/glossary/#std-term-backup-cursor>` instead of
-   :opsmgr:`head databases </reference/glossary/#std-term-head-database>`. For
-   more information, see :ref:`backup-daemon`.
+|fcv-link| ``4.2`` and later use 
+:manual:`backup cursors </reference/glossary/#std-term-backup-cursor>` instead of
+:opsmgr:`head databases </reference/glossary/#std-term-head-database>`. For
+more information, see :ref:`backup-daemon`.
