Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
mueslix
@mueslix:matrix.org
[m]
Yep, that's how I use it. Also if you backup a farm of servers, you could have a volume per machine
(and still benefit from data deduplication across multiple machines)
Domink Heinz
@dominikheinz
Perfect, yea that sounds good !
How would I remove a snapshot with knoxite? The documentation only mentions removal of volumes
(Because I can see removing a snapshot not being trivial because of all the deduplication functionality)
mueslix
@mueslix:matrix.org
[m]
There is knoxite snapshot remove [id]. If that's missing from the docs, that's an oversight :)
Domink Heinz
@dominikheinz
Gotcha !
mueslix
@mueslix:matrix.org
[m]
This will indeed only delete the metadata. If you want to also remove chunks that are now not associated with any snapshot anymore (data deduplication), you would have to use knoxite repo pack manually.
Domink Heinz
@dominikheinz
How would I specify more complex rules what to include and exclude in a backup. Say all files in dir1, except for *.txt files for example etc etc. (I am kinda thinking of a similar ruleset that one can specify with a .gitignore file for example.

This will indeed only delete the metadata. If you want to also remove chunks that are now not associated with any snapshot anymore (data deduplication), you would have to use knoxite repo pack manually.

Perfect!

mueslix
@mueslix:matrix.org
[m]
A .gitignore like feature would be super neat indeed, but doesn't exist yet.
Domink Heinz
@dominikheinz
Gotcha.
mueslix
@mueslix:matrix.org
[m]
You can however filter the files beforehand, and then pass the file-set to knoxite
Domink Heinz
@dominikheinz
You mean manually filter the files beforehand?
mueslix
@mueslix:matrix.org
[m]
yeah
Domink Heinz
@dominikheinz
Yea, but that could be really tedious when there are many files :D But yep, thats a way to do it
mueslix
@mueslix:matrix.org
[m]
I wonder if there's a cli tool that parses .ignore files and returns the resulting list of filtered fiels/dirs
if not, there totally should be one :D
Domink Heinz
@dominikheinz
A quick google search told me there are gitignore parsers, yea
Not sure if there are any for go tho
mueslix
@mueslix:matrix.org
[m]
I meant a pure, universal CLI tool actually
for Go, I actually wrote one myself: https://github.com/muesli/gitcha
Domink Heinz
@dominikheinz
Ah nice. Yea, you could use that then if you ever decide to add some sort of .knoxiteignore file :P
mueslix
@mueslix:matrix.org
[m]
yep :)
Domink Heinz
@dominikheinz
Another thing that came to my mind: Does knoxite have some sort of retention functionality. E.g. keep 3 snapshots each week, 1 per month and 4 per year or something like that
I know that restic and borg have that kinda feature
Not really needed for me, just curiouys
mueslix
@mueslix:matrix.org
[m]
it doesn't, sorry
but certainly something that might be useful
Domink Heinz
@dominikheinz
Fair
Yea, but overall knoxite seems really good. Simple and straight to the point. The only feature I am missing is the diff between snapshots. But I can see myself using knoxite for my personal backups for sure
mueslix
@mueslix:matrix.org
[m]
That's lovely to hear :)
Keep in mind: there's a reason we didn't have a public release yet. This all started out as an experiment to do some things other storage/backup software hasn't tackled by design.
Domink Heinz
@dominikheinz
Yea makes sense. I hope there will be a public release at some point, as the project already seems pretty mature
mueslix
@mueslix:matrix.org
[m]
So clearly software like restic or borg is currently better maintained and more well tested. That's a bit of a vicious cycle for backup software, I guess. Releasing it is kind of promising this to work well, which is nothing I wanted to do just yet. But without a release, you don't get users, and there's no way to build up this confidence :D
Just a friendly reminder of "use at your own risk", but I honestly don't know of a showstopper that should prevent you from using knoxite.
Domink Heinz
@dominikheinz
I am aware :)
Is there the chance that in the future there will be breaking changes - to the point that the new version will not be able to restore e.g. backups made with an older version?
mueslix
@mueslix:matrix.org
[m]
There have been times during the development where newer versions updated the metadata schema: that means you can't use an older release to access a newer backup. But so far we've always been backwards-compatible with existing data iirc.
"older release" sounds funny, with there being no release. I meant "older binary", I guess :)
Domink Heinz
@dominikheinz
Yea, as long as one can use an old version to restore the data and then switch to a new version if that should ever happen, its fine I suppose
Is the version of knoxite somewhere encoded in the repo metadata, so i know what version was used to create the repos/snapshots etc
2 replies
If I have to use an older version at any point in time
mueslix
@mueslix:matrix.org
[m]
Domink Heinz
@dominikheinz
Gotcha!
Last question: I assume the repository.knoxite file is essentially. If that file ever gets corrupted/lost, access to all snapshots/data is irreversible lost?
mueslix
@mueslix:matrix.org
[m]
Absolutely correct!
Domink Heinz
@dominikheinz
Aight
Domink Heinz
@dominikheinz
Another suggestion, since I am in the process of setting up my knoxite repos right now. It would be cool if knoxite volume list also has a last-changed column - to see when the volume was last modified/had a snapshot added. Just a thought :)
Or maybe a snapshot count column too