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

MMS Instructions for Restoring from Replica Set omit a argument from ./seedSecondary.sh

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: v1.3.13
    • Component/s: Cloud Manager
    • Labels:
      None
    • Last comment by Customer:
      true
    • Actual Time:
      4

      Description

      The MMS documentation page for Restore a Replica Set from a Backup, under the section Restoring Each Secondary, Step 6 uses the following command-line invocation for seedSecondary.sh

      ./seedSecondary.sh <oplog-size-in-gigabytes>

      However, I have just downloaded a fresh backup from MMS, and have attached the seedSecondary.sh script. The seedSecondary.sh script looks like this:

      #!/bin/sh
      if [ "$#" -ne 2 ]; then
          echo "Usage: $0 MONGODB_PORT OPLOG_SIZE_GB"
          exit 1
      fi
      mongo --port ${1} --eval "var res=db.getSiblingDB('local').runCommand({ create: 'oplog.rs', capped: true, size: (${2} * 1024 * 1024 * 1024)}); if(!res.ok){throw res.errmsg;} else{db.getSiblingDB('local').oplog.rs.insert({ts : Timestamp(1411766369, 1), h : NumberLong('1401333684165020466'), op : 'n', ns : '', note : 'seed from backup service'});}"

      As you can see, the signature of the script appears to be different to what the documentation state.

      The corresponding page for MMS 1.5, as well as for MMS 1.6 also appear to have this same error.

        Attachments

          Activity

            People

            Assignee:
            bgrabar Bob Grabar
            Reporter:
            victor.hooi Victor Hooi
            Participants:
            Last commenter:
            Jonathan Dahl Jonathan Dahl
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

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