On Mon, Dec 12, 2005 at 02:05:16PM +0100, Jo wrote: > I'm not so sure this is a waste of resources. Only the files that were > changed will be in those incrementals. The first one will catch all the > files that changed while the full was running. The second one will be > virtually empty.
In my case, these would get run Sunday night, and so both would contain little beyond the log files that have changed. I'd rather not bother saving these twice, and could certainly do without the three near-identical copies of the catalog backup. In addition to the waste of tape, this creates a bunch of job entries that I don't care about. > If you skip these backups and then a problem occurs the > following day, you won't be able to restore to the most current > situation, but only to the situation at the moment of the full backup. That's a good reason to leave the default action as is, although in my situation I'd still like to be able to override it. -- John Kodis. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
