Re: [Bacula-users] Incremental backup, not accurate?
On 11/15/06, Michel [EMAIL PROTECTED] wrote: Hello all, I read in the bacula docs that incremental backups use modification times to decide if it or doesn't backup. For example and as it is said in the doc, a mv on a directory doesn't change the modification time. So, if I am not wrong, incremental backup are not accurate? If this is true, how do you come over this? (except avoiding the use of mv) Thanks you! (I just started using Bacula, so I don't know if this is actually possible!) I also looked into this same problem. I solution I was thinking about is to let Bacula run a check to compare the real data with the backup. this should produce a nice list of file and directories that are different. I then can then touch these files, so the will be backuped in the next incremental backup. Does anyone know is this is possible? I'm running Bacula on Debian Linux, use file volumes (on the Debian box) and all clients are winXP. Jaap. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Incremental backup, not accurate?
On Wed, 15 Nov 2006 18:53:47 +0100, Michel said: I read in the bacula docs that incremental backups use modification times to decide if it or doesn't backup. For example and as it is said in the doc, a mv on a directory doesn't change the modification time. So, if I am not wrong, incremental backup are not accurate? If this is true, how do you come over this? (except avoiding the use of mv) Incremental backups use the ctime as well as the mtime by default, so it depends on whether mv changes the ctime (some file systems do, some don't). If Bacula does detect the moved file then there is also a problem with restoring from incrementals, because it will create two copies of the file, with the old and the new names. There is currently no way around this, so regular full backups are advisable. __Martin - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
