In the message dated: Thu, 29 Mar 2007 11:09:39 BST,
The pithy ruminations from Alan Brown on
were:
=> On Wed, 28 Mar 2007, Erich Prinz wrote:
=>
=> > Others have experienced issues relating to antivirus scan engines
=> > interfering with successful backups. Perhaps it is interfering with
=> >
Hi,
On 3/29/2007 1:28 PM, Brian Debelius wrote:
> For what its worth, I use Nod32 (www.eset.com), I have not had a problem
> with it. Its fast, and has a small footprint. Download a trial, and
> see what happens.
Right, nice to remind me :-)
I also have tried NOD32 and found no more errors w
On Thu, 29 Mar 2007, Alan Brown wrote:
>> The others have tested by disabling AV then running a test job.
>
> It would be nice if there was a way of telling AV software not to inspect
> files being opened by Bacula
Update:
F-secure helpdesk inform me that if an executable is exempted from
f
For what its worth, I use Nod32 (www.eset.com), I have not had a problem
with it. Its fast, and has a small footprint. Download a trial, and
see what happens.
brian-
Alan Brown wrote:
> On Wed, 28 Mar 2007, Erich Prinz wrote:
>
>
>> Others have experienced issues relating to antivirus sca
On Wed, 28 Mar 2007, Erich Prinz wrote:
> Others have experienced issues relating to antivirus scan engines
> interfering with successful backups. Perhaps it is interfering with
> the communications between the daemons (different machines from what
> I gather.)
>
> The others have tested by disabl
Good call, I have not tried that yet. I'll give that a shot then post
back to the list.
Jason
Erich Prinz wrote:
>
> Others have experienced issues relating to antivirus scan engines
> interfering with successful backups. Perhaps it is interfering with
> the communications between the daemons
Others have experienced issues relating to antivirus scan engines
interfering with successful backups. Perhaps it is interfering with
the communications between the daemons (different machines from what
I gather.)
The others have tested by disabling AV then running a test job.
Erich
On Ma
Anyone else in the list have any idea what might be causing the problem
I'm having? I'm totally at a loss for what to do other than setup a
local director on that server. The backup works fine if the director is
loaded locally.
[EMAIL PROTECTED] wrote:
> I already read about that and the "Heart
[EMAIL PROTECTED] schrieb:
> I already read about that and the "Heartbeat Interval" has already been
> setup and changed to 90 seconds. I have Heartbeat setup on both the SD and
> the FD of this server. I actually had to setup the Heartbeat to handle a
> different problem with the backup. The Heart
I already read about that and the "Heartbeat Interval" has already been
setup and changed to 90 seconds. I have Heartbeat setup on both the SD and
the FD of this server. I actually had to setup the Heartbeat to handle a
different problem with the backup. The Heartbeat solved that problem but
then c
On Monday 26 March 2007 23:55, Jason King wrote:
> Ok, I've got the debug output of the storage daemon now:
>
> I have the system setup to spool the data to the drive then write to the
> media. Everything looks fine until after the system starts to despool
> everything to tape. Here are the debu
Ok, I've got the debug output of the storage daemon now:
I have the system setup to spool the data to the drive then write to the
media. Everything looks fine until after the system starts to despool
everything to tape. Here are the debug messages from despool on:
dctn-sd: ../../stored/spool
On Monday 26 March 2007 21:54, Brian Debelius wrote:
> Kern Sibbald wrote:
> > On Monday 26 March 2007 21:38, Jason King wrote:
> >
> >> The problem I have is that this particular SD is running on Windows so
> >> there is no STOUT. Where do I look from there? I can set the -d option
> >> withi
Kern Sibbald wrote:
> On Monday 26 March 2007 21:38, Jason King wrote:
>
>> The problem I have is that this particular SD is running on Windows so
>> there is no STOUT. Where do I look from there? I can set the -d option
>> within the services options but I just don't know where to look for th
On Monday 26 March 2007 21:38, Jason King wrote:
> The problem I have is that this particular SD is running on Windows so
> there is no STOUT. Where do I look from there? I can set the -d option
> within the services options but I just don't know where to look for the
> debug information.
Well
The problem I have is that this particular SD is running on Windows so
there is no STOUT. Where do I look from there? I can set the -d option
within the services options but I just don't know where to look for the
debug information.
jason
Kern Sibbald wrote:
> On Monday 26 March 2007 21:20, Ja
On Monday 26 March 2007 21:20, Jason King wrote:
> You mean in the console?
No.
> I set my debug level to 100 and nothing
> different has come through to my console. Where can I get the debug
> information?
Unless you redirect the output, it will appear in the shell from which you
started
You mean in the console? I set my debug level to 100 and nothing
different has come through to my console. Where can I get the debug
information?
Kern Sibbald wrote:
> On Monday 26 March 2007 19:53, Jason King wrote:
>
>> I'm sorry, I said that wrong. I tried to say the email I got showed the
On Monday 26 March 2007 19:53, Jason King wrote:
> I'm sorry, I said that wrong. I tried to say the email I got showed the
> director sees an errored backup...but the file daemon puts a successful
> backup in its own history logs. I'll try using debugging to see if that
> gives me what I need.
No, I didn't know there was such a thing.
Jaime Ventura wrote:
> Hello Jason,
> Are you using the MAIL ON SUCCESS feature?
>
>Jaime
>
> Jason King wrote:
>> I'm sorry, I said that wrong. I tried to say the email I got showed
>> the director sees an errored backup...but the file daemon puts a
Hello Jason,
Are you using the MAIL ON SUCCESS feature?
Jaime
Jason King wrote:
> I'm sorry, I said that wrong. I tried to say the email I got showed the
> director sees an errored backup...but the file daemon puts a successful
> backup in its own history logs. I'll try using debugging to s
I'm sorry, I said that wrong. I tried to say the email I got showed the
director sees an errored backup...but the file daemon puts a successful
backup in its own history logs. I'll try using debugging to see if that
gives me what I need. Where can I find the debug output?
Kern Sibbald wrote:
>
On Monday 26 March 2007 18:10, Jason King wrote:
> Also, the email I got showed the director does see a successful
> backup...
That seems unlikely because the output you showed below indicates that the job
failed.
> but like I said, the file daemon says the backup WAS successful
> when I do
Also, the email I got showed the director does see a successful
backup...but like I said, the file daemon says the backup WAS successful
when I do a "status client" from the console of the director.
Jason
Kern Sibbald wrote:
> Your email title is a bit misleading as this was not successful back
No, it did not die or crash. The SD is still running. I can check it
with the director and it's still running just fine.
Jason
Kern Sibbald wrote:
> Your email title is a bit misleading as this was not successful backup.
>
> It looks like the SD might have died ... i.e. probably crashed.
>
>
>
>
Your email title is a bit misleading as this was not successful backup.
It looks like the SD might have died ... i.e. probably crashed.
On Monday 26 March 2007 17:10, Jason King wrote:
> According to my bacula database, my backup of one of my servers ended in
> an error but when I do a status
According to my bacula database, my backup of one of my servers ended in
an error but when I do a status on the servers file daemon, it shows a
successful backup, here is the email I received:
26-Mar 09:01 maint-dir: Start Backup JobId 353, Job=dctn.2007-03-26_09.01.49
26-Mar 09:01 dctn-sd: Wrot
27 matches
Mail list logo
