Jobs Failing After Upgrading Ubuntu OS from 20.04 to 22.04

70 views
Skip to first unread message

santhoshreddy aleti

unread,
Jan 13, 2025, 2:10:33 PMJan 13
to bareos-users
I have recently upgrade the Ubuntu OS from 20.04 to 22.04 where BareOS is running. After the upgrade, jobs keep failing with below error:

Screenshot 2025-01-13 at 12.09.26 PM.png

I'm running this on production and I would like to get this fixed as soon as possible. Any help would be highly appreicated.

Thanks in advance!

Thanks
Santhosh

Bruno Friedmann (bruno-at-bareos)

unread,
Jan 14, 2025, 3:36:56 AMJan 14
to bareos-users
Ok you upgraded your OS to 22.04 (I would have gone to 24.04 :-) but what about bareos which version before and now did you think to upgrade the repo

what is your configuration, etc ... 

Your message seems to lack a few information to make anyone able to help you ;-)

santhoshreddy aleti

unread,
Jan 15, 2025, 10:47:28 AMJan 15
to bareos-users
Hi Bruno!

With Ubuntu OS upgrade, it did upgrade the bareos version to "24.0.1~pre19.3e3a7a6a2".

Please find the configuration below:

Fileset:
FileSet {
  Name = "Catalog"
  Description = "Backup the catalog dump and Bareos configuration files."
  Include {
    Options {
      Signature = XXH128
    }
    File = "/var/lib/bareos/bareos.sql" # database dump
    File = "/etc/bareos"                  # configuration
  }
}

Pool (Full):
Pool {
  Name = Full
  Pool Type = Backup
  Recycle = yes                       # Bareos can automatically recycle Volumes
  AutoPrune = yes                     # Prune expired volumes
  Volume Retention = 60 days         # How long should the Full Backups be kept?
  Maximum Volume Bytes = 50G          # Limit Volume size to something reasonable
  Maximum Volumes = 9000               # Limit number of Volumes in Pool
  Maximum Volume Jobs = 1
  Label Format = "Full-"              # Volumes will be labeled "Full-<volume-id>"
}

Job:
Job {
  Name = "BackupCatalog"
  Description = "Backup the catalog database (after the nightly save)"
  JobDefs = "DefaultJob"
  Level = Full
  FileSet="Catalog"
  Schedule = "WeeklyCycleAfterBackup"

  # This creates an ASCII copy of the catalog
  # Arguments to make_catalog_backup are:
  #  make_catalog_backup <catalog-name>
  RunBeforeJob = "/usr/lib/bareos/scripts/make_catalog_backup MyCatalog"

  # This deletes the copy of the catalog
  RunAfterJob  = "/usr/lib/bareos/scripts/delete_catalog_backup MyCatalog"

  # This sends the bootstrap via mail for disaster recovery.
  # Should be sent to another system, please change recipient accordingly
  Write Bootstrap = "|/usr/bin/bsmtp -h localhost -f \"\(Bareos\) \" -s \"Bootstrap for Job %j\" root"
  Priority = 11                   # run after main backup
}


Please let me know if any additional details are needed.


Thanks
Santhosh

santhoshreddy aleti

unread,
Jan 16, 2025, 5:35:26 PMJan 16
to bareos-users
Can someone please help here to resolve this issue? I'm completely blocked running backups in my environment. Any help would be highly appreciated. 

Not sure how to fix this? Is there a way I can fix the catalog or volume on the bareos server. Please find the error message below:

Error: Bareos cannot write on disk Volume "Full-0145" because: The sizes do not match! Volume=248 Catalog=249

Sebastian Sura

unread,
Jan 20, 2025, 12:50:36 AMJan 20
to bareos...@googlegroups.com

Hi Santhosh

could you verify that the size of the volumes created are actually 248 bytes big ?
What happens if you manually label a volume with the `label` command ? Is there still a disagreement between catalog and sd ? You can check the size of volumes via `list volumes`.
Could you run the storage daemon with debug level = 200 and send us the debug log ?  This would make it much easier to understand the issue.
We do automatic testing on Ubuntu 22.04, but this did not happen on our test mashines.

Could you also send us one of the bad volumes ? E.g. Full-0145 ?  I would like to look at the label that was created.

Kind Regards
Sebastian Sura

Am 16.01.25 um 23:35 schrieb santhoshreddy aleti:
--
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...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bareos-users/d5d4a0d1-e6dc-42fb-b413-95a67e49000an%40googlegroups.com.
-- 
 Sebastian Sura                  sebasti...@bareos.com
 Bareos GmbH & Co. KG            Phone: +49 221 630693-0
 https://www.bareos.com
 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
 Komplementär: Bareos Verwaltungs-GmbH
 Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz

Bruno Friedmann (bruno-at-bareos)

unread,
Jan 20, 2025, 5:15:21 AMJan 20
to bareos-users
Thank you to have reported this as an issue, we should continue to work there.

Reply all
Reply to author
Forward
0 new messages