Chuck Swiger wrote:
Alex Zbyslaw wrote:
Damian Sobieralski wrote:
I added the following to my tape drive area in the bacula-sd-conf:
Minimum Block Size = 64512
Maximum Block Size = 64512
I'm not seeing those errors any longer. I've restored and all seems
to go well.
Good stuff! Did t
Alex Zbyslaw wrote:
Damian Sobieralski wrote:
I added the following to my tape drive area in the bacula-sd-conf:
Minimum Block Size = 64512
Maximum Block Size = 64512
I'm not seeing those errors any longer. I've restored and all seems
to go well.
Good stuff! Did that number come out of yo
Damian Sobieralski wrote:
I added the following to my tape drive area in the bacula-sd-conf:
Minimum Block Size = 64512
Maximum Block Size = 64512
I'm not seeing those errors any longer. I've restored and all seems
to go well.
Good stuff! Did that number come out of your tape drive manua
FYI:
I added the following to my tape drive area in the bacula-sd-conf:
Minimum Block Size = 64512
Maximum Block Size = 64512
I'm not seeing those errors any longer. I've restored and all seems
to go well.
___
freebsd-questions@freebsd.org mai
Damian Sobieralski wrote:
2) See if you can't find some option to match the bacula record size
to that of your tape drive. Dump, for example, has a -b option e.g.
"-b 64" to set its record size. I'm puzzled by you only seeing three
messages though. Why would three buffers be smaller and not t
> 1) Try restoring the whole tape to either an empty partition, or if
> you don't have one of those, to /dev/null. /dev/null isn't
> conclusive proof, but I assume that if data weas dropped then there
> *should* be a failed checksum somewhere along the line.
I'll do that tomorrow (restore the wh
Damian Sobieralski wrote:
I'm test piloting bacula on a FreeBSD 5.4-REL system. All seemed to
work well in monitored tests. So last night I set up a job to run at
night. When I came in this morning, all seemed to go well...the
backup happened but I noticed 3 messages on the console:
(sa0:ahc0
