kimono-koans
commented
4 days ago But I can't seem to get httm to look at /btrbk on the other drive. /snapshots and /btrbk look the same... a long list of snapshots.
In general, re: ZFS, we have tried to do this via the -a, --alt-replicated flag, which will auto-discover snapshots of the type rpool/ROOT/ubuntu_w0ha6q when "backup-ed" to a local data pool, like so data/rpool/ROOT/ubuntu_w0ha6q or data/something/anotherthing/rpool/ROOT/ubuntu_w0ha6q.
Re: btrfs, auto-discovery of such pools may not be possible because of how you sent (or copied, which, if you see my next comment, is a no-no!) the datasets. If it were me, I'd first try to be as close as possible to the ZFS topology and see if you can't use -a, because it won't require any extra legwork on your part like --map-aliases.
WARN: Mount "/btrbk" appears to have no snapshots available.
Here, it seems httm is not detecting any snapshot subvolumes at /btrbk which means -- perhaps you're not doing a btrfs send to your data pool, but instead just copying new datasets? Note, httm will not discover snapshots which aren't snapshot subvolumes. My guess is that this is your problem.
See below, httm discovers the /btrbk dataset but does not see any snapshots because snapshots are just raw directories, not btrfs subvolumes (which you can see via btrfs subvolume list -s /path/to/btrfs/volume):
map_of_snaps: MapOfSnaps {
inner: {
"/backup": [],
"/btrbk": [],
"/data": [
"/snapshots/@data.20240307T0907",
"/snapshots/data.20240804T0000",
"/snapshots/data.20241002T2351",
"/snapshots/data.20241003T2215",
"/snapshots/data.20241004T0015",
"/snapshots/data.20241005T0015",
"/snapshots/data.20241005T1215",
"/snapshots/data.20241005T1245",
"/snapshots/data.20241005T1315",
"/snapshots/data.20241005T1345",
],
"/extra": [],
"/more": [],
"/snapshots": [],
},
},
bshor
I'm using httm 0.43.2 on a Debian 12 system, with a BTRFS file system and btrbk for creating snapshots. It works perfectly for showing the older versions living in my snapshots directory, which is located at
@snapshotsand mounted on /snapshots. My data is located at@dataand mounted on /data. On a separate drive, I have@btrbkmounted on /btrbk. This is where I send "backup" snapshots.For my local drive, these are both top-level subvolumes:
For my backup drive it is as well:
ID 257 gen 16551 top level 5 path @btrbkHere's an example of it working as expected using snapshots in /snapshots.
But I can't seem to get httm to look at /btrbk on the other drive.
I tried map-aliases but no luck:
/snapshots and /btrbk look the same... a long list of snapshots.
I'm guessing that httm is trying to look in obvious places for snapshots, and doesn't think to look in some other place for them. Which is fine -- but is there a way to tell it to look there?
Here's the debug output. Interesting that it appears to believe /btrbk is a live subvolume that might have its own snapshots.