File indexing is processed on virtual machines as follows:
A Linux proxy is required to file index a Linux VM.
A Linux proxy can file index a Windows VM, if the VM has a basic disk and an NTFS file system.
If a Linux proxy attempts to file index a Windows VM that has a dynamic volume, a FAT/FAT-32/ReFS file system, or MS Windows storage spaces configured, the file indexing job will go to Pending state and then re-distributed to a Windows proxy on the next attempt available at the subclient level.
The FREL provides UNIX file system support for ext2, ext3, ext4, XFS, JFS, Btrfs, HFS, and HFS Plus. To enable extended file system recovery for UNIX-based virtual machines, deploy a FREL or convert a Linux MediaAgent to a File Recovery Enabler. For more information, see Converting a Linux MediaAgent to a VMware File Recovery Enabler for Linux.
Index Server Hardware Requirements
The index server must have the MediaAgent, Index Gateway, and Index Store packages installed. For index server MediaAgent hardware requirements, see System and Hardware Requirements.
Multi-node is supported on index servers. For more information, see Adding a Node to the Index Server.
When you enable file search at plan level, the system pushes the packages to the MediaAgent that is specified in the associated backup plan or storage policy. That MediaAgent then begins acting like an index server.
It is recommended that you deploy a separate MediaAgent, rather than using a shared computer, for the index server. Make sure that you associate this MediaAgent with the storage plan policy.
If the MediaAgent used in the storage plan or storage policy is the same computer as the CommServe, Web Console, Web Server, or Command Center computer, then you must manually install the required packages on the MediaAgent before you enable file indexing.
VSA Proxy Hardware Requirements
For hardware requirements for a VSA proxy installed on either a physical or virtual machine, see Hardware Specifications for Virtual Server Agent.
When enabling File Indexing Version 2 for virtual machines, the hardware requirements listed in Hardware Specifications for Virtual Server Agent should be increased by 25 percent.
File Based Recovery Cache Requirements
You must ensure that there is at least 100 GB of free disk space for the file based recovery (FBR) cache directory.
By default, the FBR cache directory is located under the Job Results directory, unless the FBR cache directory location was changed manually or was deployed from an open virtual appliance (OVA) template.
To change the FBR cache directory location, see "Additional Configuration" in Automatic Configuration of a MediaAgent as a Linux File Recovery Enabler (FREL).
Do not set the path for the FBR cache mount point to the root directory or to the Commvault ransomware protection-enabled directory.