Hi all,
I received an alert about the index cache of a media agent that will be full in less than 30 days, this for the first time with this server.
This media agent is only used to backup VMware VMs, around 220 machines per night (2 storage policies).
A Treesize report shows clearly the origin of this phenomena (1.png):
More details indicates that there are huge VMware logs (2.png):
Yesterday, disk was almost filled up to 90 % (3.png), I ran the load balance process from the “ Index server load” report, it freed 20 GB.
The “Index cache space usage details” report for this MA, on a monthly basis this time (4.png) shows that before May, 2025, the legacy index (v1) size was neglectable.
As far as I know, the only modifications on the infrastructure over the lasts months are deployment of updates, from 11.32.76 to 96, then 112.
I had a look at Index log files on MA, nothing relevant.
My questions are:
Why the VMware logs consumed so much disk space ?
Why the legacy index (v1) size increased recently that way ?
How can I get rid of that issue ?
Thank you advance for your help.
Media agent index cache space usage increasing quickly: Huge VMware log files.
+5Best answer by RC23
By the way, I configured today this additional settings on MA to avoid downloading VM log files, I guess it should be sufficient to solve this issue:
https://documentation.commvault.com/additionalsetting/ndownloadlogfile.html
+5By the way, I configured today this additional settings on MA to avoid downloading VM log files, I guess it should be sufficient to solve this issue:
https://documentation.commvault.com/additionalsetting/ndownloadlogfile.html
+17- Commvault Certified Expert
For v1 indexing in combination with intellisnap on VMware 175GB doesn’t seem to be a huge amount for 200+ VM’s. Looking at the system requirements, even an extra small media agent should have 400GB for Index Cache available. My question is, is there a reason that you aren’t adopting v2 indexing for VM backup? This will result in a far more effecient Index Cache usage.
+5Yes, you are right, v2 indexes will be implemented soon.
As VM log files are no longer downloaded, it has freed disk space so this can be considered as solved.
In v1, what is the point for Commvault to download VM log files and store that files in the indexes ?
+17- Commvault Certified Expert
Here is the information you are looking for:
VM log files are being stored in the index cache folder on the MediaAgent during IntelliSnap backups of VMware VMs due to a change introduced in Commvault Feature Release 32.83 (and included in 11.32.94 and later). This change was made to improve restore reliability, especially for proxyless backup copies, by ensuring that VMware VM configuration files—including log files and the nvram file—are included in the backup process.
Key Points:
- Starting with FR32.83, Commvault includes VMware VM configuration files and logs in the backup copy process.
- These files are processed and temporarily stored in the index cache folder on the MediaAgent during the indexing phase of the backup.
- The intention is to enhance restore reliability by ensuring all necessary configuration files are available for recovery scenarios.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.