Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-47552

Unable to do point in time recovery using oplogReplay -

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Diagnostics
    • Labels:
      None
    • ALL
    • Hide

      Step 1: mongorestore --port 27017 --nsInclude mydb1.mycoll ./ --drop

      Step 2:  mongorestore --port 27017 --oplogReplay --oplogLimit 1586934385 ./

      Show
      Step 1: mongorestore --port 27017 --nsInclude mydb1.mycoll ./ --drop Step 2:  mongorestore --port 27017 --oplogReplay --oplogLimit 1586934385 ./

      [root@************ local]# mongorestore --port 27017 --oplogReplay --oplogLimit 1586934385 ./
       2020-04-15T07:45:15.764+0000 preparing collections to restore from
       2020-04-15T07:45:15.764+0000 don't know what to do with file "oplog.rs.metadata.json", skipping...
       2020-04-15T07:45:15.764+0000 replaying oplog
       2020-04-15T07:45:18.067+0000 Failed: restore error: error applying oplog: applyOps: cannot apply insert or update operation on a non-existent namespace mydb.mycoll: { ts: Timestamp 1586931218000|1, h: 7203907580858761715, v: 2, op: "u", ns: "mydb.mycoll", o: { $set: { score: 10.0 }}, o2: { _id: ObjectId('5e96a22adf21792157ed2299') } }
      

       

       

      I dropped "mydb.mycoll" earlier which is not require to me. 

            Assignee:
            carl.champain@mongodb.com Carl Champain (Inactive)
            Reporter:
            dba.satvant@gmail.com Satvant Singh
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: