Project

General

Profile

Scénario #35704

Scribe 2.8 - erreur de sauvegarde incr. et diff. après migration scribe 2.4 => scribe 2.8.1

Added by Thierry ARBEZ-CARME 4 months ago. Updated 28 days ago.

Status:
Terminé (Sprint)
Priority:
Normal
Assigned To:
Category:
-
Start date:
12/14/2023
Due date:
01/01/2024
% Done:

100%

Story points:
3.0
Velocity based estimate:
Release:
Release relationship:
Auto

Description

Réf: autres personnes ayant le même problème:

Bonjour,

Sur un scribe 2.8 fraichement migré, la sauvegarde ne marche qu’en full, pas
en incrémentale ni en différentiel.
La sauvegarde 'catalogue' qui se fait vers 4H00 du matin se passe bien.

J’ai réinitialisé bareos (bareosregen.sh), mais rien à faire…

un extrait du log:

16-oct. 18:47 scribe-sd JobId 6: Labeled new Volume "scribe-dir-diff-0050" on
device "FileStorage" (/mnt/sauvegardes).
16-oct. 18:47 scribe-sd JobId 6: Wrote label to prelabeled Volume
"scribe-dir-diff-0050" on device "FileStorage" (/mnt/sauvegardes)
16-oct. 18:48 scribe-dir JobId 6: Fatal error: TLS read/write failure.:
ERR=error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad*
record mac*
16-oct. 18:48 scribe-dir JobId 6: Fatal error: Network error with FD during
Backup: ERR=Aucune donnée disponible
16-oct. 18:48 scribe-dir JobId 6: Fatal error: Director's comm line to SD
dropped.
16-oct. 18:48 scribe-dir JobId 6: Fatal error: No Job status returned from FD.
16-oct. 18:48 scribe-dir JobId 6: Error: Bareos scribe-dir 20.0.0 (16Dec20):
Build OS: Ubuntu 20.04.1 LTS
JobId: 6

Cordialement,

b-dir.log View (51.1 KB) Klaas TJEBBES, 01/09/2024 09:47 AM

b-fd.log View (6.51 KB) Klaas TJEBBES, 01/09/2024 09:47 AM

b-sd.log View (33.1 KB) Klaas TJEBBES, 01/09/2024 09:47 AM


Related issues

Related to Scribe - Scénario #33960: Bareos sur scribe 2.8.1 (suite upgrade) Terminé (Sprint) 03/28/2022 04/15/2022
Related to Distribution EOLE - Scénario #34220: Bareos : vérifier l'intérêt du paramètre "Heartbeat Interval" Terminé (Sprint) 06/07/2022 06/24/2022

History

#1 Updated by Klaas TJEBBES 3 months ago

#2 Updated by Klaas TJEBBES 3 months ago

Question posée sur la liste Bareos :
https://groups.google.com/g/bareos-users/c/pF_CfvoJF5U

#3 Updated by Klaas TJEBBES 3 months ago

#4 Updated by Klaas TJEBBES 3 months ago

On rencontre les erreurs suivantes (voir fichier de log ci-joint) :
ERR=error:1408F119:SSL
ERR=error:14094438:SSL
ERR=error:1409E10F:SSL

#6 Updated by Klaas TJEBBES 3 months ago

Ceci semble résoudre le problème, en attente de confirmation au 22.01.2024.

* modifier /etc/bareos/bareos-dir.conf et commenter "Heartbeat Interval = 10" (environ ligne 12)
* modifier /etc/bareos/bareos-fd.conf et commenter "Heartbeat Interval = 10" (environ ligne 19)
* redémarrer les services :
   ** systemctl restart bareos-dir.service
   ** systemctl restart bareos-fd.service

#7 Updated by Klaas TJEBBES 2 months ago

bruno.friedmann [à] bareos.com :

While in most majority of cases you don't need heartbeat, it may necessary
when some firewall drop idled connection after a certain time. This may occur
when the FD is collecting files and didn't send anything to the SD.

I highly recommend to set client to passive mode (will be our default in next 
24 version).

https://docs.bareos.org/TasksAndConcepts/NetworkSetup.html#passive-clients

The normal way of initializing the data channel (the channel where the backup data itself is transported) is done by the Bareos File Daemon (client) that connects to the Bareos Storage Daemon.

In many setups, this can cause problems, as this means that:

  • The client must be able to resolve the name of the Bareos Storage Daemon (often not true, you have to do tricks with the hosts file)
  • The client must be allowed to create a new connection.
  • The client must be able to connect to the Bareos Storage Daemon over the network (often difficult over NAT or Firewall)

By using Passive Client, the initialization of the data channel is reversed, so that the storage daemon connects to the Bareos File Daemon. This solves almost every problem created by firewalls, NAT-gateways and resolving issues, as

  • The Bareos Storage Daemon initiates the connection, and thus can pass through the same or similar firewall rules that the director already has to access the Bareos File Daemon.
  • The client never initiates any connection, thus can be completely firewalled.
  • The client never needs any name resolution and is totally independent from any resolving issues.

To use this feature, just configure Passive (Dir->Client)=yes in the client definition of the Bareos Director:

Enable passive mode in bareos-dir.d/client/myself.conf :

Client {
   Name = client1-fd
   Password = "secretpassword" 
   Passive = yes
   [...]
}

#8 Updated by Joël Cuissinat 2 months ago

  • Tracker changed from Demande to Scénario
  • Due date set to 01/01/2024
  • Assigned To set to Klaas TJEBBES
  • Target version set to Carnet MENSR
  • Release set to EOLE 2.8.0
  • Story points set to 3.0

#9 Updated by Joël Cuissinat 28 days ago

  • Related to Scénario #34220: Bareos : vérifier l'intérêt du paramètre "Heartbeat Interval" added

#10 Updated by Joël Cuissinat 28 days ago

  • Status changed from Nouveau to Terminé (Sprint)
  • Target version changed from Carnet MENSR to Livraison MENSR 31/12/2023
  • % Done changed from 0 to 100

L'étude et les différents échanges montrent que la suppression de l'option Heartbeat Interval résout le problème dans la plupart des cas.
Cette option est d'ailleurs supprimée sur EOLE ≥ 2.9.0.
À cette époque, nous avions fait le choix de ne pas modifier les configurations 2.8 : #34220#note-2
Si d'autres problèmes sont remontés, il faudra penser à proposer les patches proposés dans : #34293

Also available in: Atom PDF