Discussion:
[bareos-users] Is FD Connect Timeout the correct approach
Raymond Norton
2018-11-13 14:47:41 UTC
Permalink
My new Bareos setup is working fine but jobs stack up when a client PC is down. I would like for Bareos to try 5 minutes or less and move on to the next job. I added FD Connect Timeout 1 to the dir config but it did not seem to change things.

Running 18.2 for the server and 17.2 for a client (linux)
--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+***@googlegroups.com.
To post to this group, send email to bareos-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Raymond Norton
2018-11-15 15:28:06 UTC
Permalink
Post by Raymond Norton
My new Bareos setup is working fine but jobs stack up when a client PC is down. I would like for Bareos to try 5 minutes or less and move on to the next job. I added FD Connect Timeout 1 to the dir config but it did not seem to change things.
Running 18.2 for the server and 17.2 for a client (linux)
I still have not figured out how to force the director to cancel a job when it cannot connect to a client and move on to the next job. My .conf file indicates it should run up to 10 concurrent jobs.

Director { # define myself
Name = bareos-dir
QueryFile = "/usr/lib/bareos/scripts/query.sql"
Maximum Concurrent Jobs = 10
Password = "password" # Console password
Messages = Daemon
Auditing = yes
FD Connect Timeout = 1

I added the FD Connect timeout but that does not work either.

Ideas?
--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+***@googlegroups.com.
To post to this group, send email to bareos-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Stefan Klatt
2018-11-16 00:26:09 UTC
Permalink
Hi Raymond,

what about the other way?
A job which try to reach the client and if possible it starts the backup
job. If not it logs the event.

Greetings

Stefan Klatt
Post by Raymond Norton
Post by Raymond Norton
My new Bareos setup is working fine but jobs stack up when a client PC is down. I would like for Bareos to try 5 minutes or less and move on to the next job. I added FD Connect Timeout 1 to the dir config but it did not seem to change things.
Running 18.2 for the server and 17.2 for a client (linux)
I still have not figured out how to force the director to cancel a job when it cannot connect to a client and move on to the next job. My .conf file indicates it should run up to 10 concurrent jobs.
Director { # define myself
Name = bareos-dir
QueryFile = "/usr/lib/bareos/scripts/query.sql"
Maximum Concurrent Jobs = 10
Password = "password" # Console password
Messages = Daemon
Auditing = yes
FD Connect Timeout = 1
I added the FD Connect timeout but that does not work either.
Ideas?
--
*CaC, Computer and Communication*
Inhaber Stefan Klatt
End-2-End Senior Security Consultant
CISSP / CISM / ISO27001 Lead Implementer / TOGAF9 /
VdS-anerkannter Berater fÃŒr Cyber-Security
Badges: https://www.youracclaim.com/users/stefan-klatt
Triftstrasse 9
60528 Frankfurt
Germany
USt-IdNr.: DE260461592

Tel.: +49-(0)172-6807809
Tel.: +49-(0)69-67808-900
Fax: +49-(0)69-67808-837
Email: ***@cac-netzwerk.de
Profil: http://www.cac-netzwerk.de/profil
--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+***@googlegroups.com.
To post to this group, send email to bareos-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Raymond Norton
2018-11-16 14:07:43 UTC
Permalink
Originally, I attempted that and it would be my preference but the director would not connect to the client. I am assuming I was missing something on the client machine that the director needed. I will need to dig into it more to find out what was missing.
Post by Stefan Klatt
Hi Raymond,
what about the other way?
A job which try to reach the client and if possible it starts the
backup job. If not it logs the event.
Greetings
Stefan Klatt
Am 15.11.2018 um 16:28 schrieb Raymond
My new Bareos setup is working fine but jobs stack up when a client PC is down. I would like for Bareos to try 5 minutes or less and move on to the next job. I added FD Connect Timeout 1 to the dir config but it did not seem to change things.
Running 18.2 for the server and 17.2 for a client (linux)
I still have not figured out how to force the director to cancel a job when it cannot connect to a client and move on to the next job. My .conf file indicates it should run up to 10 concurrent jobs.
Director { # define myself
Name = bareos-dir
QueryFile = "/usr/lib/bareos/scripts/query.sql"
Maximum Concurrent Jobs = 10
Password = "password" # Console password
Messages = Daemon
Auditing = yes
FD Connect Timeout = 1
I added the FD Connect timeout but that does not work either.
Ideas?
--
CaC, Computer and Communication
Inhaber Stefan Klatt
End-2-End Senior Security Consultant
CISSP / CISM / ISO27001 Lead Implementer / TOGAF9 /
VdS-anerkannter Berater fÃŒr Cyber-Security
Badges: https://www.youracclaim.com/users/stefan-klatt
Triftstrasse 9
60528 Frankfurt
Germany
USt-IdNr.: DE260461592
Tel.: +49-(0)172-6807809
Tel.: +49-(0)69-67808-900
Fax: +49-(0)69-67808-837
Profil: http://www.cac-netzwerk.de/profil
--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+***@googlegroups.com.
To post to this group, send email to bareos-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Raymond Norton
2018-11-15 21:01:28 UTC
Permalink
Post by Raymond Norton
My new Bareos setup is working fine but jobs stack up when a client PC is down. I would like for Bareos to try 5 minutes or less and move on to the next job. I added FD Connect Timeout 1 to the dir config but it did not seem to change things.
Running 18.2 for the server and 17.2 for a client (linux)
I got things to work properly (err out and move on) by adding the following to the client .conf files in /etc/bareos/bareos-dir.d/client :

Heartbeat interval = 60
Passive = yes
Enabled = yes

Not sure if it is the best answer but it works for me
--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+***@googlegroups.com.
To post to this group, send email to bareos-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Albert Marques
2018-11-16 08:32:47 UTC
Permalink
Post by Raymond Norton
Post by Raymond Norton
My new Bareos setup is working fine but jobs stack up when a client PC is down. I would like for Bareos to try 5 minutes or less and move on to the next job. I added FD Connect Timeout 1 to the dir config but it did not seem to change things.
Running 18.2 for the server and 17.2 for a client (linux)
Heartbeat interval = 60
Passive = yes
Enabled = yes
Not sure if it is the best answer but it works for me
Hello Raymond,

The setting 'Passive = yes' worked perfectly.

Thanks a lot.

Greetings
--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+***@googlegroups.com.
To post to this group, send email to bareos-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Loading...