Comment 16 for bug 1710515

Thanks a lot Vej !
You are right, but i'm a bit unconfortable with this solution which i'm not at all familiar with and which will probably take time and nerves ;-)
Well, if nothing else works, i'll try the "duplicity" thing.

But i have another card in my pocket before that: Next monday i will be back from vacation and have access to my second back up, that i also do on a weekly basis.
I will try a total restore (once again) but from this second source.
I will see if it works as usual or if the probleme stays the same.

Probably, knowing if the problem does or doesn't happen then should be interesting to understand, and maybe solve it, in the future.
=> If it doesn't happen, we can assume it comes from an incident during back up, or from the media itself.
=> If it does, then the problem is systematic, and due to an error in my config, or between DD and TB...

I'll let you know the results as soon as i can try.

And if it doesn't , i will probably have tons of questions about duplicity commands ;-)