Hello,
Volker Sauer wrote:
On Fr, 15 Jul 2005, Mario Ohnewald wrote:
In my eyes this is a huge "bug".
Lets says you have a big home directory with a couple of projects and
sourcecode files in there, and you reorganize the folder structure and
you move some files and folders around.
All this then would NOT be included in a backup!
What's the point of a backup then?
In this case you should submit a bug in the bug database at bacula.org.
Indeed.
According to bacula's manual, Director configuration, Jobs, Job Level
Incremental:
The File daemon (Client) decides which files to backup for an
Incremental backup by comparing start time of the prior Job (Full,
Differential, or Incremental) against the time each file was last
``modified'' (st_mtime) and the time its attributes were last
``changed''(st_ctime). If the file was modified or its attributes
changed on or after this start time, it will then be backed up.
So, a mv'ed file should be backed up:
# ls >> datetest
# ls -l datetest
-rw-r--r-- 1 root root 944 Jul 15 23:20 datetest
# ls -lc datetest
-rw-r--r-- 1 root root 944 Jul 15 23:20 datetest
# sleep 60; mv datetest testdate
# ls -lc testdate
-rw-r--r-- 1 root root 944 Jul 15 23:21 testdate
# ls -l testdate
-rw-r--r-- 1 root root 944 Jul 15 23:20 testdate
So, at least o my linux box the ctime is modified by mv'ing a file -
which is correct concerning POSIX etc. standards, I believe.
Accordingly, bacula should back up this file.
Before submitting a bug report I suggest you verify this. Kern will wnat
something like this anyway :-)
- Create a test job with a simple file set, for example something like
/tmp/bactest/
- Put a file in it.
- Backup.
- Use estimate listing command to see if his file would be saved again
at incremental level (it should not, obviously).
- Move a file from another directory into your test directory.
- Verify the time stamps using ls -l and ls -tc (assuming you use a
more-or-less standard unix OS).
- Use the estimate listing command to see if this file would be included.
When the ls verification shows old ctime and mtime the bug is the OSes,
not baculas.
My comment:
Actually you are right. The path to the file should be included in the
hash of the file. But: modifying this hash would force all users of
bacula to a unscheduled full-backup (which in my case would be a lot
of effort).
Erm... What are we talking about?
File hashes?
When deciding which files to back up bacula uses the metadata time
stamps only, as far as I know... the client is, to my knowledge, not
interested in the file name or path (as long as it is one include and no
exclude lists, of course).
Maybe an option in the file set:
Include Path in Hash = (yes|no)
would be the solution?
I don't understand to what... but that might be because it's too late
and the day was too warm.
Arno
Regards
Volker
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
