large DB size

[Ramil]

Hello!
On a new Bareos server (ct-bareos02) that is 1 month old, the size of the Bareos database (vl-bareos02) is growing. On another server (vl-bareos01), which is more than 2 years old, with the same settings and more VMs and backup files, this does not happen.
What does it depend on and what steps should be taken?

[root@CT-BAREOS01 pgsql]# du -h --max-depth=1
926M    ./data
4.0K    ./backups
926M    .

bareos=# SELECT relname AS table_name,
       pg_size_pretty(pg_total_relation_size(relid)) AS total_size
FROM pg_catalog.pg_statio_user_tables
ORDER BY pg_total_relation_size(relid) DESC
LIMIT 10;
   table_name   | total_size
----------------+------------
 file           | 503 MB
 restoreobject  | 113 MB
 pathvisibility | 77 MB
 log            | 57 MB
 path           | 40 MB
 pathhierarchy  | 10040 kB
 jobmedia       | 5880 kB
 job            | 2128 kB
 jobhisto       | 944 kB
 media          | 936 kB
(10 rows)

========================================

[root@VL-BAREOS02 pgsql]# du -h --max-depth=1
8.7G    ./data
4.0K    ./backups
8.7G    .

bareos=# SELECT relname AS table_name,
       pg_size_pretty(pg_total_relation_size(relid)) AS total_size
FROM pg_catalog.pg_statio_user_tables
ORDER BY pg_total_relation_size(relid) DESC
LIMIT 10;
   table_name   | total_size
----------------+------------
 file           | 8312 MB
 path           | 15 MB
 pathvisibility | 2712 kB
 log            | 2648 kB
 pathhierarchy  | 2144 kB
 media          | 456 kB
 jobmedia       | 352 kB
 job            | 208 kB
 pool           | 80 kB
 fileset        | 80 kB
(10 rows)

[Silvio Schloeffel]

Hi Ramil,

you wrote your old server has more backup files (files to backup in my
mind).
The size of the file table says something different.
Have you done a simple count over the file table to look for the number
of entries?
Eventually you backuped more files as expected on the new system.
-> a lot of small files will not grow the used media size but the
filesize and the infos to store will be a lot more

Best

Silvio


Am 03.12.24 um 09:25 schrieb Ramil:
> pg_size_pretty(pg_total_relation_size(relid)) AS total_size

[Ramil]

I got a little confused when I wrote the server name. I meant that the database size of the old CT-BAREOS01 server, which is more than 2 years old, is larger than the new VL-BAREOS02 (1 month of use). CT-BAREOS01 has much more VMs backups than VL-BAREOS02, but the database size is smaller

вторник, 3 декабря 2024 г. в 14:43:22 UTC+6, Silvio Schloeffel:

[Silvio Schloeffel]

That's not a problem in my thinking.
If you backup a lot of small files, your file table will grow a lot.
After your definied recycle time, old files will be deleted from the table.

If your "old" system has different backup rules or vm's the number of
files is possible smaller and so the file table is smaller.
This table is, from the numbers I can see, your biggest difference
between old and new.

How long do you store backups before your overwrite the media files?
Have you done tests and these test data is still in the new system?
Have you compared backup jobs between old and new (number of backuped
files)?
Have you compared the job definitions, eventually you exclude some stuff
in the old system?
Same usage scenario of the vm's? We have a dev machine and a job creates
a lot of temp and testfiles ...
Do you backup the vm as file or do you backup the files from inside of
the vm?

I would wait until the system gets to the point where it recycles
volumes and look if you have a "stable" disk usage after this.
A new system will grow at the beginning and your db size is not big. I
mean 10G is nothing. Our backup system is small and the data dir is 20G
in size.

Best

Silvio



Am 03.12.24 um 10:01 schrieb Ramil:

> --
> 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 <mailto:bareos-
> users+un...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/bareos-
> users/fab8132e-e880-484f-a5f3-d30dd175e718n%40googlegroups.com <https://
> groups.google.com/d/msgid/bareos-users/fab8132e-e880-484f-a5f3-
> d30dd175e718n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
Silvio Schloeffel | CIO
silvio.s...@musicdna.com
Tel. +49 3677 2094 840

the evolution of music continues

MusicDNA GmbH
Schwanitzstrasse 6,
98693 Ilmenau, Germany
Phone: +49 3677 2094 840 | Fax: +49 322 298 222 00

Steuer-NR.: DE 156/114/04317

Handelsregisterzeichen: HRB Jena 517208,
Geschäftsführer: Sebastian Schmidt
www.musicdna.com