![]() Am I correct that there is no way to alter my local block size after a backup is already created, right? (In any case, that would probably just blow up my sql lines further.).I think the main goal here would be to alleviate some of the local load (mostly sqllite IO) to make operations run more smoothly.: I have read several articles on block and dblock sizes and from these, i am surmising that the problem was around my block sizes being too small, ie too many lines in the sqllite db. My observations over the last 10 days were that duplicati was mostly pegging the io of my old fileserver hammering on sqllite file for about 80-90% of the time, then it would spin CPU for a while and go back to pegging IO (a pair of mirrored spinning platters). I am on a pretty stable line of about 20MB (power outage above is probably the second in 5 years), using wasabi and b2 as offsite providers. New data streams in on a fairly constant basis as new email and pics come in and periodically docs/etc are updated but for the most part I am not worried any significant ‘file edit’ churn. This is mostly coldish storage, family digital junk accumulated over several years. I have a roughly 750GB archive with about 250k files. I am considering starting over w/ more manageable chunking. ![]() ![]() I watched the machine spin for about 10 days before a brief power outage killed it. I tried to repair to no avail and eventually did a delete/recreate. ![]() I recently got the dreaded ‘we expected X files but found Y files’ error. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |