> -Original Message-
> From: Brian Debelius [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 30, 2007 11:11 AM
> To: Robert Nelson
> Cc: bacula-users@lists.sourceforge.net
> Subject: Re: [Bacula-users] Trying to workaround the MTWEOF error
>
> Well, I know tha
Well, I know tha Nawfel had this problem with his Ultrium. I have an
Exabyte VXA-172, which is a firmware crippled VXA-320, and I have this
problem also. Yes this is a Windows installation. Director, sd, and fd
on one box.
Ahh, so you are saying that Maximum Volume Bytes, is the count of byt
Brian,
Are you also seeing this on Windows? If so it is quite possible that I have
a bug in the Windows emulation of the UNIX tape IOCTLs. I've ordered an
Ultrium 232 drive to do further testing on both Windows and Linux. If there
is anything we can do to fix this in Bacula I should have a fix
Yes, use the "maximum volume bytes" directive to limit the amount of
data stored to a tape. Once bacula sees that much data has been written,
it should label the volume as "full" and ask you for the next tape in
the pool.
Jason
Brian Debelius wrote:
> Brian Debelius wrote:
>
>> Is there a w
Brian Debelius wrote:
> Is there a way I can work around the end of tape MTWEOF error by telling
> bacula to limit the amount of data written to the tape? Lets say I have
> an 80GB tape. Is there a way to tell bacula to only write 75 or 70GB
> and then start a new tape?
>
> My next thought is,
