Details
-
Task
-
Resolution: Won't Do
-
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
Issue Links
- depends on
-
SERVER-62627 Implement the first phase of the restore algorithm where the storage engine prepares the backup
-
- Closed
-
-
SERVER-62630 Implement the first phase of the restore algorithm where the backup is imported into the server
-
- Closed
-
- is depended on by
-
SERVER-62631 Implement the abort logic during a failure where the backup is imported into the server in the first phase
-
- Closed
-
-
SERVER-62634 Implement the final steps of the first phase restore algorithm
-
- Closed
-