AW: [bareos-users] Storage Daemon stops writing without any visible reason

[Christian Garling]

Hi,

I updated Bareos to version 20.0.1 and made some changes to the VMs (specially 
director and storage daemon) right now and it looks more stable now.

But I still receive these messages nearly every minute while the backups are 
running:

17-Mar 05:35 bareos-dir JobId 0: Fatal error: TwoWayAuthenticate failed, 
because job was canceled.
17-Mar 05:35 bareos-dir JobId 0: Fatal error: Director unable to authenticate 
with Storage daemon at "10.20.2.2:9103". Possible causes:
Passwords or names not the same or
TLS negotiation problem or
Maximum Concurrent Jobs exceeded on the SD or
SD networking messed up (restart daemon).

I ran the storage daemon in the debug mode and found these messages:

bareos-sd (100): lib/bsock.cc:84-0 Construct BareosSocket
bareos-sd (200): lib/bsock.cc:745-0 Identified from Bareos handshake: 
bareos-dir-R_DIRECTOR version not recognized
bareos-sd (200): lib/try_tls_handshake_as_a_server.cc:61-0 TlsPolicy for 
bareos-dir is 0

It looks like the director first tries to connect with TLS but its disabled in 
all configs. Did I miss an option or how can I avoid these?


Mit freundlichen Grüßen / best regards

Christian Garling
Operating

Pix Software GmbH
An der Beek 255, 41372 Niederkrüchten, Germany

Tel.: +49 (0)2163 / 98999 71
Fax: +49 (0)2163 / 953031
E-Mail: 
christian.garl...@pixsoftware.de
https://www.pixsoftware.de

[linkedin_social_button][xing_social_button]

Geschäftsführer: Arne Schirmacher, David-Andreas Bergens
Eingetragen beim Amtsgericht Mönchengladbach, HRB 16527
USt-IdNr. DE153180010

[cid:image003.png@01D71B43.0A325AF0]

Von: bareos-users@googlegroups.com  Im Auftrag 
von Christian Garling
Gesendet: Mittwoch, 24. Februar 2021 16:34
An: bareos-users@googlegroups.com
Betreff: AW: [bareos-users] Storage Daemon stops writing without any visible 
reason

Hi Frank,

thank you for the quick response. I do not know, if we use data-spooling. I did 
not set any options fort hat explicit.
How can I check that?


Mit freundlichen Grüßen / best regards
Christian Garling
Operating
Pix Software GmbH
An der Beek 255, 41372 Niederkrüchten, Germany
Tel.: +49 (0)2163 / 98999 71
Fax: +49 (0)2163 / 953031
E-Mail: 
christian.garl...@pixsoftware.de
https://www.pixsoftware.de
[linkedin_social_button][xing_social_button]
Geschäftsführer: Arne Schirmacher, David-Andreas Bergens
Eingetragen beim Amtsgericht Mönchengladbach, HRB 16527
USt-IdNr. DE153180010

[cid:image003.png@01D71B43.0A325AF0]

Von: bareos-users@googlegroups.com 
mailto:bareos-users@googlegroups.com>> Im 
Auftrag von Frank Ueberschar
Gesendet: Dienstag, 23. Februar 2021 14:48
An: bareos-users@googlegroups.com
Betreff: Re: [bareos-users] Storage Daemon stops writing without any visible 
reason


If you are using data-spooling on one or more jobs you may have hit a bug that 
we just fixed in the upcoming bareos-20.0.1.

Best, Frank


--

Mit freundlichen Grüßen



 Frank Ueberschar  
frank.uebersc...@bareos.com

 Bareos GmbH & Co. KG  Phone: +49 221 63 06 93-88

 http://www.bareos.com Fax:   +49 221 63 06 93-10



 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646

 Geschäftsführer: S. Dühr, M. Außendorf, J. Steffens, P. Storz

Am 23.02.21 um 08:49 schrieb Christian Garling:
Good morning,

we are experiencing the following problem with our Bareos backup.

We are backing up round about 280 systems (most of them Debian 10 or 9 and some 
Windows servers). The greatest part of them are running version 20. The 
director and the storage daemon also is on version 20. The director and the 
clients are located in a datacenter together, the storage daemon is in antother 
datacenter, connected with a metro LAN connection. The Heartbeat Interval is 
set to 60 on all systems (director, storage, filedaemon). The 
tcp_keepalive_time is set to 900.

Sometimes the backup works good for several days, then suddenly it stops 
working. The jobs are marked as running, but no data is written on the storage 
daemon side. If I restart the storage daemon, sometimes the backup goes on 
until its finished, sometimes all unfinished jobs abort.

In the log file I found:

23-Feb 08:01 bareos-dir JobId 0: Fatal error: Director unable to authenticate 
with Storage daemon at "10.20.2.2:9103". Possible causes:
Passwords or names not the same or
TLS negotiation problem or
Maximum Concurrent Jobs exceeded on the SD or
SD networking messed up (restart daemon).
23-Feb 08:01 bareos-dir JobId 7897: Fatal error: Director's comm line to SD 
dropped.
23-Feb 

[bareos-users] Keep a deleted file in backup for a certain time

[F S]

Hi,

I want to set up a backup of a fileserver with the following parameters:
- we need to keep files in the backup for at least 30 days but not longer
- incremental Backups are created every night every day
- every other Saturday a virtual full backup is created
- we have two full backup volumes which are switched every other Saturday 
when the virtual full backup is running
- the incremental volumes are rotated as well and will be overwritten after 
the virtual full

This is working fine except one issue.
When a file is created e.g. on Monday it is backup in a incremental backup. 
When it is deleted on Thursday it will not be in the virtual full backup 
next Saturday, because of accurate = yes setting.
So the file will not be in the backup for at least 30 days. If I set 
accurate = no it never is removed from the full backup even after months.
Is there some setting I'm missing? Or do I have to keep the incremental 
backup for at least 30 days which will lead to much more needed 
volumes/disk space.

Thanks and best regards
Fabian

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/e4fe01ce-c13d-4dfa-b1aa-e35492407da7n%40googlegroups.com.

Re: [bareos-users] Compatibility question

[Spadajspadaj]

Of course it's always best to have the whole environment with coherent 
current version but it's usually quite OK to have director slightly 
"ahead" of the clients. It's the other way around that easily causes 
problems - if you have FD's newer than director, you might run into 
problems.


On 17.03.2021 08:06, 'Frank Cherry' via bareos-users wrote:


Hi there,
On my backup system I've run Bareos v20 (Director and Storage Daemin) 
but I have a system with CentOS 6, there is running Bareos with V19 
(File Director). I have tested it successful.

Are there any pages which shows the version compatibility?
As I read between the lines in 
https://docs.bareos.org/Appendix/BackwardCompatibility.html 

the backward compatibility to a lower version of a FD should be ever 
possible - right?


Thanks and all the best,
Frank
--
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+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/481485cc-9dd3-4f13-927c-53bdcd35984en%40googlegroups.com 
.


--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/72de9c45-2944-ede4-74d1-31d8cd94bb9a%40gmail.com.

Re: [bareos-users] Backup data to AWS S3 bucket using the BareOS utility

[Spadajspadaj]

Yes, there is a plugin for storage daemon to store data in S3. See the docs.

On 16.03.2021 17:02, Kaushal Shriyan wrote:

Hi,

Is there a way to push the backup data to the AWS S3 bucket using the 
BareOS utility? For example, if I backup both configurations and data 
directory of GitLab SCM services using BareOS utility, Can it be 
pushed to AWS S3 bucket instead of storing it locally in the BareOS 
server.


Please advise. Thanks in advance.

Best Regards,

Kaushal
--
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+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/655c1c45-4a5e-47d3-9895-7c87f47a0af6n%40googlegroups.com 
.


--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/0e7df0d5-8749-4c63-f0a3-735d7ec7697e%40gmail.com.

[bareos-users] Compatibility question

['Frank Cherry' via bareos-users]

Hi there,
On my backup system I've run Bareos v20 (Director and Storage Daemin) but I 
have a system with CentOS 6, there is running Bareos with V19 (File 
Director). I have tested it successful. 
Are there any pages which shows the version compatibility?
As I read between the lines in 
https://docs.bareos.org/Appendix/BackwardCompatibility.html
the backward compatibility to a lower version of a FD should be ever 
possible - right?

Thanks and all the best,
Frank

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/481485cc-9dd3-4f13-927c-53bdcd35984en%40googlegroups.com.