Stay incremental when source folder becomes non-safe symlink

Asked by Torsten Crass

Hi there,

BIT has served me well for over two years now -- great piece of software!

Now, however, a problem came up when I had to move some of my source folders to a partition on a new (larger...) hard drive. In order to keep everything as close as possible to its previous state, I created identically-named symlinks to those moved folders. This way, most of my day-to-day operations work fine, but BIT seems to think that everything inside the thus treated folders has changed and wants to re-copy all contained files into the new snapshot.

So is there any way to trick BIT into treating the contents of folders which have become (unsafe, since pointing to a different file system) symlinks as unchanged? (Maybe, if there's no other way, by manually replacing the contents of the concerned backup folders with hard links to the previous snapshot?)

Thanx for any hints on this issue --

Torsten

Question information

Language:
English Edit question
Status:
Solved
For:
Back In Time Edit question
Assignee:
No assignee Edit question
Solved by:
Germar
Solved:
Last query:
Last reply:
Revision history for this message
Best Germar (germar) said :
#1

Hi Torsten,
please take a look at Question #241417 on how to keep them incremental.
But in your case I would rather use 'mount --bind' instead of symlinks. This should also make BIT keep everything incremental (didn't test it yet, but I'm pretty sure).

Regards,
Germar

Revision history for this message
Germar (germar) said :
#2

Sorry, Launchpad didn't link the Question automatically. Here you are:
https://answers.launchpad.net/backintime/+question/241417

Revision history for this message
Torsten Crass (torsten-crass) said :
#3

Thanks Germar, that solved my question.