Hi Bruno,
no, I haven't updated my Debian system.
Yes, my Bareos instance is include backed up.
But I also create a daily dump of all my databases.
This dump is stored separately on the backup medium.
Regards, Stefan

Am Montag, dem 10.11.2025 um 00:50 -0800 schrieb Bruno Friedmann
(bruno-at-bareos):
> Hi Stefan, I'm glad you finally been able to fix it.
> I was not able on my side to reproduce the case with Debian 13.
> 
> Just a side question, was that system upgraded for example from
> Debian 12 to 13 ?
> Maybe during that process some symlink would have been introduced ?
> 
> By the way, I just want to mention the fact that I hope you're doing
> backup of external PG cluster with the plugin and not
> the Bareos instance itself. While it seems to work, doing a disaster
> recovery from that stream will force you to setup
> at new Bareos, then use bscan to restore the volume and insert the
> content of that last catalog backup inside the database and then
> being able to run the restore of the cluster with the plugin.
> 
> We highly advise to keep a dump that can be directly extracted from
> the volume with bextract.
> Regards.
> On Friday, 7 November 2025 at 01:45:04 UTC+1 Stefan Harbich wrote:
> > I was able to solve the problem.
> > I backed up all the databases from the PostgreSQL server to a dump
> > file.
> > I deleted and reinstalled the PostgreSQL server.
> > I restored all the databases.
> > I reconfigured the WAL archive.
> > Now it works.
> > 
> > Stefan Harbich schrieb am Freitag, 7. November 2025 um 00:58:08
> > UTC+1:
> > > I think it's a permissions issue.
> > > I didn't change any permissions when I installed the Bareos
> > > server on different hardware.
> > > I checked the UID and GID.
> > > They're the same on both systems.
> > > I even reinstalled the PostgreSQL server and the Bareos server.
> > > Always the same result. I'm at my wit's end.
> > > Here is my Debug Log.
> > > Greetings from Stefan Harbich
> > > 
> > > Am Mittwoch, dem 05.11.2025 um 02:25 -0800 schrieb Bruno
> > > Friedmann (bruno-at-bareos):
> > > > The cluster might be read-only replica too ;-9
> > > > 
> > > > On Wednesday, 5 November 2025 at 11:15:36 UTC+1 Bruno Friedmann
> > > > (bruno-at-bareos) wrote:
> > > > > PostgreSQL plugin will use FD bareos function to collect the
> > > > > data, like reading archived wal
> > > > > So the FD and the plugin need to be hosted on the PostgreSQL
> > > > > cluster.
> > > > > 
> > > > > 
> > > > > On Wednesday, 5 November 2025 at 10:09:16 UTC+1 Stefan
> > > > > Harbich wrote:
> > > > > > Hello, i'm getting the following error message with the
> > > > > > PostgreSQL plugin:
> > > > > > 
> > > > > > ...
> > > > > > 05-Nov 09:46 bareos-dir JobId 45: Version:
> > > > > > 24.0.7~pre11.e690d3a37 (28 October 2025) Debian GNU/Linux
> > > > > > 13 (trixie)
> > > > > > 05-Nov 09:46 bareos-dir JobId 45: Start Backup JobId 45,
> > > > > > Job=backup-postgresql.2025-11-05_09.46.15_03
> > > > > > 05-Nov 09:46 bareos-dir JobId 45: Connected Storage daemon
> > > > > > at bareos.intern.example.com:9103, encryption:
> > > > > > TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
> > > > > > 05-Nov 09:46 bareos-dir JobId 45:  Encryption:
> > > > > > TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
> > > > > > 05-Nov 09:46 bareos-dir JobId 45: Probing client
> > > > > > protocol... (result will be saved until config reload)
> > > > > > 05-Nov 09:46 bareos-dir JobId 45: Connected Client: bareos-
> > > > > > fd at bareos.intern.example.com:9102, encryption:
> > > > > > TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
> > > > > > 05-Nov 09:46 bareos-dir JobId 45:    Handshake: Immediate
> > > > > > TLS 
> > > > > > 05-Nov 09:46 bareos-dir JobId 45:  Encryption:
> > > > > > TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
> > > > > > 05-Nov 09:46 bareos-sd JobId 45: Using just in time
> > > > > > reservation for job 45
> > > > > > 05-Nov 09:46 bareos-dir JobId 45: Using Device "JustInTime
> > > > > > Device" to write.
> > > > > > 05-Nov 09:46 bareos-fd JobId 45: Connected Storage daemon
> > > > > > at bareos.intern.example.com:9103, encryption:
> > > > > > TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
> > > > > > 05-Nov 09:46 bareos-fd JobId 45:  Encryption:
> > > > > > TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
> > > > > > 05-Nov 09:46 bareos-sd JobId 45: Version:
> > > > > > 24.0.7~pre11.e690d3a37 (28 October 2025) Debian GNU/Linux
> > > > > > 13 (trixie)
> > > > > > 05-Nov 09:46 bareos-fd JobId 45: Extended attribute support
> > > > > > is enabled
> > > > > > 05-Nov 09:46 bareos-fd JobId 45: ACL support is enabled
> > > > > > 05-Nov 09:46 bareos-fd JobId 45: python3-fd-mod: python:
> > > > > > 3.13.5 (main, Jun 25 2025, 18:55:22) [GCC 14.2.0] | pg8000:
> > > > > > 1.31.2
> > > > > > 05-Nov 09:46 bareos-fd JobId 45: python3-fd-mod: Connected
> > > > > > to PostgreSQL version 130022
> > > > > > 05-Nov 09:46 bareos-fd JobId 45: python3-fd-mod: data_dir:
> > > > > > /var/lib/postgresql/13/main/
> > > > > > 05-Nov 09:46 bareos-fd JobId 45: Fatal error: python3-fd-
> > > > > > mod: building paths to backup failed with value.error:
> > > > > > start_dir needs to be a real directory, symlinks are not
> > > > > > supported.05-Nov 09:46 bareos-fd JobId 45: Version:
> > > > > > 24.0.7~pre11.e690d3a37 (28 October 2025) Debian GNU/Linux
> > > > > > 13 (trixie)
> > > > > > 05-Nov 09:46 bareos-fd JobId 45: Fatal error:
> > > > > > filed/fd_plugins.cc:784 PluginSave: Command plugin
> > > > > > "python:module_name=bareos-fd-
> > > > > > postgresql:db_host=postgresql.intern.example.com:db_user=po
> > > > > > stgres:db_password=:wal_archive_dir=/media/backups/
> > > > > > dsme01.intern.example.com/postgresql/wal_archives/"
> > > > > > requested, but job is already cancelled.
> > > > > > ...
> > > > > > The directories:
> > > > > > -
> > > > > > "/media/backups/dsme01.intern.example.com/postgresql/wal_archives/
> > > > > > "
> > > > > > - "/var/lib/postgresql/13/main/"
> > > > > > exist but are not linked. What does this error message
> > > > > > mean? Where should I look for the problem? The PostgreSQL
> > > > > > database server and the Bareos server are not running on
> > > > > > the same server. The plugin and the pg8000 software are
> > > > > > installed on both systems (Director & File Daemon). I don't
> > > > > > understand it. When I had the PostgreSQL database server
> > > > > > and Bareos server installed on the same hardware,
> > > > > > everything worked. Now, after separating them, it doesn't.
> > > > > > I'm at a loss.
> > > > > > Regards, Stefan Harbich
> > > 

-- 
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 [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/bareos-users/5d96787e959837803ac22f1ebad997d132a4891d.camel%40harnet.de.

Reply via email to