Access Nodes
File indexing is processed on virtual machines as follows:
-
A Linux access node is required to file index a Linux VM.
-
A Linux access node can file index a Windows VM, if the VM has a basic disk and an NTFS file system.
-
If a Linux access node 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.
Note
-
For ReFS considerations, see Restoring Guest Files and Folders.
-
For Storage Spaces considerations, see Live Browse for VMware.
The access node 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 Linux access node.
Hardware Requirements
MediaAgent Hardware Requirements
For MediaAgent hardware requirements, see System and Hardware Requirements.
Access Node Hardware Requirements
For hardware requirements for an access node installed on either a physical or virtual machine, see Hardware Specifications for Virtual Server Agent.
Note
When enabling file indexing for virtual machines, the hardware requirements listed in Hardware Specifications for Virtual Server Agent should be increased by 25%.
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 Access Node.
Note
Do not set the path for the FBR cache mount point to the root directory or to the Commvault ransomware protection-enabled directory.