Verify that the restore worker VM you want to use on the destination hypervisor meets the requirements.
Packages
-
Commvault MediaAgent
-
Commvault Threat Analysis
-
Commvault Virtual Server Agent. (Only for Linux-based restore worker VM)
-
Python3
-
AWS Python SDK (boto3)
Operating Systems
-
Windows Server 2022 x86_64 Edition
-
Rocky Linux 9.x x86_64
-
Red Hat Enterprise Linux 9.x x86_64
Hardware
-
8 cores CPU or vCPU
-
Minimum of 32 GB RAM
File System Support
To ensure that the backed up VM disks mount successfully, configure the restore worker VMs with necessary FS tools.
-
For Windows VMs that use Resilient File System (ReFs), a worker VM with same or higher OS version is required.
-
For Linux VMs that use Btrfs file system, a worker VM with the Btrfs utility tool is required.
Considerations
-
A restore worker VM cannot be the same machine as the access node of the hypervisor.
-
Ensure that the Microsoft Defender or other anti-virus software are disabled on the restore worker VM.
-
Ensure that the restore worker VM connects to the CommServe server, workflow engine server and access nodes.
-
All the restore worker VMs that you configure must reside on the destination hypervisor.
-
A Windows worker VM must have an OS disk only. A Linux worker VM must have 3 disks—
/dev/xvda,/dev/xvdfand/dev/xvdgonly. -
Configure appropriate number of restore worker VMs on the destination hypervisor. The number of Windows and Linux worker VMs required depends on the number of guest VMs in your environment. For example, if there are 30 Windows and 10 Linux guest VMs, then you can configure 3 Windows and 1 Linux worker VM.
-
For Linux worker VMs, in the LVM config file
/etc/lvm/lvm.conf, do the following:-
Set
use_devicesfile = 0to disable use of Devices file. -
Set
event_activation = 0to disable event activation. -
Set
auto_activation_volume_listto the name of root volume groups of the respecting restore worker VM.
-