[SERVER-49162] Expand Sharded Backup Restore tests to cover incremental backups Created: 29/Jun/20  Updated: 06/Dec/22  Resolved: 02/Jul/20

Status: Closed
Project: Core Server
Component/s: Replication, Sharding, Storage
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Backlog - Storage Execution Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-47936 Expand test coverage for streaming in... Closed
Related
Assigned Teams:
Storage Execution
Participants:

 Description   

We want to cover all supported backup-restore procedures, and incremental is missing.



 Comments   
Comment by Daniel Gottlieb (Inactive) [ 02/Jul/20 ]

Closing as a dup of SERVER-47936. Some notes for posterity: while it's easy to write a test that would have caught HELP-16711, it's not easy to write a test at the MongoDB layer that also avoids false positives. Even when data doesn't logically change, WT can shuffle blocks around while the server is up, for example as the oldest/stable timestamp move. These blocks do need to be copied as part of an incremental backup. It's not sufficient to assume that stopping writes to the server implies no blocks need to be copied.

Comment by Judah Schvimer [ 29/Jun/20 ]

When creating these tests we focused on covering all aspects of the restore spec, but were less complete in the backup side of the spec, and should make sure all covered backup procedures are complete.

Generated at Thu Feb 08 05:19:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.