>>>>> On Mon, 09 Jan 2006 23:53:14 +0100, Julien Cigar <[EMAIL PROTECTED]> said:
Julien> | 65 | canis-job-full | 2006-01-09 03:00:02 | B | F | 500389 | 86335144294 | T | Julien> | 66 | canis-job-incremental | 2006-01-09 20:00:01 | B | F | 501015 | 86544091759 | T | Julien> +-------+-----------------------+---------------------+------+-------+----------+-------------+-----------+ Julien> As you can see, we are today 2006-01-09. A full backup on tape of client Julien> canis started at 3:00:02 and finished successfully (job id 65) at 08:51. Julien> Why on 2006-01-09 at 20:00 PM the incremental backup is upgraded to a Julien> full backup (job id 66) ? Julien> As you can see, job id 62 has also been upgraded to a full backup Julien> without any reasons because job id 53 was a full backup three days ago Julien> ... I'm a bit confused ... Julien> Any ideas ? It looks like you have two different jobs defined, called canis-job-full and canis-job-incremental. If so, that is not the correct way to run incremental backups. Instead, you want one job called canis-job which is scheduled with different levels and pools. See the "Automated Disk Backup" example in the manual. __Martin ------------------------------------------------------- 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
