for Go, I actually wrote one myself: https://github.com/muesli/gitcha
I know that restic and borg have that kinda feature
Not really needed for me, just curiouys
but certainly something that might be useful
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
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.
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.
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?
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 :)
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
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?
Or maybe a snapshot count column too
Any idea what causes this:
I can list all teh volumes just fine, the ID's are correct and the path to backup and and files seem to be correct aswell.
For example, I tried running the following command:
This fails with the error: open /mnt/sdb2/KnoxiteBackups/chunks/index: no such file or directory. And yes, indeed the index file does not exist, but I can list volumes just fine, and the creation of them worked fine too.
knoxite -r KnoxiteBackups/ store bbe17fb8 /media/veracrypt2/ -d "Initial music library backup".This fails with the error: open /mnt/sdb2/KnoxiteBackups/chunks/index: no such file or directory. And yes, indeed the index file does not exist, but I can list volumes just fine, and the creation of them worked fine too.
What could be the cause for this error. The same command worked just fine when I tried the same procedure with small files in a test environment
2 replies
And the next question would be: Do wildcards work here aswell? Because Ideally I wouldnt want the folder veracrypt2 be part of the backup, the "root" of the backup should eb the contents that are inside the "veracrypt2 folder".
Is it possible to specify a path like so:
Is it possible to specify a path like so:
/mnt/veracrypt2/* ?
1 reply
@mueslix:matrix.org No problem. Were you able to reproduce the bug on your end? I am talking about #225
@mueslix:matrix.org I ran into another issue with knoxite. For some reason I can not access my snapshots anymore I created yesterday ... While with
knoxite -r /mnt/sdb2/KnoxiteBackups volume list I can list the snapshots just fine - when doing knoxite -r /mnt/sdb2/KnoxiteBackups snapshot list <volumeid>, I am prompted with an exception: "unable to load snapshot from any storage backend". I am aware somebody already created a bug report for that: #48 but the suggested solution there does not work at all. I can't list the snapshots regardless in what folder I am. Not a great look :/
Do you have any idea what is the cause for this problem? Currently I am locked out of my backups ...
😄
So, I created my repo initially on an external hdd that was mounted to my system.
Let's it was mounted as /mnt/a/.
I then created my repository, created volumes, snapshots etc - all good.
Now the next day, I wanted to access my snapshots again. However, everytime I tried to access my snapshots (list them) I got an error: unable to load snapshot from any storage backend.
I figured out, that this has to do with how the repository is mounted when it was crated.
Because on that day, my drive with the repository was mounted as /mnt/b/. And then there was a mismatch between the path that is saved in the knoxite configuration and the one that is specified.
Even tho I specified the correct path when I wanted to list the snapshots (/mnt/b/), it failed. Most likely because internally it still uses the path from the knoxite configuration that was set upon repository creation (/mnt).
When I umounted my harddrive and remounted it as /mnt/a/, everything worked fine.
So, to recreate this problem, try this:
- Connect external hdd and mount it to your system with mountpoint:
/mnt/a/. - Create a folder on that drive, something like
backupsor so. Initialize a new repo in there. - Create a volume and backup some data to it.
- See if you can list the snapshots with
knoxite -r /mnt/a/backups snapshot list <volume_id>. Should work fine. - Unmount the drive.
- Remount the drive under a different path, for example
/mnt/b/. - See if you can list the snapshots with
knoxite -r /mnt/b/backups snapshot list <volume_id>. It will fail with the error "unable to load snapshot from any storage backend". - Weirdly enough, it is possible to list volumes, but not snapshots.
@mueslix:matrix.org