Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1279132

Bug#1126024: dbconfig-common: dbc_config_allow_backup usage needs to be clarified and tested

From "Bruno Friedmann @ bareos" <bruno.friedmann@bareos.com>
Newsgroups linux.debian.bugs.dist
Subject Bug#1126024: dbconfig-common: dbc_config_allow_backup usage needs to be clarified and tested
Date 2026-01-20 16:30 +0100
Message-ID <MflQ5-bY5c-3@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Show all headers | View raw


Package: dbconfig-common
Version: 2.0.25
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
At Bareos we use dbconfig to setup, configure, and also process db
schema upgrade when Major version of Bareos are installed.

But quite a number of our user have very very large database, hundreds
of GB even TB, and dumping locally into an hardcoded place a file has often 
lead to get / or /var partition full.

We have done all kind of research about the parameter
`dbc_config_allow_backup` as state in documenation, but without success.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

As documented we place dbc_config_allow_backup='' into
/etc/dbconfig-common/config and try the package upgrade.

The backup dump is created in /var/cache/dbconfig-common/backups

We also tried using ENV var dbc_backup='false' but it look like this one
is always reset to true in code with the $RET

   * What was the outcome of this action?

We really want to allow the usage of dbconfig with Bareos to most of
user and allow to skip db dump during package upgrade.

   * What outcome did you expect instead?

Db upgrade nicely handled, but not backup created.

ps: To be considered at the same time use a configurable place instead
of hardcoded path in the backup part

dbc_config_backup_path='/var/cache/dbconfig-common/backups' by default
having this variable can mitigate the case, as user would be able to
indicate a location able to able the dump.

fix doc and usage by standarizing dbc_config_allow_backup to be
dbc_config_allow_backup='false' and inside the code compared to true

if [ $dbc_config_allow_backup = 'true' ] ... a bit more same way as
other variables.

Thanks for you attention.
reference for bareos debian scripts https://github.com/bareos/bareos/debian 

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 13.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.18.5-1-default (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dbconfig-common depends on:
ii  debconf [debconf-2.0]  1.5.91
ii  ucf                    3.0052

dbconfig-common recommends no packages.

Versions of packages dbconfig-common suggests:
ii  dbconfig-pgsql  2.0.25

Back to linux.debian.bugs.dist | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

Bug#1126024: dbconfig-common: dbc_config_allow_backup usage needs to be clarified and tested "Bruno Friedmann @ bareos" <bruno.friedmann@bareos.com> - 2026-01-20 16:30 +0100
  Bug#1126024: dbconfig-common: dbc_config_allow_backup usage needs to be clarified and tested Paul Gevers <elbrus@debian.org> - 2026-01-22 19:10 +0100

csiph-web