Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13847

[OM] Fix Errors in 4.2 Manual Restore Instructions

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Ops Manager
    • Labels:
    • Last comment by Customer:
      true
    • Story Points:
      5
    • Sprint:
      CET: Mab (3-9 Nov 2020), CET: Oberon (17-23 Nov 2020), CET: Turkey (24-30 Nov 2020), CET: T (29 Dec 20 - 4 Jan 21), CET: Umbra (5 - 11 Jan 21)

      Description

      Description

      https://docs.opsmanager.mongodb.com/v4.2/tutorial/restore-replica-set/

      There are errors with the instructions in the manual restore instructions for a Replica Set as per link above:

      FCV of 4.2 or later > Manual Restore

      1. Step 7 - should state what do with existing files - delete them ? 
      2. Step 10 - doesn't state what user to use and what permissions are required
      3. Step 13 - Errors with restoreTS.getTime() not recognised. This there is a missing declaration of restoreTS
      4. Step 13 - My  restoreInfo.txt did not contain a "Restore timestamp"
      5. Step 14 - Refers to a port number in Step 10 that doesn't exist
      6. Step 17 refers to connecting to a mongo shell but we were instructed to shut this down in Step 15. Step 16 was skipped because it states to do so if not a PiT restore so maybe a mistake here ?

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

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

        Attachments

          Activity

            People

            Assignee:
            julia.malkin Julia Malkin
            Reporter:
            greg.cox Greg Cox
            Participants:
            Last commenter:
            Julia Malkin Julia Malkin
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Days since reply:
              34 weeks, 3 days ago
              Date of 1st Reply: