[SERVER-46444] The 'length' in the backup block for incremental backups should always be equal to the block size specified during the first full incremental backup Created: 27/Feb/20  Updated: 27/Feb/20  Resolved: 27/Feb/20

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

Type: Improvement Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Gregory Wlodarek
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Sprint: Execution Team 2020-03-09
Participants:

 Description   

There are two cases where the 'length' in the backup block may be larger than the block size today. Specifically, the length is equal to the file size in these two cases.

  1. On the first full incremental backup, the length will be equal to the file size for all files regardless of the specified block size.
  2. On subsequent incremental backups when a new file needs to be copied, then the length will be equal to the file size for that file, regardless of the specified block size.

Users are responsible for not reading past the file size as the last (offset, length) backup block pair may go past the file size.



 Comments   
Comment by Gregory Wlodarek [ 27/Feb/20 ]

The size returned in the incremental cursor is not guaranteed to be in multiples of the granularity for WT. So we'd have to handle more cases than the ones listed. Cloud agreed to handle the size not being in multiples of the granularity.

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