To read data for advanced Linux file systems, a File Recovery Enabler for Linux can be used to browse and restore data from backups of Linux guest VMs.
Live Browse Results
When you perform a live browse for a Linux guest VM, the directory hierarchy displays results for each guest VM using the same root directory structure as the source VM, and are restored using the same folder structure. Mounted devices are shown in the directory structure according to the following rules:
-
If a device is present in the source VM under the /etc/fstab folder with the device UUID or logical volume name, the live browse results show the device in the same location.
-
If a device cannot be located in the root file system and the device is a raw disk, the live browse results show the device under the /cvlostandfound/blkuuidOfDevice directory.
-
If a device cannot be located in the root file system and the device is a logical volume, the live browse results show the device under the /cvlostandfound/vgname-lvname directory.
Prior to 11.20, directories were listed under volume names or mount paths that were different from the source VM.
Linux File System Support
For Linux guest VMs, you can enable browse and restore operations for Linux file systems (ext2, ext3, ext4, XFS, JFS, HFS, HFS Plus, and Btrfs) by converting a Linux MediaAgent to act as a File Recovery Enabler. For hypervisors that support Linux proxies, the Virtual Server Agent role can also be enabled on the MediaAgent.
For Commvault Service Pack 7 and later, MediaAgents that are able to act as File Recovery Enablers are automatically configured.
Note
The 11.20 version of the FREL runs on CentOS 8, which does not support Btrfs file systems. To perform live browse and restore operations for VM guest files with Btrfs file system data, use an earlier service pack version of the FREL that runs on CentOS 7.x.
Live Browse with Linux MediaAgents
For Service Pack 11 and earlier service packs, if the MediaAgent for a live browse operation is running on Linux, the operation replaces the MediaAgent with a VSA proxy running on Windows:
-
If a Windows proxy is included on the proxy list for the instance or subclient, the live browse uses that proxy instead of the default MediaAgent. The MediaAgent role must be enabled on the Windows proxy.
-
For Service Pack 11 and later service packs, if no Windows proxies are available for the instance or subclient, the live browse uses the CommServe system. The Virtual Server Agent and MediaAgent packages must be installed on the CommServe system.
Note
-
On the Commvault HyperScale Appliance, the CommServe software and the Virtual Server Agent and MediaAgent packages are pre-installed. If you are using a CommServe system on the HyperScale Appliance, you do not need to perform any additional configuration to enable live browse operations using VSA proxies and MediaAgents running on Linux machines.
-
In HyperScale 1.5 and HSX environments, live file browse of RedHat Enterprise Linux/CentOS/Oracle Linux 8.x virtual machines needs a RedHat Enterprise Linux/CentOS/Oracle Linux 8.x Linux MediaAgent that is converted to FREL machine.
-
To avoid falling back to a Windows proxy or the CommServe system, you can specify a Windows MediaAgent for a browse operation. From the Browse and Restore Options dialog box, click the Advanced Options tab and select a Windows MediaAgent from the Use MediaAgent list.