Personal backup copy coverage calculator

Calculate missing file/destination copies and stale or nonmatching copies with your own figures.

Your numbers

Use the units shown. Results update as you change valid inputs.

Use missing file/destination copies and stale or nonmatching copies to compare changes to your inputs. The method and limits below explain the scope.

Examples

Examples

Try the starting example

JSON Files [ID,size bytes,last modification day index]
[["A",1000,10],["B",2000,20]]
JSON Copies [file ID,destination ID,last matching-checksum day index,matches flag 0/1]
[["A","D1",12,1],["A","D2",5,1],["B","D1",22,1]]
JSON Required destination IDs
["D1","D2"]
Missing file/destination copies
[["B","D2"]]
Stale or nonmatching copies
[["A","D2"]]
Valid copy coverage fraction
0.5
Valid byte-copy coverage fraction
0.5

Try another scenario

JSON Files [ID,size bytes,last modification day index]
[["A",1000,10],["B",2000,20]]
JSON Copies [file ID,destination ID,last matching-checksum day index,matches flag 0/1]
[["A","D1",12,1],["A","D2",15,1],["B","D1",22,1],["B","D2",25,1]]
JSON Required destination IDs
["D1","D2"]
Missing file/destination copies
[]
Stale or nonmatching copies
[]
Valid copy coverage fraction
1
Valid byte-copy coverage fraction
1
Calculation method

Calculation method

Missing file/destination copies

All required file×destination pairs absent from manifest.

Stale or nonmatching copies

Present copies whose matching checksum predates source modification or whose matches flag is zero.

Valid copy coverage fraction

Fresh matching copy count / required file×destination pair count.

Valid byte-copy coverage fraction

Sum source bytes for valid copies / (sum source bytes×destination count).

Symbols and units
a
JSON Files [ID,size bytes,last modification day index]
b
JSON Copies [file ID,destination ID,last matching-checksum day index,matches flag 0/1]
c
JSON Required destination IDs

Use the units shown. A list keeps the order in which you enter its values. The symbol ^ means “raised to the power of”.

Assumptions & limits

Assumptions & limits

  • Read-only checksum-manifest/timestamp reconciliation. Matching flags are supplied evidence, not computed cryptographic checks. Uses one checksum result per file/destination. Supported limits: 1–1000 files, 1–20 destinations, 1–20000 manifest copies; finite nonnegative byte sizes and day indices.
Are these inputs private?

These calculations run in your browser. A shared link contains the values you choose to share. Only questions submitted to the separate AI finder are sent to OpenAI.

Share this page
Share this calculator

Leave unchecked to share the page without your entered values.