Large VBRCatalog folder

[Peter Faber]

Hi Guys,
why is index data from GuestIndexData.ZIP located both compressed AND uncompressed in the VBRCatalog???!!
i know why its there, but why twice??
with alot of VMs the folder gets very big

Regards Peter

[foggy]

Most likely index files are downloaded from guest in a compressed format and then are uncompressed to be used for search. Archive could then be of course deleted, but you still need this space to download the new one during the next job run.

[Peter Faber]

both the GuestIndexData.zip and uncompressed data is there for EVERY restorepoint
so is it safe to ex. Schedule a delete of all GuestIndexData.zip files from the VBRCatalog folder once a day ?
it would reduce the space usage of the VBRCatalog folder by 20-25% ^^

[foggy]

It is safe, you just will not be able to search guest OS files in corresponding restore points using Enterprise Manager.

[Peter Faber]

im only talking about deleting the compressed data not the uncompressed..

you stated that the uncompressed data is used for Enterprise Manager - Search.
so deleting the .zip files should not impact search or any other functions - correct ?

[foggy]

Correct. We will look into the ability to clean up them automatically though.

[Peter Faber]

Any news on this on foggy ?

[foggy]

This was not included in v9, but still on our radar. The correct behavior should maintain 14 days of uncompressed data, compressed data should be kept for all registered backups.

[agrob]

any news about this topic?
i just discovered that i have about 6 months of vbrcatalog data (compressed and uncompressed) on disk. I set the catalog retention in Enterprise Manager to 2 months, Recovery Points on backup and or copy Jobs are Maximum 5 weeks back. so if i get it right, i should have 2 months of vbrcatalog data at Maximum, not 6 months..? thanks

[foggy]

This is fixed in the upcoming v9.5.

[agrob]

good News, thanks Alexander!

[msknight]

I'm using Backup Enterprise Manager 8, and I've noticed two machines which are recording large space usage in the vbrcatalog/index/machines folder.

What I'd like to do, is get in to these files and examine them, so I can see what is going on, in these machines, that is causing such large file sizes.

I believe the problem is something going on, on the machines themselves, and I'm hoping that these index files can give me a clue ... I just don't know how to get in to these files to examine them. I've tried the usual internet searches, which is what led me here.

[Shestakov]

Hello Michele and welcome to the community!
What is the folder size you observe?
Thanks!

[msknight]

HI Shestakov, Thanks for the welcome

Most of our servers are a matter of a few hundred meg. A couple break in to the log gig territoriy, but two are 8 gig and 15 gig respectively.