aawsome
aawsome
> Most of the time the backup-chain is linear, I assume, so is there an disadvantage of just using the latest snapshot as parent? Mhh - in fact we could...
@RubenKelevra Thanks for your feedback! > Restic should be able to determine how long certain blocks will _need_ to be kept when `forget` is run. This would require two thresholds:...
@RubenKelevra sorry for the late reply > On the other hand the cold storage should be able to have pretty recent data as well, as second storage if the redundancies...
> Has any progress been made on the several issues concerning restic supporting cold-storage? We at CERN are also looking into this and are very interested in linking restic with...
Actually, re-reading it you might be right that all bits and not only the nine ones are the public API. Then, maybe the best way would be to add this...
I'm still struggling with this very restic/golang-specific way of saving file modes. There is the (POSIX?) standard described in the man page inode(7) which seems to be used in C/C++/Python/Rust....
> In lieu of that, I used restic mount [(described here)](https://restic.readthedocs.io/en/stable/050_restore.html?highlight=mount#restore-using-mount) and rclone sync [(described here)](https://rclone.org/commands/rclone_sync/) and it seems to work quite well - only downloading files that are different,...
@pabs3: You can also try the lowmem approach of #2523 for backing up your maildir. I guess some part of your memory usage is due to the index. I would...
About having really large directories, I think the problem is the following: A node (see `internal/restic/node.go`) can just have one subtree. Therefore if a node is a directory, all files...
I started with the implementation in the branch [optimize-large-dir](https://github.com/aawsome/restic/tree/optimize-large-dir) It's still WIP and so far only the initial backup and some commands like `mount` and `check` work. I'm not yet...