Open kapitainsky opened 6 months ago
For the backup
command: All those information is saved in the snapshots. Try rustic snapshots --long
or rustic snapshots --json
to get the information.
About forget
and prune
: Which information do you miss in the logs?
For the
backup
command: All those information is saved in the snapshots. Tryrustic snapshots --long
orrustic snapshots --json
to get the information.
It is nice that it is included in snapshot but I think it is reasonable to expect any logging facility to include it as well? Snapshots also are deleted together with all information. Log file has an obvious purpose - to log:) what happened in the past.
About
forget
andprune
: Which information do you miss in the logs?
What snapshots were deleted, what snapshots were not, reason
What prune did, how much data was repacked, what is unused % after etc.
Pretty much everything what today can only be seen in console and is completely missing from log file.
Today this is what I have in log file when I run forget
:
14:04:33 [INFO] using config ./rustic.toml
14:04:34 [INFO] repository opendal:test-dal-lock: password is correct.
14:04:34 [INFO] using cache at /Users/kptsky/Library/Caches/rustic/79622816e3c9c922340f1fd7b7fd31f225f7a1d14faaeea5d6d52386980d16ce
How I can even tell what it was? As for prune
I would get:
14:06:21 [INFO] using config ./rustic.toml
14:06:22 [INFO] repository opendal:test-dal-lock: password is correct.
14:06:22 [INFO] using cache at /Users/kptsky/Library/Caches/rustic/79622816e3c9c922340f1fd7b7fd31f225f7a1d14faaeea5d6d52386980d16ce
One more obvious thing would be also to log full rustic
command executed + rustic
version
When I use log file to look what my rustic
backup was doing last month I should be able to see it. So I can investigate what went wrong (or not) and when. Simply by having track record of all actions and their results I can grep
for specific date and see all.
And real icing on the cake would be ability to use OS logging subsystem - so for example in Linux to redirect all log to syslog.
All above is of course only wish list but I think it is reasonable long term for rustic
to be proper backup solution. Logging similarly to documentation is something many cool software is missing. Here great thing is that we already have all info captured, some presented in console, some saved in snapshots so logging should be low hanging fruit to sort out.
Is it feasible to add an option to print the file name being processed during backup
?
Borg has:
U /path/to/unchanged/file
d /path/to/directory
A /path/to/new-file.txt
@AlphaJack You should be able to see that when using --log-level=debug
(or log-level = "debug"
) in the config profile.
Thank you, I missed that!
I love your program :heart:
When running backup, generated log (
log-file
) contains:When on the console I see:
It would be great if log file could also contain this information - it is already generated and only not saved in log:
Similarly for
forget
andprune
etc.Otherwise without running
rustic
interactively I do not have really much information about what happened - and it is all what log files are about:)