Comprehensive data protection for all workloads
Post Reply
jlo
Influencer
Posts: 11
Liked: never
Joined: Jul 08, 2019 2:11 am
Contact:

VBRCatalog Index didn't auto cleanup

Post by jlo »

VBRCatalog Index size getting bigger and bigger. Found that the oldest Index was created in March last year.
I don't understand why those old index still exist as the retention period in Enterprise Manager set to keep 1 month only.

In Backup & Replication:
<target_backup_job> -> Storage -> Retention policy -> Restore points to keep on disk: 356

In Backup Enterprise Manager
Configuration -> Settings:
Guest File System Catalog -> Retention period, months: 1
Event History -> Keep only last 12 week(s)
wishr
Veteran
Posts: 3077
Liked: 455 times
Joined: Aug 07, 2018 3:11 pm
Full Name: Fedor Maslov
Contact:

Re: VBRCatalog Index didn't auto cleanup

Post by wishr »

Hi jlo,

Welcome to Veeam Community Forums!

It may be happening due to configuration backup. Have you discussed this situation with our support team?

Thanks
jlo
Influencer
Posts: 11
Liked: never
Joined: Jul 08, 2019 2:11 am
Contact:

Re: VBRCatalog Index didn't auto cleanup

Post by jlo »

Hello wishr,
I didn't contact veeam support team. As I think I may find the answer here. Is it save to delete those outdated index manually?
veremin
Product Manager
Posts: 20413
Liked: 2301 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: VBRCatalog Index didn't auto cleanup

Post by veremin »

Correct, you can manually remove obsolete data from this directory.

However, it won't fix the underlying problem (why it auto cleanup doesn't work), so, I'd still recommend you contacting support team.

Thanks!
Post Reply

Who is online

Users browsing this forum: AdsBot [Google], Bing [Bot], Google [Bot] and 152 guests