Restore doesn't restore with no useful message

duplicacy -v restore -r 108 etc/apt/sources.list
Repository set to /
Storage set to gcd://Duplicacy/AStorage
Using 16384 iterations for key derivation
etc/apt/sources.list
Loaded 6 include/exclude pattern(s)
Pattern: -proc/*
Pattern: -run/*
Pattern: -dev/*
Pattern: -sys/*
Pattern: -tmp/*
Pattern: -var/lib/docker/*
Restoring / to revision 108
Restored / to revision 108
Total running time: 00:00:24

The file is not restored, it might be related to the fact that the file exists on the target and I should use overwrite flag, but I’d expect some message about that (I saw somewhere in the forum something like “/etc/apt/sources.list already exists”)

How does it work exactly? Should I always use overwrite flag for restoring older versions of existing files?

That file was skipped because the existing file has the same size and timestamp as the one to be restored. You’re right that there should be at least a message to say so. I’ll fix this in the next update.

1 Like

thanks for the answer gchen, but that doesn’t seem to be my case.
I’ve just modified the file, and both size and time were modified locally, then I run the restore command again

# duplicacy -v -log restore -r 108 etc/apt/sources.list
2019-05-22 19:42:45.687 INFO REPOSITORY_SET Repository set to /
2019-05-22 19:42:45.687 INFO STORAGE_SET Storage set to gcd://Duplicacy/AStorage
2019-05-22 19:42:49.429 TRACE CONFIG_ITERATIONS Using 16384 iterations for key derivation
2019-05-22 19:42:49.685 TRACE RESTORE_PATTERN etc/apt/sources.list
2019-05-22 19:43:05.165 INFO SNAPSHOT_FILTER Loaded 6 include/exclude pattern(s)
2019-05-22 19:43:05.165 TRACE SNAPSHOT_PATTERN Pattern: -proc/*
2019-05-22 19:43:05.165 TRACE SNAPSHOT_PATTERN Pattern: -run/*
2019-05-22 19:43:05.165 TRACE SNAPSHOT_PATTERN Pattern: -dev/*
2019-05-22 19:43:05.165 TRACE SNAPSHOT_PATTERN Pattern: -sys/*
2019-05-22 19:43:05.165 TRACE SNAPSHOT_PATTERN Pattern: -tmp/*
2019-05-22 19:43:05.165 TRACE SNAPSHOT_PATTERN Pattern: -var/lib/docker/*
2019-05-22 19:44:55.942 INFO RESTORE_START Restoring / to revision 108
2019-05-22 19:44:56.196 INFO RESTORE_END Restored / to revision 108
2019-05-22 19:44:56.196 INFO RESTORE_STATS Total running time: 00:02:07 

no other output, file was not restored

# duplicacy -v -log history -hash -r 108 etc/apt/sources.list
2019-05-22 19:48:47.142 INFO REPOSITORY_SET Repository set to /
2019-05-22 19:48:47.142 INFO STORAGE_SET Storage set to gcd://Duplicacy/AStorage
2019-05-22 19:48:49.490 TRACE CONFIG_ITERATIONS Using 16384 iterations for key derivation
2019-05-22 19:48:56.552 INFO SNAPSHOT_HISTORY     108:             774 2019-04-26 07:21:21 ef73cc97b838e8f21d9c24bc750c58e54417318875ad7960e7b7326de4372424 etc/apt/sources.list
2019-05-22 19:48:56.552 INFO SNAPSHOT_HISTORY current:             705 2019-05-22 19:48:22 cda428d5f14b93cc0f975f6d4e5ea9f4d4a2db2a231ed067e8b9ee8f98bd9053 etc/apt/sources.list*

This is because etc/apt/sources.list was treated as a pattern: Fixed a bug where filenames starting with i or e are mistakenly inter… · gilbertchen/duplicacy@abcb4d7 · GitHub

This bug has been fixed in version 2.2.0.