Thanks Radosław,
Yes, other backups were running at the time of this jobid 5738, I have 100 devices to handle ~200 concurrent backup jobs. Looks like there was shortage of free device for reading the previous full backup, although a device was reserved for writing. Regards Yateen From: Radosław Korzeniewski <rados...@korzeniewski.net> Sent: Saturday, January 18, 2020 3:47 PM To: Shaligram Bhagat, Yateen (Nokia - IN/Bangalore) <yateen.shaligram_bha...@nokia.com> Cc: Bacula-users@lists.sourceforge.net Subject: Re: [Bacula-users] Issue with config setting "Max Virtual Full Interval" Hello, pt., 10 sty 2020 o 10:38 Shaligram Bhagat, Yateen (Nokia - IN/Bangalore) <yateen.shaligram_bha...@nokia.com<mailto:yateen.shaligram_bha...@nokia.com>> napisał(a): Hi all, I am using bacula v 9.4.4 on Centos 6.4. for disk file based backup. Let's start simple. 10-Jan 13:54 bacula-server-dir JobId 5738: Warning: This Job is not an Accurate backup so is not equivalent to a Full backup. Start correcting obvious issues which job is reporting. 10-Jan 13:54 bacula-server-dir JobId 5738: Using Device "DeviceF1" to write. 10-Jan 13:54 bacula-server-sd JobId 5738: Fatal error: Read and write devices not properly initialized. Virtual full require a single device to read previous data and a single device to write consolidated job. It requires to read previous (virtual)full job and then all incremental ones. It means you have to ensure that Bacula has two devices configured and it can read required data, ie. the previous and the current virtual full do not share a volume. You should review your configuration and corrects errors. Then it start working. I hope it helps. best regards -- Radosław Korzeniewski rados...@korzeniewski.net<mailto:rados...@korzeniewski.net>
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
