vykar -v should report new/ removed/ changed files

[goebbe]

#65 (reply in thread)

You can enable info logging with -v which will print new and changed files.

Testing vykar 0.12.10 on Linux:

vykar -v in the terminal - should report new / removed and changed files:

1. Example: Applying a new exclude pattern that matches approx 1000 files - this is the output of vykar -v:

(base) user@goebbe:~$ vykar -v
 INFO Using config: /home/user/.config/vykar/config.yaml (user)
==> Starting backup
 INFO file cache loaded from disk sections=1 entries=36130
 INFO file cache section key="/home/user" anchor=8aa46f8978a2b78a entries=36130
 INFO file cache: section valid, using cached metadata source_label="home"
Files: 10479, Original: 11.68 GiB, Compressed: 9.10 GiB, Deduplicated: 0 B, CurrFiles: 21286, Original: 29.17 GiB, Compressed: 20.36 GiB, Deduplicated: 0 B, CurFiles: 33917, Original: 38.28 GiB, Compressed: 23.11 GiB, Deduplicated: 0 B, Cur INFO Snapshot 'b6be9940' created: 35506 files, 43256286423 original, 25435001006 compressed, 0 deduplicated
Files: 35506, Original: 40.29 GiB, Compressed: 23.69 GiB, Deduplicated: 0 B, Current: 
==> Starting prune
==> Starting compact
 INFO Repacking 007e8a73025f4ba0 (11 live blobs)
 INFO Repacking 82f4b701d76c6008 (1 live blobs)
 INFO Deleting empty pack def0fa95c189f1d9
==> Starting check
Snapshot created: b6be9940
  Source: /home/user (label: home)
  Files: 35506, Original: 40.29 GiB, Compressed: 23.69 GiB, Deduplicated: 0 B
Pruned 1 snapshots (kept 5), freed 4 chunks (125.09 KiB)
Compaction complete: 2 packs repacked, 1 empty packs deleted, 218.83 KiB freed
  1 orphan pack(s) (present on disk but not in index)

=== Summary ===
  backup       ok
  prune        ok
  compact      ok
  check        skipped (check not due)
  Duration:    5s

2. Example: A new file has been created - this is the output of vykar -v:

(base) user@goebbe:~$ vykar -v
 INFO Using config: /home/user/.config/vykar/config.yaml (user)
==> Starting backup
 INFO file cache loaded from disk sections=1 entries=35506
 INFO file cache section key="/home/user" anchor=fdc42ba7753c8cf8 entries=35506
 INFO file cache: section valid, using cached metadata source_label="home"
 INFO Snapshot '3d5e47b8' created: 35507 files, 43256286424 original, 25435001046 compressed, 0 deduplicated
Files: 35507, Original: 40.29 GiB, Compressed: 23.69 GiB, Deduplicated: 0 B, Current: Zotero/translators/Citavi 5 XML.js
==> Starting prune
==> Starting compact
 INFO Deleting empty pack a680c67810df6c4e
==> Starting check
Snapshot created: 3d5e47b8
  Source: /home/user (label: home)
  Files: 35507, Original: 40.29 GiB, Compressed: 23.69 GiB, Deduplicated: 0 B
Pruned 1 snapshots (kept 5), freed 1 chunks (40.68 KiB)
Compaction complete: 0 packs repacked, 1 empty packs deleted, 40.69 KiB freed
  1 orphan pack(s) (present on disk but not in index)

=== Summary ===
  backup       ok
  prune        ok
  compact      ok
  check        skipped (check not due)
  Duration:    5s

In both cases vykar -v does not report the new/ removed/ changed files.

A list of the source_path filename would be helpful for debugging.

[m3nu]

Hmm. This should work actually. Maybe it doesn't work for the 'full backup flow', but only for the backup subcommand.

[goebbe]

Thank you! Until now, I only tested vykar -v

I can confirm that
vykar -v backup does provide information about

• new files
• modified files

However, there is no equivalent information about the files that have been excluded in the snapshot,

• e.g. by **exclude_patterns**
• or since they have been deleted (since the last backup/ snapshot).

The number of files is smaller (by the number of removed files) - but this is the only feedback for removed files.

[m3nu]

OK. Then I see 2 possible improvements:

1. Standardize logging for the full backup flow command.
2. Log excluded files at the INFO log level.

[goebbe]

Should/ could vykar -v also distinguish between

1. removed from a snapshot (e.g. excluded/ deleted compared to last existing snapshot) - but file/ folder may still be part of older snapshots
   AND
2. removed from a repository, i.e. there is no snapshot in the repository, with this file (next run of vykar compact will free the space?

Probably the first would be easier (and faster) -
and vykar snapshot find can be used to check if a folder/ file is still somewhere in the repo (old snapshots), anyway.