No more backup and empty restore

Bug
, , ,
#1

Hello all,
After adding 6Go in a directory of my backup I ran a backup command through web-ui but it exited very quickly. I checked and it seems that the new files are not viewed. After some tests it seems that duplicacy doesn’t detect new files at all.
Here is the last log:

Running backup command from /home/uisang/.duplicacy-web/repositories/localhost/0 to back up /donnee
Options: [-log backup -storage local-backup-cedric -stats]
2019-11-08 21:00:01.099 INFO REPOSITORY_SET Repository set to /donnee
2019-11-08 21:00:01.100 INFO STORAGE_SET Storage set to /backup/duplicacy_donnee
2019-11-08 21:00:01.148 INFO BACKUP_START Last backup at revision 70 found
2019-11-08 21:00:01.148 INFO BACKUP_INDEXING Indexing /donnee
2019-11-08 21:00:01.148 INFO SNAPSHOT_FILTER Parsing filter file /home/uisang/.duplicacy-web/repositories/localhost/0/.duplicacy/filters
2019-11-08 21:00:01.148 INFO SNAPSHOT_FILTER Loaded 4 include/exclude pattern(s)
2019-11-08 21:00:01.784 INFO BACKUP_END Backup for /donnee at revision 71 completed
2019-11-08 21:00:01.784 INFO BACKUP_STATS Files: 0 total, 0 bytes; 0 new, 0 bytes
2019-11-08 21:00:01.784 INFO BACKUP_STATS File chunks: 0 total, 0 bytes; 0 new, 0 bytes, 0 bytes uploaded
2019-11-08 21:00:01.784 INFO BACKUP_STATS Metadata chunks: 3 total, 403 bytes; 1 new, 397 bytes, 294 bytes uploaded
2019-11-08 21:00:01.785 INFO BACKUP_STATS All chunks: 3 total, 403 bytes; 1 new, 397 bytes, 294 bytes uploaded
2019-11-08 21:00:01.785 INFO BACKUP_STATS Total running time: 00:00:01
2019-11-08 21:00:01.785 INFO SCRIPT_RUN Running script /home/uisang/.duplicacy-web/repositories/localhost/0/.duplicacy/scripts/post-backup
2019-11-08 21:00:02.294 INFO SCRIPT_OUTPUT %!T(MISSING)otal    %!R(MISSING)eceived %!X(MISSING)ferd  Average Speed   Time    Time     Time  Current
2019-11-08 21:00:02.294 INFO SCRIPT_OUTPUT Dload  Upload   Total   Spent    Left  Speed
2019-11-08 21:00:02.294 INFO SCRIPT_OUTPUT 0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100     2  100     2    0     0      4      0 --:--:-- --:--:-- --:--:--     4
2019-11-08 21:00:02.294 INFO SCRIPT_OUTPUT OK

And if I go to restore, the file list is always empty???

Any command to check things. I’m a bit worried…

Thanks

#2

What do your filters look like?

#3

Nothing special…

+Nextcloud/
+cc/
+dr/
+np/
#4

I think this is probably what you’re looking for. I still don’t understand the include/exclude filtering logic well enough to justify all of its nuances, but this should work based on a quick test I just did in a fresh repo (since I don’t adjust my filters often enough to be comfortable with them).

+Nextcloud/*
+cc/*
+dr/*
+np/*

If you added these using the web GUI, I don’t think clicking on a folder and then clicking include actually creates the correct entries in the filters file to include the directory. I think it creates entries like the ones in your post, but that don’t do what you might expect.

2 Likes
#5

You are right.
Incredible, I reinstall it so much time due to the migration from cli to web that I didn’t get it.
How is it possible that the use of the gui create a pattern that is not working.
I don’t feel trustful in duplicacy and it’s a concern for a backup app.

Thank you very much for your help.

#6

I would personally consider this a bug.

FWIW the whole folder selection is on the roadmap to be overhauled in a way that is more user friendly.

#7

@gchen Is it a bug to you? Thanks.

#8

Yes, this is a bug (if you don’t add an include pattern). If all patterns are include patterns then anything not matching a pattern is automatically excluded. The added pattern for each selected directory should have been +dir/* instead of +dir/. I’ll fix this in the next release.

1 Like