Re: [Bacula-users] allways full even if incremental
Hi, Actually bacula uses ctime by default, not mtime. Actually under the 'Level = Incremental' section of the page you linked it states: 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 we were both right almost :) One possibility which occurs to me is that there may be some kind of time synchronization problem between the director and the client. I suspect the problem as described could be a result of the client's clock being too far ahead of the director's. I would suggest verifying the client and director's clocks more or less agree. This may be a non-obvious issue if the client and director are in different time zones -- or, more to the point, if one of them is in the wrong timezone. I've seen Bacula compensate for different clock times on servers a few seconds/minutes apart - it logs a line at the top of the job saying it's doing so. However, I've never tried it when the clocks are hours/timezones apart so cant say if it'd compensate then. Cheers, -- Troy Daniels iTouch Australia, a Buongiorno company Senior Systems Administrator Ph +618 6461 4102 troy.dani...@itouch.com.auFax +618 6461 4199 www.itouch.com.au -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] allways full even if incremental
snip I've seen Bacula compensate for different clock times on servers a few seconds/minutes apart - it logs a line at the top of the job saying it's doing so. However, I've never tried it when the clocks are hours/timezones apart so cant say if it'd compensate then. Just for the record: 30-Jul 10:49 Sales-fd JobId 10345: Warning: DIR and FD clocks differ by -43952 seconds, FD automatically compensating. blah, blah, blah, Termination:Backup OK That's around 12 hours difference. Ken B. Cheers, -- Troy Daniels iTouch Australia, a Buongiorno company Senior Systems Administrator Ph +618 6461 4102 troy.dani...@itouch.com.auFax +618 6461 4199 www.itouch.com.au --- --- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] allways full even if incremental
Troy Daniels wrote: Hi, Actually bacula uses ctime by default, not mtime. Actually under the 'Level = Incremental' section of the page you linked it states: 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 we were both right almost :) Fair enough. One possibility which occurs to me is that there may be some kind of time synchronization problem between the director and the client. I suspect the problem as described could be a result of the client's clock being too far ahead of the director's. I would suggest verifying the client and director's clocks more or less agree. This may be a non-obvious issue if the client and director are in different time zones -- or, more to the point, if one of them is in the wrong timezone. I've seen Bacula compensate for different clock times on servers a few seconds/minutes apart - it logs a line at the top of the job saying it's doing so. Ah, interesting. I use ntp on all my systems, so I've never seen that message. Anyway, it occurred to me that simply picking a file on the client that is getting backed up repeatedly and doing a stat on it might be informative if the problem is time or timestamp related: Stat shows you the mtime, ctime, and atime (among other things): stat myfile File: `myfile' Size: 11603298Blocks: 22664 IO Block: 4096 regular file Device: fe03h/65027dInode: 810095 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 500/ cedric) Gid: ( 500/ cedric) Access: 2009-08-19 23:04:07.0 -0700 Modify: 2002-02-09 04:55:02.0 -0700 Change: 2009-08-19 23:04:07.721728624 -0700 In particular, doing a stat on the same file immediately before, and again immediately after a backup might reveal something. - Cedric -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] allways full even if incremental
hi, On Tue, 2009-09-08 at 19:56 +0100, Martin Simmons wrote: On Tue, 08 Sep 2009 14:05:19 +0200, Gerald Leier said: hello, i noticed some strange behaviour when backing up one of our linux hosts with bacula. bacula allways backs up everything. if i run it 3 times in a row it allways produces the same amount of files (Incremental backup) at first i thought it may be because of some timestamps missing.. but the mount options are the same on hosts that dont do a allways full never incremental even if incremental backup. any suggestions how to debug that, or any ideas what can cause that behaviour? bacula version is 3.0.1 the filesystem taht makes trouble: / type ext3 (rw,acl,user_xattr) kernel: 2.6.16.60 Does Bacula upgrade all of the jobs to Full or is it running them as Incremental? The log output shows this. it is running them as incremental. Are you using the same fileset for working and broken hosts? yes its the same fileset for the other linux hosts. gerald __Martin -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users -- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] allways full even if incremental
08.09.2009 15:05, Gerald Leier пишет: bacula version is 3.0.1 Try to update up to 3.0.2 -- WBR, Dubrovskiy Vyacheslav smime.p7s Description: S/MIME Cryptographic Signature -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] allways full even if incremental
Troy Daniels wrote: Is it possible the files where created with a mtime in the future? From memory, Bacula uses the mtime of the files to determine if they have changed since the last backup ran. If they have a mtime in the future they get backed up every time. If so, using 'touch' on all the files to reset their mtime should stop the behaviour I believe. Actually bacula uses ctime by default, not mtime. According to the documentation for File Set options ( http://www.bacula.org/manuals/en/install/install/Configuring_Director.html#SECTION0067 ), if you set keepatime=yes WITHOUT also setting mtimeonly=yes, bacula will back up every file every time, even for incrementals. HOWEVER if the OP is literally using one file set definition for multiple hosts, then he should expect to see this behavior on all of those hosts, not just the one. One possibility which occurs to me is that there may be some kind of time synchronization problem between the director and the client. I suspect the problem as described could be a result of the client's clock being too far ahead of the director's. I would suggest verifying the client and director's clocks more or less agree. This may be a non-obvious issue if the client and director are in different time zones -- or, more to the point, if one of them is in the wrong timezone. - Cedric -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] allways full even if incremental
On Tue, 08 Sep 2009 14:05:19 +0200, Gerald Leier said: hello, i noticed some strange behaviour when backing up one of our linux hosts with bacula. bacula allways backs up everything. if i run it 3 times in a row it allways produces the same amount of files (Incremental backup) at first i thought it may be because of some timestamps missing.. but the mount options are the same on hosts that dont do a allways full never incremental even if incremental backup. any suggestions how to debug that, or any ideas what can cause that behaviour? bacula version is 3.0.1 the filesystem taht makes trouble: / type ext3 (rw,acl,user_xattr) kernel: 2.6.16.60 Does Bacula upgrade all of the jobs to Full or is it running them as Incremental? The log output shows this. Are you using the same fileset for working and broken hosts? __Martin -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
