Hi, In case the server is "unbootable" because the root directory is full, you could try to mount from an usb stick and access your root partition by mounting it on the stick. You could then rsync or move the bareos database to a mount of an external storage. Once the rsync has been successful, delete the database on / then restart your server. Once the root partition is bootable again, make sure that bareos will find the new database location. You should either adapt it in the configuration file vi /etc/postgresql/<database>/main/postgresql.conf - search for "data_directory =" or you can crate a symbolic link inside /var/lib (something like postgresql -> /your/mount/path/to-the-new-database-location).
Start then the database and check if it is running. systemctl start postgresql To test the bareos services, use /usr/sbin/bareos-sd -t /usr/sbin/bareos-fd -t /usr/sbin/bareos-dir -t If everythig is okey, you should be able to start the bareos services: /bin/systemctl start bareos-dir bareos-sd bareos-fd Hoping that might help you. Birgit Riot Nrrrd schrieb am Freitag, 20. Juni 2025 um 22:02:35 UTC+2: > At my work we have a Bareos setup with about 70 or so clients. > > It wasn't set up by me originally; I inherited it. It (Bareos 22.1.4) was > set up on a RHEL system with dual SSDs for the root volume and the total > disk space on "/" is around 380 GB. Well, due to 'slow creep' eventually > the Bareos PostgreSQL database filled up the partition to 100% and now > backups have stopped. > > The last job before they stopped failed with > > -- > 18-Jun 21:06 bareos-sd JobId 93060: Releasing device "Disk2" > (/export/bareos/storage2). > 18-Jun 21:06 bareos-sd JobId 93060: Elapsed time=01:06:55, Transfer > rate=12.86 M Bytes/second > 18-Jun 21:06 bareos-dir JobId 93060: Insert of attributes batch table with > 475489 entries start > 18-Jun 21:07 bareos-dir JobId 93060: Fatal error: cats/sql_create.cc:815 > Fill File table Query failed: INSERT INTO File (FileIndex, JobId, PathId, > Name, LStat, MD5, DeltaSeq, Fhinfo, Fhnode) SELECT batch.FileIndex, > batch.JobId, Path.PathId, batch.Name, batch.LStat, batch.MD5, > batch.DeltaSeq, batch.Fhinfo, batch.Fhnode FROM batch JOIN Path ON > (batch.Path = Path.Path) : ERR=ERROR: relation "batch" does not exist > LINE 1: ..., batch.DeltaSeq, batch.Fhinfo, batch.Fhnode FROM batch JOIN... > -- > > I tried using the *bconsole* 'prune' command to prune back the jobs, > hoping it might result in a database shrinkage. Instead it just kept > getting larger. :-( I tried asking ChatGPT for suggestions and it just > returned a bunch of pgsql commands that I don't really understand (not that > I'd trust ChatGPT anyway). > > Does anyone have any 'ELI5" suggestions on what to do? > > I suppose I could shut down Bareos and the database and move > */var/lib/pgsql* to one of the data (backups) volumes and out of the root > partition, but I was hoping I could solve this without having to move it by > getting the database to shrink. Is that a possibility? > > -- 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 visit https://groups.google.com/d/msgid/bareos-users/b3bf1e5a-4583-4843-a514-be31c9bdf17bn%40googlegroups.com.