Re: [Bacula-users] New volumes put into "Full" status in succession from single backup

2009-01-23 Thread Alan Brown
On Thu, 22 Jan 2009, Win Htin wrote: > Problem resolved. The FC switch was acting up and due to that, the tape > backups went crazy while doing FC path failover. Replaced the switch and > everything is back to normal. Thanks! What model/firmware revision is the switch? --

Re: [Bacula-users] New volumes put into "Full" status in succession from single backup

2009-01-22 Thread Win Htin
Problem resolved. The FC switch was acting up and due to that, the tape backups went crazy while doing FC path failover. Replaced the switch and everything is back to normal. Thanks! On Tue, Jan 20, 2009 at 12:52 PM, Win Htin wrote: > I'm seeing "st0: Error 1 (sugg. bt 0x0, driver bt 0x0, ho

Re: [Bacula-users] New volumes put into "Full" status in succession from single backup

2009-01-20 Thread Win Htin
I'm seeing "st0: Error 1 (sugg. bt 0x0, driver bt 0x0, host bt 0x1)" messages from "dmesg" command and checking the /var/log/messages file, I see the same. I was able to do "mt" commands a couple of hours ago, failed a few minutes ago and it is working again right now. Maybe I should restart th

Re: [Bacula-users] New volumes put into "Full" status in succession from single backup

2009-01-20 Thread John Drescher
On Tue, Jan 20, 2009 at 11:49 AM, Win Htin wrote: > Hi folks, > > I received a "Backup Fatal Error" report from one of my prod backups last > evening. After going through the report, I noticed the initial volume that > was being used went in Error. Bacula loaded a new volume from scratch pool, > c

[Bacula-users] New volumes put into "Full" status in succession from single backup

2009-01-20 Thread Win Htin
Hi folks, I received a "Backup Fatal Error" report from one of my prod backups last evening. After going through the report, I noticed the initial volume that was being used went in Error. Bacula loaded a new volume from scratch pool, continued with the backups and after writing less than 18GB of