Re: [Bacula-users] Baculum restoration issue

2019-09-26 Thread Marcin Haba
Hello Frédéric,

Yes, it is a bug. Thanks for reporting it.

This problem will be fixed in next release.

Best regards,
Marcin Haba (gani)

On Thu, 26 Sep 2019 at 10:19, Frédéric F.  wrote:
>
> Hello everyone,
>
> I think it's a bug.
> I have an issue with Bacula : I can't browse folders names containing the '€' 
> character.
>
> I can do it with the bconsole/restore command but impossible in the GUI 
> Interface
>
> Thank you for your help
>
> Best regards
>
> Frédéric.
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users



-- 
"Greater love hath no man than this, that a man lay down his life for
his friends." Jesus Christ

"Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie
za przyjaciół swoich." Jezus Chrystus


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] False "Intervention needed" flood

2019-09-26 Thread David Brodbeck
On Thu, Sep 26, 2019 at 10:02 AM Andrea Venturoli  wrote:

> On 2019-09-26 18:22, David Brodbeck wrote:
>
> > I've just been putting up with the error messages rather than deal with
> > the added maintenance of that approach. The extra alert emails can be
> > dealt with by filtering my incoming email.
>
> The only problem here is that you'll eventually miss *real*
> "intervention need"s.
> So if something *really* gets stuck, you won't know, because you
> filtered all these messages (or you didn't, but won't be possibly able
> to check all of them anyway).
>

That's true. I have the list of currently running jobs integrated into my
network monitoring display, which is on the wall just above my desk, so I
glance up there every so often to see if anything's stuck. Since most
backups run at night, any problems are going to wait until I come in in the
morning anyway.

-- 
David Brodbeck
System Administrator, Department of Mathematics
University of California, Santa Barbara
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] False "Intervention needed" flood

2019-09-26 Thread Andrea Venturoli

On 2019-09-26 18:22, David Brodbeck wrote:

I've just been putting up with the error messages rather than deal with 
the added maintenance of that approach. The extra alert emails can be 
dealt with by filtering my incoming email.


The only problem here is that you'll eventually miss *real* 
"intervention need"s.
So if something *really* gets stuck, you won't know, because you 
filtered all these messages (or you didn't, but won't be possibly able 
to check all of them anyway).


 bye
av.


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Syslog errors

2019-09-26 Thread David Brodbeck
I deliberately have this set up because I want to know if the director
crashes. Does mean I have to put up with one of those messages every ten
minutes though. ;)


On Wed, Sep 25, 2019 at 2:43 PM Chris Wilkinson 
wrote:

> Yes i think that is most likely the reason. The IP in question is a
> machine that runs a network monitor. I wasn't aware that it was sending
> packets to the Bacula ports and see no reason why it should since it isn't
> a port scanner. It just pings and checks a webserver on port 80 is up.
>
> However, I'll turn it off and see if the errors stop.
>
> Thanks to all for those pointers.
>
> Regards
> Chris Wilkinson
>
> On Wed, 25 Sep 2019, 10:22 p.m. David Brodbeck, 
> wrote:
>
>>
>>
>> On Wed, Sep 25, 2019 at 1:37 AM Radosław Korzeniewski <
>> rados...@korzeniewski.net> wrote:
>>
>>> Hello,
>>>
>>> pon., 23 wrz 2019 o 12:26 Chris Wilkinson 
>>> napisał(a):
>>>

 Sep 22 10:11:12 HOMESERVER bacula-fd: job.c:508 FD expecting Hello got bad 
 command from 192.168.1.30. Len=0.

 Something/someone at 192.168.1.30 is connecting to your (I see all your
>>> Bacula Components) server and is trying to chat with Bacula but is not
>>> using a bacula network protocol. So the errors.
>>>
>>> You have to verify what/who it is and disable it.
>>>
>>
>> If you're using a network monitoring system, like Observium or Big
>> Brother, that's a likely culprit.
>>
>> --
>> David Brodbeck
>> System Administrator, Department of Mathematics
>> University of California, Santa Barbara
>>
>> ___
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>>
>

-- 
David Brodbeck
System Administrator, Department of Mathematics
University of California, Santa Barbara
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] False "Intervention needed" flood

2019-09-26 Thread David Brodbeck
Part of the problem is it takes upwards of ten minutes for a job to fail
when a workstation isn't available -- which is entirely correct, since the
network connection has to time out. However, the SD reservation is made
*before* it tries to contact the FD, so I end up with resource starvation
where jobs that are waiting to time out tie up resources that could be used
by other jobs. I'm guessing the assumption is that clients will always be
available, but the SD might be maxed out, so the code assumes it's more
efficient not to contact a client until the director knows it has the
resources to actually run the job.

One option would be to stagger the start times of my jobs so only the
maximum the SD can handle get launched in any given 10 minute window, but
that adds a lot of complexity to my configuration, since I currently can
just allow JobDefs to pull in the schedule for all clients. I'd have to
define start times individually, and maintain those in order to keep them
balanced as I add/remove clients. Adding enough disks for the worst case
isn't going to be possible. (I'm assuming one client per spindle is optimal
for disk arrays -- maybe that's too conservative?)

I've just been putting up with the error messages rather than deal with the
added maintenance of that approach. The extra alert emails can be dealt
with by filtering my incoming email.


On Thu, Sep 26, 2019 at 1:28 AM Kern Sibbald  wrote:

> Hello,
>
> Bacula does already attempt to acquire the needed devices in the SD and
> then backs them out if all the needed resources cannot be obtained.
> This works quite nicely.   Consequently, while the job is waiting the
> resources are released in the SD.
>
> The problem occurs because the SD realizes that the resources are not
> available, so it will wait a short period of time trying again to
> acquire the resources, which is what one wants for virtually all jobs.
> When it cannot acquire the resources the SD will fail the job.  The
> problem occurs because the user is over committing the SD resources.
> The solution is to get more drives or modify how you run jobs.
>
> From what I understand in this case is that the user has a large number
> of jobs that regularly fail and thus the user explicitly over commits
> the resources.  The consequent is that Bacula works as it should but the
> user gets lots of messages about the SD not being able to get resources.
>
> Bacula was designed in a way were it expects to have the needed
> resources available (i.e. the configuration should be optimized for the
> available resources).  It also handles the case where you over load the
> SD (too many jobs for available resources), but in that case it will
> warn you, which is exactly what 99% of all users want.
>
> One possible solution would be to add a new directive that suppresses
> the reservation failure message.  However there is very likely a better
> solution with the existing Bacula, I just do not know what it is at this
> time.  This is the first time in 19 years that this problem has come up,
> so before changing anything in the code, it has to be very clearly
> understood, which is not the case (at least for me).
>
> Another solution is for the user to modify the source code and remove
> the warning message.
>
> Best regards,
> Kern
>
> On 9/25/19 10:50 AM, Andrea Venturoli wrote:
> > On 2019-09-25 10:19, Radosław Korzeniewski wrote:
> >> Hello,
> >>
> >> sob., 21 wrz 2019 o 00:52 David Brodbeck  >> > napisał(a):
> >>
> >> I think this is a somewhat unfortunate design decision, to be
> >> honest. (...)
> >>
> >>
> >> So what should be the best design in this case which should solve the
> >> problem?
> >
> > I'm not so into the code to tell for sure.
> > Maybe rescheduling should release the SD once the job first fails and
> > reserve again when it starts the next time?
> >
> >  bye & Thanks
> > av.
> >
>
>

-- 
David Brodbeck
System Administrator, Department of Mathematics
University of California, Santa Barbara
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Problem for Restore after bscan

2019-09-26 Thread Martin Simmons
I think restore after bscan can be very slow.  How long did you wait?

__Martin


> On Wed, 25 Sep 2019 13:21:38 -0400, Jose Alberto said:
> 
> Hi.
> 
> I have Bacula 9 on Debian with Postgres.
> 
> The problem, for error, the sysadmin delete (prune and purge), 6 job
> (example jobid  10,20,30,40,50 and 60) but have jobid 70 (no delete)   on
> volumen. (lto5).
> 
> The jobid 70restore all fine.
> 
> For solve:  i delete volume on pool,after  exe bscan  volumen.
> 
> 
> I view now  the jobs  with other numbers ID.
> 
> but but but but.   Restore good is number 100 (before 70).But the
> restore 101,102,104,104,105,106) (before 10,20,30,40,50,60).no run.
> 
> Ready to read from volume,   It stays there in an endless cycle.
> 
> After having removed the volume and running bscan, should anything else be
> done?
> 
> Thanks
> 
> PD: bextrack  all fine.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> -- 
> #
> #   Sistema Operativo: Debian  #
> #Caracas, Venezuela  #
> #
> 


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] False "Intervention needed" flood

2019-09-26 Thread Gary R. Schmidt

On 26/09/2019 18:37, Kern Sibbald wrote:

See below ...

On 9/25/19 7:38 PM, Andrea Venturoli wrote:

[SNIP]


Yes: as I said it's not a big problem, just an annoyance.
*Not* solving the resource contention problem, but just avoiding to
nag about it would probably be enough (at least to me).


Bacula is not capable of solving resource contentions itself other than
trying again.


Would it be very difficult to change Bacula so that rather than trying 
every five (or whatever) minutes it did an exponential back-off?


Such as, after the first failure try again in five minutes, then again 
in fifteen, then in sixty minutes, then two hours, four, eight, sixteen, 
too many retries I am giving up?


I don't think this change would be simple, but I think it should be 
possible.


Cheers,
Garyb-)


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] False "Intervention needed" flood

2019-09-26 Thread Kern Sibbald
See below ...

On 9/25/19 7:38 PM, Andrea Venturoli wrote:
> On 2019-09-25 18:42, David Brodbeck wrote:
>> I'm not sure how Max Full Interval solves the problem. I have used it
>> (before we switched to virtual full) but it doesn't really pertain to
>> resource contention. Maybe I didn't explain the problem very well.
>
> I agree.
> I'm *also* using Max Full Interval & co, but I fail to see how this
> relates to the problem we are discussing.
>
> Could you elaborate on this?

Aside from waiting for the next nightly backup due to an off-line
machine a major problem with having unavailable clients is that a Full
could be skipped by having the job failed.  Max Full Interval resolves
this issue.  It does not however resolve the issue that if the machine
is always off during the backup window, the machine might never be
backed up, which is where rescheduling can help.
>
>
>
>
>> It's a minor issue, so I'm not too concerned about it.
>
> Yes: as I said it's not a big problem, just an annoyance.
> *Not* solving the resource contention problem, but just avoiding to
> nag about it would probably be enough (at least to me).

Bacula is not capable of solving resource contentions itself other than
trying again.
>
>
>
>  bye & Thanks
> av.
>



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] False "Intervention needed" flood

2019-09-26 Thread Kern Sibbald
Hello,

Bacula does already attempt to acquire the needed devices in the SD and
then backs them out if all the needed resources cannot be obtained. 
This works quite nicely.   Consequently, while the job is waiting the
resources are released in the SD. 

The problem occurs because the SD realizes that the resources are not
available, so it will wait a short period of time trying again to
acquire the resources, which is what one wants for virtually all jobs. 
When it cannot acquire the resources the SD will fail the job.  The
problem occurs because the user is over committing the SD resources. 
The solution is to get more drives or modify how you run jobs.

From what I understand in this case is that the user has a large number
of jobs that regularly fail and thus the user explicitly over commits
the resources.  The consequent is that Bacula works as it should but the
user gets lots of messages about the SD not being able to get resources.

Bacula was designed in a way were it expects to have the needed
resources available (i.e. the configuration should be optimized for the
available resources).  It also handles the case where you over load the
SD (too many jobs for available resources), but in that case it will
warn you, which is exactly what 99% of all users want.

One possible solution would be to add a new directive that suppresses
the reservation failure message.  However there is very likely a better
solution with the existing Bacula, I just do not know what it is at this
time.  This is the first time in 19 years that this problem has come up,
so before changing anything in the code, it has to be very clearly
understood, which is not the case (at least for me).

Another solution is for the user to modify the source code and remove
the warning message.

Best regards,
Kern

On 9/25/19 10:50 AM, Andrea Venturoli wrote:
> On 2019-09-25 10:19, Radosław Korzeniewski wrote:
>> Hello,
>>
>> sob., 21 wrz 2019 o 00:52 David Brodbeck > > napisał(a):
>>
>>     I think this is a somewhat unfortunate design decision, to be
>>     honest. (...)
>>
>>
>> So what should be the best design in this case which should solve the
>> problem?
>
> I'm not so into the code to tell for sure.
> Maybe rescheduling should release the SD once the job first fails and
> reserve again when it starts the next time?
>
>  bye & Thanks
> av.
>



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


[Bacula-users] Baculum restoration issue

2019-09-26 Thread Frédéric F .
Hello everyone,

I think it's a bug.
I have an issue with Bacula : I can't browse folders names containing the
'€' character.

I can do it with the bconsole/restore command but impossible in the GUI
Interface

Thank you for your help

Best regards

Frédéric.
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users