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

Ops Manager steps for manual backup restore are incorrect

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Ops Manager

    Description

      Hello! I recently worked on HELP-47199 regarding a non-point-in-time manual snapshot restore that followed the Ops Manager documentation listed here. Ultimately, we came to the conclusion that the documentation for a manual restore has diverged from what we actually do in the automation agent.

      Specifically, in the "FCV 4.2 or later" section under "Manual Restore", here are the following discrepancies:

      • Step 14: Add a New Replica Set Configuration
        • Here, we tell the user to insert a new replica set config with just one member (or it's implied), with the host being defined with the `ephemeralPortNewReplicaSet`. We should instead be inserting a replica set config with all replica set members in the config, with all their hosts defined with the final port the user will use for their replica set.
      • Step 18: Restart the Instance to Recover the Oplog
        • It's noted that we should start the node up as a replica set. Instead, what we should be doing is starting the node up as a standalone again, but with the additional oplog reply parameters set. These include:
          •  --setParameter recoverFromOplogAsStandalone=true
             --setParameter takeUnstableCheckpointOnShutdown=true
             --setParameter startupRecoveryForRestore=true
            

        • This will still recover the oplog.
      • Steps 23, 24, 28: We can get rid of these steps for the following reasons:
        • Step 23 and 24:
          • We don't need to remove the existing replica set config, since the one we inserted in step 14 now is the correct final one, with all members and the correct ports. As a result, we can skip both the stopping and insertion steps.
        • Step 28
          • As mentioned above, since we already have all replica set members in the new config, we don't need to set up the replica set configuration.

      I'm happy to review these changes, and I would also get a second look from someone on the Cloud Backup team to confirm.

      Attachments

        Activity

          People

            lander.kerbey@mongodb.com Lander Kerbey
            ali.mir@mongodb.com Ali Mir
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              1 week, 1 day ago