No good way to tell what files are eating up backup space

Bug #1854600 reported by frEEk on 2019-12-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Déjà Dup

Bug Description

Despite excluding all the appropriate folders I could think of, my initial backup was way too big. Unfortunately other than restoring to another drive and they analysing the resulting file tree, there is no way to tell what is responsible for the unexpected backup filesize since the backup format doesn't reflect the source directory tree.

A tool that allows the user to inspect the backup contents would be VERY useful.

deja-dup 37.1-2fakesync1ubuntu0.1
duplicity 0.7.17-0ubuntu1.1

Wishlist item, obviously.

Vej (vej) on 2019-12-04
Changed in deja-dup:
status: New → Triaged
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers