-
- Expert
- Posts: 106
- Liked: 29 times
- Joined: Mar 16, 2023 5:47 pm
- Contact:
Veeam 12 Postgres - Very large config backup
When I was running MSSQL the daily config backups were about 1MB. With Postgres, they are 101MB and growing. Why are they so much bigger and what can be done about this? I can open a SR but I wanted to ask first if this is a known issue and if there was a fix. My latest support cases have been less than ideal in terms of the quality of the support engineer.
Start time 10:00:10 AM Data size 1.7 GB
End time 10:01:46 AM Backup size 101.6 MB
Duration 0:01:36 Compression 17.13x
Details
Catalog Items Size Packed
Configuration catalog 5448 5.4 MB 424.7 KB
Backups catalog 25799 61.5 MB 5.0 MB
Sessions catalog 1640624 1.6 GB 96.2 MB
Tape catalog 0 55.0 B 63.0 B
Start time 10:00:10 AM Data size 1.7 GB
End time 10:01:46 AM Backup size 101.6 MB
Duration 0:01:36 Compression 17.13x
Details
Catalog Items Size Packed
Configuration catalog 5448 5.4 MB 424.7 KB
Backups catalog 25799 61.5 MB 5.0 MB
Sessions catalog 1640624 1.6 GB 96.2 MB
Tape catalog 0 55.0 B 63.0 B
-
- Product Manager
- Posts: 10110
- Liked: 2696 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Veeam 12 Postgres - Very large config backup
Hello Pmichelli
Our support team has tools to identify any potential known issue from the logs and compare it to the list of private hot fixes (or registry workarounds) we have. That's why I suggest to open a support case.
May I ask, have you File To Tape jobs in your environment? Starting with V12, information about each file is stored in the configuration database and will also be exported with a configuration backup.
Best,
Fabian
Our support team has tools to identify any potential known issue from the logs and compare it to the list of private hot fixes (or registry workarounds) we have. That's why I suggest to open a support case.
May I ask, have you File To Tape jobs in your environment? Starting with V12, information about each file is stored in the configuration database and will also be exported with a configuration backup.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Expert
- Posts: 106
- Liked: 29 times
- Joined: Mar 16, 2023 5:47 pm
- Contact:
Re: Veeam 12 Postgres - Very large config backup
Hi Fabian,
We do not use tape at all. Our jobs have remained pretty much the same since we moved from MS SQL to PostgreSQL, which is why I can't understand why the config backups are much larger now. I will open a SR this morning and submit some logs.
Thanks
We do not use tape at all. Our jobs have remained pretty much the same since we moved from MS SQL to PostgreSQL, which is why I can't understand why the config backups are much larger now. I will open a SR this morning and submit some logs.
Thanks
-
- Chief Product Officer
- Posts: 31979
- Liked: 7441 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Veeam 12 Postgres - Very large config backup
From the data in Details it is clear that almost all the space in configuration backup is consumed by Sessions history. This will of course keep growing for years until hitting its retention policy (3 years by default, if I'm not mistaken).
However, you say "very large" in the topic name... really? 100MB is like 100x times less than image-level backup of a single VM. And even when/if your config backup grows 10x, its size will still be negligible in the grand scheme of things? So, I'm not sure why this is even remotely a concern tbh...
However, you say "very large" in the topic name... really? 100MB is like 100x times less than image-level backup of a single VM. And even when/if your config backup grows 10x, its size will still be negligible in the grand scheme of things? So, I'm not sure why this is even remotely a concern tbh...
-
- Expert
- Posts: 106
- Liked: 29 times
- Joined: Mar 16, 2023 5:47 pm
- Contact:
Re: Veeam 12 Postgres - Very large config backup
Hi Gostev
I said very large because less than 1 year ago we upgraded from V11 to V12 and moved from MSSQL to Postgres. My backups were 800KB vs 101MB so that is quite a large delta considering the amount of backups and times they run have not changed. Yes 100MB is not big but when you see 100x increase in a short time, you start to wonder what is going on
I said very large because less than 1 year ago we upgraded from V11 to V12 and moved from MSSQL to Postgres. My backups were 800KB vs 101MB so that is quite a large delta considering the amount of backups and times they run have not changed. Yes 100MB is not big but when you see 100x increase in a short time, you start to wonder what is going on
-
- Novice
- Posts: 8
- Liked: 1 time
- Joined: Feb 20, 2023 6:05 am
- Full Name: Fino
- Contact:
Re: Veeam 12 Postgres - Very large config backup
@pmichelli
Dont't worry - my bco file is 13GB. Postgres database round about 200GB large on a standalone
linux server.
And yes - we are doing file tape backups with 6 month of retention having now problems
with the function "collectvbrinfrainfoincremental" which runs 10 to 15 minutes and loops,
consuming lots of I/O. Console is very laggy. Closing console stops the function.
Case #07272243.
Also found out, because of our "large" environment the function "tape.delete_tape_medium_from_catalogue" made
problems and ran more than 24h for deleting a tape with NAS files (#07096403). That was fixed with a PF and is
included in the latest release. Funny comment in that PF from DEV:
-- plan for this query is very unstable, and when it uses "materialize" tactic, it can run for many hours.
-- probably a hack, but it works - we'll live with this. Probably come up with something better later.
Dont't worry - my bco file is 13GB. Postgres database round about 200GB large on a standalone
linux server.
And yes - we are doing file tape backups with 6 month of retention having now problems
with the function "collectvbrinfrainfoincremental" which runs 10 to 15 minutes and loops,
consuming lots of I/O. Console is very laggy. Closing console stops the function.
Case #07272243.
Also found out, because of our "large" environment the function "tape.delete_tape_medium_from_catalogue" made
problems and ran more than 24h for deleting a tape with NAS files (#07096403). That was fixed with a PF and is
included in the latest release. Funny comment in that PF from DEV:
-- plan for this query is very unstable, and when it uses "materialize" tactic, it can run for many hours.
-- probably a hack, but it works - we'll live with this. Probably come up with something better later.
-
- Service Provider
- Posts: 26
- Liked: 11 times
- Joined: Jul 25, 2016 2:36 pm
- Full Name: Philip Elder
- Location: St. Albert, AB, Canada
- Contact:
Re: Veeam 12 Postgres - Very large config backup
Is it the database itself that is large?
@sveloso indicates a huge database.
@pmichelli Same? Database or are there logs in there too?
@sveloso indicates a huge database.
@pmichelli Same? Database or are there logs in there too?
-
- Novice
- Posts: 8
- Liked: 1 time
- Joined: Feb 20, 2023 6:05 am
- Full Name: Fino
- Contact:
Re: Veeam 12 Postgres - Very large config backup
@MPECSInc:
Catalog Items Size Packed
Configuration catalog 575500038 58,1 GB 2,1 GB
Backups catalog 54999 259,2 MB 38,4 MB
Sessions catalog 853377 918,4 MB 53,0 MB
Tape catalog 732392549 386,7 GB 10,8 GB
Catalog Items Size Packed
Configuration catalog 575500038 58,1 GB 2,1 GB
Backups catalog 54999 259,2 MB 38,4 MB
Sessions catalog 853377 918,4 MB 53,0 MB
Tape catalog 732392549 386,7 GB 10,8 GB
Who is online
Users browsing this forum: Bing [Bot], tecnico26 and 80 guests