Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.4.0-rc9, 4.7.0
Affects Version/s: 4.2.0-rc2
Component/s: Replication, Storage
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Requested:

v4.4, v4.2
Sprint:
Repl 2019-11-04, Repl 2019-12-02, Repl 2019-12-16, Repl 2019-12-30, Repl 2020-01-13, Repl 2020-01-27, Repl 2020-02-10, Repl 2020-02-24, Repl 2020-03-09, Repl 2020-03-23
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

We have tests that exercise the procedure for automated backup restore using WT snapshots in 4.2. This should be the same procedure used by external backup restore services, so we should verify that our tests match the written specification that documents the approved backup procedure.

is duplicated by

SERVER-44307 Add server test to ensure running a replica set node on a port not specified by the rsconfig document does not fire a no-op on step up.

Closed

related to

SERVER-42326 Test restoring a 4.0 backup into a 4.2 binary in fCV 4.0

Closed

SERVER-46719 Simplify sharded backup-restore spec

Closed

Assignee:: Judah Schvimer
Reporter:: Will Schultz
Participants:: Githook User, Judah Schvimer, Louisa Berger, Will Schultz
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Jul 12 2019 03:23:26 PM UTC
Updated:: Oct 29 2023 10:19:06 PM UTC
Resolved:: Mar 09 2020 04:08:46 PM UTC
Confidence Status Last Update:: 28/Jan/20 7:32 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates