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

Implement the first phase of the restore algorithm where the oplog is replayed on restored collections

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Storage Execution

    Description

      These are the next steps after SERVER-62630.

      If a timestamp was specified for a point-in-time restore, the oplog entries in local.oplog.restore will be replayed on the restored collections using the applyOps command.

      • Oplog entries for collections not restored will be skipped.
      • Oplog entries referencing a database namespace that was renamed will have to be re-written with the new database namespace before being applied.
      • An applyOps oplog entry can contain multiple oplog entries referencing multiple collections. This is how committed multi-document transactions are structured. These applyOps oplog entries will have to be re-written to remove the oplog entries referencing collections not restored before being applied.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: