Per olof Ljungmark wrote: > So, > > What did I do wrong here? > > I upgraded bacula from 2.0.3 to 2.2.0, FreeBSD 6. > Yesterdays nightly job failed big time, each backup failed with > > 16-Aug 21:46 candyman-sd: Volume "UNW259L2" previously written, moving > to end of data. > 16-Aug 21:47 candyman-sd: mars.2007-08-16_21.30.02 Error: Bacula cannot > write on tape Volume "UNW259L2" because: > The number of files mismatch! Volume=3 Catalog=4 > 16-Aug 21:47 candyman-sd: Marking Volume "UNW259L2" in Error in Catalog. > > and eventually all available tapes went Append -> Error > > There were no errors in previous 2.0.3 backups and I did not see any > notes that the database needs to be updated?
I'm answering my own question now. I needed to modify my bacula-sd.conf file to get it right, this is what it looks like now with 2.2.0 on FreeBSD-6 and a HP SSL1016 LTO2 changer. Also, there was a bit of a problem to get unused but labeled tapes to work. Device { Name = Drive-1 Media Type = LTO-2 Archive Device = /dev/nsa0 LabelMedia = yes; # lets Bacula label unlabeled media Random Access = No; AutomaticMount = yes; # when device opened, read it RemovableMedia = yes; BSF at EOM = no; TWO EOF = no; Fast Forward Space File = yes; Hardware End of Medium = no; Backward Space Record = no; Backward Space File = no; AlwaysOpen = no; Maximum Spool Size = 65498251264 Spool Directory = /dataspool AutoChanger = yes Alert Command = "sh -c '/usr/local/sbin/tapeinfo -f %c |grep TapeAlert|cat'" } ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users