Further to a question I asked previously about Linux filesystems, NTFS appears to have the ability to record a 'change journal' of all filesystem changes. If I understand correctly, with the appropriate file daemon, this could allow for _very_ fast incremental backups (eg you'd just need to work through the list of changed files), and also 'perfect' backups (in terms of knowing which files have been moved or removed).
This introduces a similar limitation to that of an MS Exchange backup - bacula would now have slightly less control over when you can do an incremental or differential backup from, but with SD Muxer's and job copying (rather than job migration), this may be less of a problem than it is now (no need for two full backups one after the other in order to get two copies of a backup) It also means that the FD would have to have a bit more intelligence, and would have to get some direction from the director about when it was okay to purge older changes (eg probably the last full backup, but maybe sometimes you wouldn't want this). Has anyone done any thinking along these lines before? IMHO it could do wonders for efficiency... Thanks James ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
