Well, that’s exactly how Duplicati sees it.
It will basically day “Oh, /joe/ and all contents has been deleted and /mark/ has appeared. I’ll flag all /joe/ contents for deletion but won’t actually delete any of it because I see the exact same content being used by /mark/”.
Things to keep in mind include:
-
pre-mark versions will still exist in /joe/ and want to be restored there unless you tell Duplicati otherwise
-
pre-mark versions exist in the /joe/ path so if you look at version history for a /mark/ path it will START after /joe/ history end
-
because the history has been split, some retention policy settings might act a bit strange for example, even if you said keep monthly versions forever, because /joe/ is seen as deleted that history will end up being purged.
In other words, assume your retention policy is starting over. @kenkendk, is this something that should be addressed in some way?