Back In Time

Created a profile as root and as user, conflict?

Asked by Borph

I have executed BIT as root and created a profile to backup once a week
/etc, /usr, /home, /var... etc. to
/media/externaldrive/BackInTime

But also I can run BIT as user, so I set up a backup once an hour of
/home/peter/Documents/
to the same backup folder as above.

Is there any conflict between two cronjobs backing up to the same folder on the external drive? I sometimes wonder about smart-remove and the amount of folders 'visible' in a snapshot.

Kubuntu 9.04. After solving my main problem with ext4 (https://bugs.launchpad.net/bugs/330824) BIT is running fine, thank you for this nice piece of software!

Question information

Language:
English Edit question
Status:
Solved
For:
Back In Time Edit question
Assignee:
No assignee Edit question
Solved by:
Bart de Koning
Solved:
Last query:
Last reply:
Revision history for this message
Borph (borph) said : 		#1

Well, I assume this is not a good idea.

As the cronjob of the user only backed up the particular home folder, the cronjob of root finds only this one and copies again the whole drive, so there is no use of the hardlinks. It just misses the /etc, /usr ... folders from the previous snapshot.

I have now only one profile active, as root, and with schedules per included folder activated. So /home has an hourly schedule, the rest weekly.

It would be nice if there would be no chance for this problem, but this would mean always maintain a (hardlinked) snapshot of the whole drive, and this seems to be inefficient. Well, we need links for folders, like on the Mac! :-)

Revision history for this message
Best Bart de Koning (bratdaking) said : 		#2

No, that is indeed not a good idea. It may only work if the destination folders are different, so the backups are not intertwined into eachother. You could file a bug for this, as it should actually be impossible to do this...

Revision history for this message
Borph (borph) said : 		#3

Thanks Bart de Koning, that solved my question.

Revision history for this message
Borph (borph) said : 		#4

filed under Bug #423086