no, we've initialized the database new, no old entries there curre nt log of a running Full. You can see JobID is "1". DB is fresh! ___
344 2024-10-16 14:57:13 bareos-sd JobId 1: New volume "AI-Consolidated-0034" mounted on device "FileStorageCons1" (/var/lib/bareos/storage) at 16-Oct-2024 14:57. 343 2024-10-16 14:57:13 bareos-sd JobId 1: Warning: For Volume "AI-Consolidated-0034": The sizes do not match! Volume=238 Catalog=0 Correcting Catalog 342 2024-10-16 14:57:13 bareos-sd JobId 1: Moving to end of data on volume "AI-Consolidated-0034" 341 2024-10-16 14:57:13 bareos-sd JobId 1: Labeled new Volume "AI-Consolidated-0034" on device "FileStorageCons1" (/var/lib/bareos/storage). 340 2024-10-16 14:57:13 bareos-dir JobId 1: Created new Volume "AI-Consolidated-0034" in catalog. 339 2024-10-16 14:57:13 bareos-sd JobId 1: End of medium on Volume "AI-Consolidated-0033" Bytes=53,682,897,134 Blocks=12,799 at 16-Oct-2024 14:57. 338 2024-10-16 14:57:13 bareos-sd JobId 1: User defined maximum volume capacity 53,687,091,200 exceeded on device "FileStorageCons1" (/var/lib/bareos/storage). 337 2024-10-16 14:45:38 bareos-sd JobId 1: New volume "AI-Consolidated-0033" mounted on device "FileStorageCons1" (/var/lib/bareos/storage) at 16-Oct-2024 14:45. 336 2024-10-16 14:45:38 bareos-sd JobId 1: Warning: For Volume "AI-Consolidated-0033": The sizes do not match! Volume=238 Catalog=0 Correcting Catalog 335 2024-10-16 14:45:38 bareos-sd JobId 1: Moving to end of data on volume "AI-Consolidated-0033" 334 2024-10-16 14:45:38 bareos-sd JobId 1: Labeled new Volume "AI-Consolidated-0033" on device "FileStorageCons1" (/var/lib/bareos/storage). 333 2024-10-16 14:45:37 bareos-dir JobId 1: Created new Volume "AI-Consolidated-0033" in catalog. 332 2024-10-16 14:45:37 bareos-sd JobId 1: End of medium on Volume "AI-Consolidated-0032" Bytes=53,682,897,118 Blocks=12,799 at 16-Oct-2024 14:45. 331 2024-10-16 14:45:37 bareos-sd JobId 1: User defined maximum volume capacity 53,687,091,200 exceeded on device "FileStorageCons1" (/var/lib/bareos/storage). 330 2024-10-16 14:37:23 bareos-sd JobId 1: New volume "AI-Consolidated-0032" mounted on device "FileStorageCons1" (/var/lib/bareos/storage) at 16-Oct-2024 14:37. 329 2024-10-16 14:37:23 bareos-sd JobId 1: Warning: For Volume "AI-Consolidated-0032": The sizes do not match! Volume=238 Catalog=0 Correcting Catalog 328 2024-10-16 14:37:23 bareos-sd JobId 1: Moving to end of data on volume "AI-Consolidated-0032" 327 2024-10-16 14:37:23 bareos-sd JobId 1: Labeled new Volume "AI-Consolidated-0032" on device "FileStorageCons1" (/var/lib/bareos/storage). 326 2024-10-16 14:37:23 bareos-dir JobId 1: Created new Volume "AI-Consolidated-0032" in catalog. 325 2024-10-16 14:37:23 bareos-sd JobId 1: End of medium on Volume "AI-Consolidated-0031" Bytes=53,682,897,134 Blocks=12,799 at 16-Oct-2024 14:37. 324 2024-10-16 14:37:23 bareos-sd JobId 1: User defined maximum volume capacity 53,687,091,200 exceeded on device "FileStorageCons1" (/var/lib/bareos/storage). 323 2024-10-16 14:34:09 bareos-sd JobId 1: New volume "AI-Consolidated-0031" mounted on device "FileStorageCons1" (/var/lib/bareos/storage) at 16-Oct-2024 14:34. 322 2024-10-16 14:34:08 bareos-sd JobId 1: Warning: For Volume "AI-Consolidated-0031": The sizes do not match! Volume=238 Catalog=0 Correcting Catalog 321 2024-10-16 14:34:08 bareos-sd JobId 1: Moving to end of data on volume "AI-Consolidated-0031" 320 2024-10-16 14:34:08 bareos-sd JobId 1: Labeled new Volume "AI-Consolidated-0031" on device "FileStorageCons1" (/var/lib/bareos/storage). Sebastian Sura schrieb am Mittwoch, 16. Oktober 2024 um 14:06:10 UTC+2: > Hi Markus, > > do you mean this message pops up whenever bareos tries to append to/read > from a volume ? If so this is probably caused by you not migrating over > your old volumes to the new server. The database still contains references > to those old volumes and now when the director tells the storage daemon to > start appending to those volumes, the storage daemon is surprised that the > size that it was told by the director does not match up with the actual > size on disk (as it was probably newly created by the storage daemon). > > Could you post some job logs here so that I can confirm my suspicion ? If > that is the case, then you need to keep in mind that you may not be able to > easily access your old backups any more. > > Kind Regards > Sebastian Sura > Am 16.10.24 um 13:33 schrieb Markus Dubois: > > we've migrated Bareos (23.05) to another server and started fresh with a > new db > > don't know if this is new or if we just recognized it... > on every backup file creation (50GB) each, we get the entry The sizes do > not match > > ..backup ist still running. Does seems to work though..... > > Can we ignore those messages? > > -- > 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 on the web visit > https://groups.google.com/d/msgid/bareos-users/e4dc57db-fa90-4494-9a5c-628b272af3ecn%40googlegroups.com > > <https://groups.google.com/d/msgid/bareos-users/e4dc57db-fa90-4494-9a5c-628b272af3ecn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > -- > Sebastian Sura [email protected] > 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 > > -- 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 on the web visit https://groups.google.com/d/msgid/bareos-users/5ae0694d-963e-4ee9-b40e-6cc1951c902bn%40googlegroups.com.
