Hi Mehrdad,

Am 30.08.2024 um 13:05 schrieb Mehrdad Ravanbod:
Hi Guys

I am looking into this issue.
the documentation i have found mentions that the system decides on which files to include on a diff or inc backup by looking at the Changed and modified fla(ctime, stime) and if Accurate is set to yes, then the whole files list from the full backup is sent to the filedaemon on the client machine,

Right.

it does not mention the dirty-bit of windows file system, i guess because it does not operat on the file blocks( i am guessing this maybe done in the BMR feature included in the Enterprise version)

No. Bacula does not use the dirty bit at all, and that's one of the best things you can do with this bit. Anything relying on it is functionally broken, I think :-)

The Enterprise BMR thing also does not use it. It also does not do a block level backup, and the dirty bit of windows files has nothing to do with block level backups.

The problem is that all the info I have found so far is old, i mean 10-15 yers old, some online documentations is talking about Bacula 3.03. I was wondering if there has been any developements on the schemes bacula uses for this, is there any newer documentations that anyone has the links to?? Or does any devs can shed some light onto how this is done on the newer versions??

Any documentation that states that Bacula uses ctime and mtime to compare if a file has been modified since the reference backups end time by default and can be configured to work differently using Accurate Mode and Accurate File Set Include Options is simply still correct.

Well, and on Windows, ctime and mtime do not exist, the time stamp semantics are slightly differently there.

Newer versions have not changed that.

Also, forget about the dirty bit on windows :-)

Cheers,

Arno

--
Arno Lehmann

IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück


_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to