Hi Folks It’s the owner of a stupidly big archive here and I want to make sure I’m testing integrity regularly and correctly. I plan on scripting this and will share with everyone once I have completed it. I’m a sucker for automation including emailing results, and I like to use the sendEmail tool,…

from restic check -h: --read-data-subset subset read a subset of data packs, specified as 'n/t' for specific part, or either 'x%' or 'x.y%' or a size in bytes with suffixes k/K, m/M, g/G, t/T for a random subset

restic check --read-data-subset x%

Where x = the percentage, but is it RANDOM? My thought is that I’d put 1% and it would just test the first 1% of the data every time.

Like @alexweiss said use the x of y approach. Depending on when your machine is used the least you can probably even check bigger parts. What I do with a storage server that has little to do on weekends: every Sunday I have it check weeknumber of 52 parts (e.g. 8/52, then 9/52 and so on). It’s not …

[image] g33kphr33k: I plan on scripting this and will share with everyone once I have completed it. Hello, on Linux or Windows?

If you choose to be a little more paranoid then have your backup script pick one changed file and restore it. Then compare the “restored” file to the actual file. I did this with a non-restic backup for small MS Sql Server database by doing a backup in prod and restore into development on a daily ba…

[image] nicnab: every Sunday I have it check weeknumber of 52 parts (e.g. 8/52, then 9/52 and so on) I don’t get this. To my understanding you would check 1/52 = 1.92% of whole repository the first Sunday in the year and then 2/52 = 3.85% (would need double the time) and then the third Sunday…

Check this explanation out. It’s not a division. “3/52” means “the third of 52 equal parts”.

Ahh, that’s interesting. Thanks.

restic forum

Data integrity testing

Getting Help

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled