purge index files in vbrcatalog folder

[Jean-Francois]

Hi,
few days ago, my hardddisk where vbrcatalog is installed, did not have more free space.
I have modified settings of retention in veeam enterprise manager but this morning, i see i have again files, whose date is higher than retention
i have defined retention at 2 months and i have again files of the beginning of the year.
I have cleaned the checkbox
i have rebooted the server.
must i do other thing ?
thanks for you help

[Vitaliy S.]

Hi Jean-Francois,

Could you please tell me what VBRCatalog you're looking at, the one which is located on the backup server or on Enterprise Manager machine? Have you synced the catalog data after applying the new retention policy settings?

Thanks!

[Jean-Francois]

Ok, it's vbrcatalog of enterprise manager, which is on the veeam backup server
When you say sync catalog, how do I do to apply policy ?
Thanks

[Vitaliy S.]

I have just verified this behavior with our QC team and it appears that this is a known bug, which should be fixed in our next update. This issue can only be observed when you configure our retention policy settings to store VM index data for less than 3 months.

[Jean-Francois]

Ok, if I understand good, it's a bug.
My version of veeam is 6.0.0.181 (64bit)
Must i upgrade to 6.1 or must i wait a new revision of the 6.1 ?
Can I delete oldest index files in the folder vbrcatalog\index\machines without risk ?
The number max of retention for one job is 5 weeks
the other jobs have a retention of 5 days
Thanks for your answer

[foggy]

Must i upgrade to 6.1 or must i wait a new revision of the 6.1 ?

You should wait for the next product release.

Can I delete oldest index files in the folder vbrcatalog\index\machines without risk?

Yes, you can remove the unneeded index files manually.

[Jean-Francois]

Thanks guys for your help

[aitzbitarte]

Hi
Same problem we have in
Version of veeam is 65.0.144(64bit)
Manager - Configuration >Setting>Catalog Retencion 1 months
is fixed in this version?
Thanks

[Vitaliy S.]

Hi Mikel,

According to the internal bug tracking system this has been fixed in the latest version.

Thanks!

[aitzbitarte]

Hi
Thanks!
We have the manual delete workaround and upgrade soon.