--analyze vs dry run

[bobpaul]

Is --analyze purely informative or does it create some cache that can be used for future deduplication? If so, where is that cache file stored?

The questions I'm trying to answer are:

• Should I run analyze before I ask it to deduplicate
• If I'm running this via docker, should I make a volume for some cache file/folder to speed up future runs?

[Lakshmipathi]

Hi @bobpaul , right now --analyze is for purely informative purpose only. It doesn't store cache files.

Should I run analyze before I ask it to deduplicate

Yes, definitely try dry-run first and check (block size) which provides better de-duplication. (Also make sure to have a backup of your critical data. :P As you may have noticed, I didn't update this repo in recent time but I'm free from work now (read as: jobless guy :D) , will be focusing on dduper in coming days and weeks. )

If I'm running this via docker, should I make a volume for some cache file/folder to speed up future runs?

As I mentioned before above, we don't have cache file from --analyze. If you think it will be helpful, let me know. I'll explore the possibility of adding this option.