Em 15 de maio de 2015 08:21:18 GMT-02:00, Kern Sibbald <kern AT sibbald DOT com> escreveu:

Hello,

As far as I know, there was never any Bacula version 3. 

Where did you get the binaries?
What is the exact version you are running?
Is your OS Window 2003 SBS?  (if I am not wrong, this system is no
longer supported).

It sounds like your SD is running on a Windows machine and you are
probably running a *very* old or non-existent version of Bacula. 

Although there were a few Windows versions that had a Director and a
Storage daemon, the Windows SD and Director have never been fully
supported, and especially writing to tape.  In fact if you are using
Windows to write to tape, I would be interested to hear about it, and in
any case, if it is a Windows system, I am not surprised to hear that
there are problems because I have never had a Windows system with an
attached tape drive to test.

Best regards,
Kern

On 14.05.2015 13:47, Markus Rosjat wrote:
 Hi there,

 we had this toic befor and I#m back again...

 My Backupjobs started to use less tape space then expected a year ago
 the System is quiet aged so this is running on a 2003 SBS with a bacula 
 version 3

 Like I said it started from one day to the other that tapes got written 
 on  but less then the expected 350+ GB for a LTO3 tape. what Ive done so 
 far:

   - changed terminator
   - canged cable
   - changed the drive
   - changed the whole autoloader
   - used brand new tapes
   - cleaned drive a dozen times
   - used HP tools to check for problems

 nothing really help, in fact its getting even worse. We started with 3 
 tapes for less then 1TB and now Im at 6 tapes for 1,2 TB of data. I get 
 this line for every Tape that reaches the "end" of the tape or better 
 bacula thinks its the end

 02-May 17:12 fg-back-sd JobId 11840: Error: Error writing final EOF to 
 tape. This Volume may not be readable.
 /home/kern/bacula/k/bacula/src/stored/dev.c:1723 ioctl MTWEOF error on 
 "LTO3" (Tape0). ERR=Input/output error.

 but some post on the list suggest this is normal for a windows 
 environement and I got this when all worked well too. The strange part 
 is I havent changed any config at all.  since I know some people will 
 tell me without logs and stuff there is nothing to tell I will not ask 
 for possible causes because we going to change the backup in autmn 
 anyway and we will move on from bacula with all the problems we had over 
 the last year.

 But back to my question, is there any thing that bacula does to mark the 
 end of a tape even its not the end? And additional is it possible to 
 remove this marker (if it exist possibly in the database) . Like I said 
 in my opinion its not passible that 4 brand new tapes have errors 
 arround 200GB of written data.

 Regards




One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y

Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users