I have not had any issues with Kopia so far, but I have also only used it for maybe a year? My main reason for trying it was that I wanted to be able to give something to family members to use as a backup client with a reasonable ui. I can also control the default exclude list and default policies for compression/etc pretty easily.
I don't know how many years of restic backups I have, but I still rely on it for my most important data. Anything really important on my desktop/laptop gets backed up via kopia, but also gets copied (usually via nextcloud) to a server that has hourly zfs snapshots and daily restic snapshots. Both the restic and kopia snapshots get stored on a local nas and then synced to rsync.net.
I was talking about dumping the database as an alternative to backing up the raw database files without stopping the database first. Taking a filesystem-level snapshot of the raw database without stopping the database first also isn't guaranteed to be consistent. Most databases are fairly resilient now though and can recover themselves even if the raw files aren't completely consistent.
Stopping the database first and then backing up the raw files should be fine.
If you're worried a out a database being corrupt, I'd recommend doing an actual backup dump of the database and not only backing up the raw disk files for it.
That should help provide some consistency. Of course it takes longer too if it's a big db
Sounds pretty cool, thanks for the details! Any chance of some pictures?
My worry would be the same, I don't know if I trust myself not to flood the house lol
I did think about using a mechanical float like in the back of a toilet, and an overflow drain in case it never stops filling
Kanboard is pretty great even if it does feel dated. I tried a lot of the newer alternatives and they all had either weird bugs or quirks I didn't appreciate.
Eh while it sucks, registrars and web hosts get so many abuse reports that sometimes they just err on the side of caution and don't investigate as thoroughly as you'd like.
Of course it also depends a lot on various things like what type of complaint, how much money you spend with them, account history, complaint source, etc.
They should be able to tell you what they had a problem with and give you a chance to fix it.
One problem is the lack of alternative transport options.
In most of the US, public transport just isn't a thing. And things are too far apart for cycling to be efficient for commutes, grocery shopping, etc.
Do you need to search inside of files for text, or just file names?
If inside of files, something simple like ripgrep/ag/grep like someone else mentioned would be an easy option.
If just file names, why not create an index of filenames and search that instead?
If you need an advanced search, maybe ElasticSearch would work for you? You'd have to upload each file to the elasticsearch server though.