Skip to main content

Backups

Plakar: an avalanche of changes

·2625 words·13 mins
TL;DR: Significant refactoring to improve its performance, implemented read and write semaphores to throttle chunkers and reduce memory usage, introduced a repository index and packfiles to decrease the number of I/O operations, also intrioduced a new HTTP storage backend. A ton of refactors # I’ve done so much work on plakar in the past few weeks that I don’t even know what to begin with…

Plakar: a TON of changes

·3855 words·19 mins
TL;DR: TL;DR: a lot of work in plakar, but also on CDC and index optimization. Optimized go-fastcdc # I ran into a benchmark which included my implementation of the FastCDC algorithm, and it made me realise that it was not on par with alternative implementations:

Plakar: snapshot forking and tagging

·2064 words·10 mins
TL;DR: plakar gained two minor features, snapshots fork-ing and snapshots tagging, which makes it possible to unlock several major new features in a relatively short future. Plakar is not only for backups # If you have followed my work on this project, you may have assumed that plakar was intended solely for backups: it’s not entirely the case.

April 2022: plakar keys and UI stuff

·1516 words·8 mins
TL;DR: I did key and UI stuff, mostly search related. There’s going to be plenty of images in this post. Reworked plakar keys # I won’t expand much on that as I’m not done yet, but I spent a couple days reworking the way plakar handles keys for encrypted repositories.

March 2022: plakar clone and plakar sync

·820 words·4 mins
TL;DR: implemented cloning and synchronization between plakar repositories Slacked a bit # Shortly after I published my yearly retrospective, I was hit with two highly annoying personal issues that kept me very busy these last two months. I finally got everything back under control, my mind is mostly free again and I resumed playing with plakar.