Hello,
I have an issue with Bacula on Debian 6.
Sometimes the backups are not working and I get the following error
message:
30-Sep 23:46 fpc-backup1-dir JobId 4840: shell command: run BeforeJob
"/etc/bacula/scripts/create_backup.sh"
30-Sep 23:46 fpc-backup1-dir JobId 4840: BeforeJob: Start
Hello,
I have an issue with Bacula on Debian 6.
Sometimes the backups are not working and I get the following error message:
30-Sep 23:46 fpc-backup1-dir JobId 4840: shell command: run BeforeJob
"/etc/bacula/scripts/create_backup.sh"
30-Sep 23:46 fpc-backup1-dir JobId 4840: BeforeJob: Starting
Zitat von b_...@mail.ru:
> On Nov 29, 2012, at 11:45 PM, lst_ho...@kwsoft.de wrote:
>
>>
>> Zitat von b_...@mail.ru:
>>
>>> On Nov 29, 2012, at 11:05 PM, Dan Langille wrote:
>>>
On Nov 29, 2012, at 2:26 PM, b_...@mail.ru wrote:
> Hello,
>
> I have a couple of hosts whi
On Nov 29, 2012, at 11:45 PM, lst_ho...@kwsoft.de wrote:
>
> Zitat von b_...@mail.ru:
>
>> On Nov 29, 2012, at 11:05 PM, Dan Langille wrote:
>>
>>>
>>> On Nov 29, 2012, at 2:26 PM, b_...@mail.ru wrote:
>>>
Hello,
I have a couple of hosts which backup through bacula. I have
This is a shot in the dark but on some IBM standalone servers (not blade)
disabling MSI did help fix a few issues (recv' queue errors, etc), your mileage
may vary on this one.
I'm not sure about freebsd but centos it is just setting an option for modprobe
after the driver init, example:
modprob
On 11/30/12 04:40, lst_ho...@kwsoft.de wrote:
>
> Zitat von Phil Stracchino :
>
>> On 11/29/12 16:45, lst_ho...@kwsoft.de wrote:
>>> Try with another NIC. We first had problems with our Bacula Server
>>> failing two clients out of ~20 with connection failures randomly.
>>> After ditching the Onbo
Zitat von Phil Stracchino :
> On 11/29/12 16:45, lst_ho...@kwsoft.de wrote:
>> Try with another NIC. We first had problems with our Bacula Server
>> failing two clients out of ~20 with connection failures randomly.
>> After ditching the Onboard GE (Marvell PHY) and using a PCIe NIC on
>> the Serv
On 11/29/12 16:45, lst_ho...@kwsoft.de wrote:
> Try with another NIC. We first had problems with our Bacula Server
> failing two clients out of ~20 with connection failures randomly.
> After ditching the Onboard GE (Marvell PHY) and using a PCIe NIC on
> the Server the problem went away.
I h
Zitat von b_...@mail.ru:
> On Nov 29, 2012, at 11:05 PM, Dan Langille wrote:
>
>>
>> On Nov 29, 2012, at 2:26 PM, b_...@mail.ru wrote:
>>
>>> Hello,
>>>
>>> I have a couple of hosts which backup through bacula. I have
>>> confronted with next situation, one host can't perform full
>>> backup
On Nov 29, 2012, at 11:05 PM, Dan Langille wrote:
>
> On Nov 29, 2012, at 2:26 PM, b_...@mail.ru wrote:
>
>> Hello,
>>
>> I have a couple of hosts which backup through bacula. I have confronted with
>> next situation, one host can't perform full backup, process of backup always
>> finished
On Nov 29, 2012, at 2:26 PM, b_...@mail.ru wrote:
> Hello,
>
> I have a couple of hosts which backup through bacula. I have confronted with
> next situation, one host can't perform full backup, process of backup always
> finished with this error:
> Error: bsock.c:389 Write error sending 262144
Hello,
I have a couple of hosts which backup through bacula. I have confronted with
next situation, one host can't perform full backup, process of backup always
finished with this error:
Error: bsock.c:389 Write error sending 262144 bytes to Storage daemon:IP
ADDRESS:9103: ERR=Broken pipe
Fatal
> On Tue, 10 Jan 2012 15:00:39 +1100, Alan Langley said:
>
> First error - Could be caused by items in this directory being deleted
> before the backup is finished?
>
> 10-Jan 02:33 preqf-fd JobId 94: Could not stat
> /var/flexshare/shares/transfers/ITEMS REQUIRING PERMANENT DELETION:
> E
UNCLASSIFIED
Hi,
I still haven't been able to resolve this fatal Error -
After 4 days of waiting for a backup to finish I get the following
errors - The first could be caused by a user being inpatient and
deleting a file before Bacula was finished with it - the second is a
problem report previou
. Juni 2009 13:13
To: Holikar, Sachin (ext); bacula-users
Subject: Re: [Bacula-users] Bacula Fatal Error
You also probably need to run mysqlrepair and then dbcheck
John
--
OpenSolaris 2009.06 is a cutting edge operating
You also probably need to run mysqlrepair and then dbcheck
John
--
OpenSolaris 2009.06 is a cutting edge operating system for enterprises
looking to deploy the next generation of Solaris that includes the latest
innovat
On Mon, Jun 8, 2009 at 7:03 AM, Holikar, Sachin
(ext) wrote:
>
>
> Hello,
>
> Before going ahead with this step, would like to understand how reducing
> the spool size will help?
>
If this is the machine with the storage I believe there is a chance
that the 8GB of spool is used 2 times. Once
: [Bacula-users] Bacula Fatal Error
> Yes, we will not disable spooling but you are asking to reduce the size to
> 4GB of what ??
>
> And I guess this is what you require,
>
Is this the same machine that has the storage? If so reduce the
Maximum Spool Size = 8G
Maximum Job Spoo
> Yes, we will not disable spooling but you are asking to reduce the size to
> 4GB of what ??
>
> And I guess this is what you require,
>
Is this the same machine that has the storage? If so reduce the
Maximum Spool Size = 8G
Maximum Job Spool Size = 8G
to
Maximum Spool Size = 4G
Maximum J
(0.00 sec)
Please let me know if you need anymore details,
Regards,
Sac
-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: Montag, 8. Juni 2009 12:33
To: Holikar, Sachin (ext)
Cc: James Harper; bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Bacula F
On 6/8/09, Holikar, Sachin (ext) wrote:
>
> Thanks Mr. Harper for the reply. Me too found that this happenes sometimes
> when the mysql file tbl_name MAX_ROWS value reaches its limits.
> We shall increase this limit and see if the error persists.
> One point you mentioned about spooling to the sam
> Thanks Mr. Harper for the reply. Me too found that this happenes
sometimes
> when the mysql file tbl_name MAX_ROWS value reaches its limits.
> We shall increase this limit and see if the error persists.
> One point you mentioned about spooling to the same volume. The details
of the
> spool are ,
e
as your database" ??
Thanks in adv.
Regards,
Sac
-Original Message-
From: James Harper [mailto:james.har...@bendigoit.com.au]
Sent: Montag, 8. Juni 2009 08:49
To: Holikar, Sachin (ext); bacula-users@lists.sourceforge.net
Subject: RE: [Bacula-users] Bacula Fatal Error
>
>
>
> Hello,
>
> We have been using Bacula Version: 2.2.7 for our backup needs. Today
morning
> we have received a fatal error and the backup could not be completed.
Strange
> enough the backup termination status is saying OK. If you have any
kind of
> hint to resolution of this error then kindly
Hello,
We have been using Bacula Version: 2.2.7 for our backup needs. Today morning
we have received a fatal error and the backup could not be completed. Strange
enough the backup termination status is saying OK. If you have any kind of hint
to resolution of this error then kindly suggest th
On 18 Feb 2006 at 17:40, Chris Wilson wrote:
> Good call Dan. I'd neglected to re-modify the mtx-changer script after
> upgrading. (In particular, my Exabyte 480 requires the tape to be placed
> "offline" before unloading it.)
>
> Thanks for the insight.
WOO HOO!
--
Dan Langille : Software
ROTECTED]
Sent: Saturday, February 18, 2006 3:35 PM
To: Chris Wilson
Cc: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Bacula fatal error
On 18 Feb 2006 at 11:22, Chris Wilson wrote:
> Hi,
>
> I received the following fatal error last night backing up my Bacula
> catalog. W
On 18 Feb 2006 at 11:22, Chris Wilson wrote:
> Hi,
>
> I received the following fatal error last night backing up my Bacula
> catalog. What's really interesting is the "Bad autochanger" error -- notice
> the slot number in the error (14) is different than the slot (24) specified
> in the precedi
Hi,
I received the following fatal error last night backing up my Bacula
catalog. What's really interesting is the "Bad autochanger" error -- notice
the slot number in the error (14) is different than the slot (24) specified
in the preceding "Issuing unload" command.
Notice in the first case it'
29 matches
Mail list logo
