Hi everyone! How exactly are "new" files, which have to be backed up, determined by Bacula?
The reason for asking: Recently, I migrated my main data to a new set of hard drives. I did so by using "rsync -aH" which *should* leave all file timestamps etc. untouched. After the migration was finished, also all paths etc. were exactly the same as before, just with a new set of HDDs "underneath". However, in the next scheduled Bacula run (which was scheduled as Incremental), Bacula stared to backup *everything* of the abovementioned data. (I cancelled the job and will resume doing backups on this particular fileset with next regular Full backup which is scheduled for the upcoming Sunday anyway.) So - what went wrong here and how could this have been avoided? Regards Sebastian _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
