[SERVER-49146] Enable s3 archiving of data files for backup tests in src/mongo/db/modules/enterprise/jstests/hot_backups Created: 26/Jun/20  Updated: 29/Oct/23  Resolved: 01/Jul/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.4.0-rc14, 4.7.0

Type: Task Priority: Major - P3
Reporter: Lamont Nelson Assignee: Lamont Nelson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
is related to SERVER-48909 Fix a bug where a sharded backup/rest... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4, v4.2
Sprint: Sharding 2020-07-13
Participants:
Linked BF Score: 0

 Description   

This will make it easier to determine where a failure occurs if there is data loss.



 Comments   
Comment by Githook User [ 09/Jul/20 ]

Author:

{'name': 'LaMont Nelson', 'email': 'lamont.nelson@mongodb.com', 'username': 'lamontnelson'}

Message: SERVER-49146: turn on archiving for the tests under the hot_backups directory

(cherry picked from commit 86c9894198962995a11d3f8d36a8f3e3fba559cc)
Branch: v4.4
https://github.com/mongodb/mongo/commit/1be7ba53b01be6d44e133e3e0f0ecc242628eb19

Comment by Githook User [ 01/Jul/20 ]

Author:

{'name': 'LaMont Nelson', 'email': 'lamont.nelson@mongodb.com', 'username': 'lamontnelson'}

Message: SERVER-49146: turn on archiving for the tests under the hot_backups directory
Branch: master
https://github.com/mongodb/mongo/commit/86c9894198962995a11d3f8d36a8f3e3fba559cc

Comment by Max Hirschhorn [ 30/Jun/20 ]

Will this include both the backup and restore paths?

It should be whatever is in the /data/db/job# directory when the test fails. That should include whatever extra data written by the tests (as they are in some subdirectory of that).

Comment by Judah Schvimer [ 30/Jun/20 ]

Will this include both the backup and restore paths?

Comment by Lamont Nelson [ 26/Jun/20 ]

https://mongodbcr.appspot.com/616770001/

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