>> Why? Shouldn't bacula treat these as a newly created directory with new >> files in it, and back them up? This is a big burden requiring people >> to remember whether they should use cp or mv to move files. Besides >> this, and the disk space issue, mv is a simple pointer redirection, and >> might be faster than a cp depending on how high in the tree you are >> working on. > > These apply only to incremental and differential backups. Those files > will be backed up on the next full backup.
Yes, but what if someone moves the directory 1 day after the Full, and it's another 29 or 30 until the next full? Potentially if you needed to restore the name change could be missed, only to be found later when something breaks because the new directory isn't there. Will changes to the files at least be noticed? Even then, what would I get if I restored? Would I get the new files in the old path name? Or will bacula finally take not of the new name. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
