Create a recovery target for the Microsoft Hyper-V host you want to recover your domain controllers to.
Specify a VM template or a WinPE ISO file
Methods for recovering domain controllers to Microsoft Hyper-V are as follows:
-
Recover AD to clean VM (database only): Provide a VM template.
-
Recover to new VM (full System State): Download and provide a WinPE ISO file.
VM template
Follow the steps to prepare a virtual machine to be used as a template for recovering domain controllers:
-
Create a virtual machine on the Hyper-V server with Windows Server installed. The following table describes the OS versions that are supported for the forest functional level you are protecting:
Forest functional level
Supported OS versions
Windows Server 2025
Windows Server 2025
Windows Server 2016
Windows Server 2025
Windows Server 2022
Windows Server 2019
Windows Server 2016
Windows Server 2012 R2
Windows Server 2022
Windows Server 2019
Windows Server 2016
Windows Server 2012 R2
Note
The Windows Server must not be domain-joined or configured as a domain controller. Creating this VM by using Sysprep is not supported.
-
Log on to the Commvault Store.
-
On the store, search for “CVcustomizeVM” and download the package.
-
On the store, search for “AD Forest HyperV Repave scripts" and download the package.
-
Copy the packages downloaded from the Commvault Store to a folder on the virtual machine you will use as a VM template.
-
Extract the contents of the downloaded packages.
-
Open a Command Prompt from the folder where the package contents were extracted.
-
In the Command Prompt type “CVCustomizeVM -install” and press Enter.
This installs the customization service to prepare the Windows Server to be used as a VM template.
-
In the Command Prompt type “CVCustomizeVM -start” and press Enter.
This starts the VM customization service.
-
Open Windows PowerShell and run the FirewallRulesForCommvaultPushInstall.ps1 script.
This PowerShell script configures Windows Firewall so that Commvault software can be installed remotely on the VM. It enables incoming ports for TCP, WMI, DCOM, SMB, File and Printer Sharing, and dynamic RPC.
-
In Windows PowerShell, run the WindowsServicesForCommvaultPushInstall.ps1 script.
This PowerShell script configures Windows services so that Commvault software can be installed remotely on the VM. It configures RPC, DCOM, and remote management services to start automatically.
Download the latest WinPE5.1 ISO file
-
In a web browser, go to Commvault Store.
-
In the navigation pane, click Media Kits.
The Media Kits page appears.
-
In the navigation pane, click 1-Touch.
-
Download the latest version of WinPE5.1 or WinPE5_1 ISO.
Start the Add Microsoft Hyper-V target wizard
-
From the Command Center navigation pane, go to Protect > Active Directory.
The Overview page appears.
-
On the Forests tab, click the forest.
The forest page appears.
-
On the Runbook tab, click the runbook.
The runbook page appears.
-
On the Runbook settings tab, in the Create new domain controller VM from backup section, click View recovery targets.
The Recovery targets dialog box appears.
-
Click Add recovery target.
The Select target dialog box appears.
-
Select Microsoft Hyper-V.
-
Click Select target.
The Add Microsoft Hyper-V target wizard appears.
General page
-
Enter a name for the recovery target.
-
To register a new Hyper-V host, beside Destination client, click the add button.
The Add hypervisor dialog box appears.
-
Download the Active Directory Forest access node package.
-
Install the access node package on a server that has access to your Hyper-V host.
-
Wait until the installation completes successfully.
-
In the Add hypervisor dialog box, refresh the Hyper-V nodes list, and then select the host you installed the access node package on.
-
In the Host name box, enter the host name of the Hyper-V server.
-
In the Hypervisor display name box, enter a name for the recovery target.
-
For Credential, click the add button.
The Add credential dialog box appears.
-
Enter a name for the credential.
-
Enter the user name and password for an administrative account that has access to the Hyper-V server.
-
Click Save.
-
Click Save in the Add hypervisor dialog box.
-
For Destination client, select the Hyper-V host.
-
For Access node, select the server that you installed the access node package on.
-
For Security, select the roles that need access to the Hyper-V recovery target.
Note
You can ignore the VM display name options because they are not used.
-
Click Next.
Destination options page
-
For Restore location, select the location where you want the Hyper-V host to create the VMs for the recovered domain controllers.
-
For Destination folder, select the folder to store the restored VM files.
-
For Network adapter, select a network switch on the Hyper-V host that can communicate with the Commvault infrastructure.
-
Click Next.
Repave options page
On this page, you can provide a VM template to be used when restoring the domain controller with the Recover AD to clean VM database only method. If you are not using this method to recover the domain controller, no selections are required.
To specify your own Windows Server image, follow these steps:
-
To add your VM template, click Add.
The Custom image page appears.
-
For Operating system, select Windows.
-
Select an image from the Amazon Machine Image (AMI) list.
-
Click Save.
If you specify your own image, follow these steps to specify a software cache:
-
For OS Type, select Windows.
-
Under Software cache, select the server where the software cache is configured.
-
Click Next.
Recommended location for the software cache
Place the software cache on the access node that has connectivity to your recovered domain controllers.
Steps to configure a new software cache
-
From the Command Center navigation pane, go to Explore > Companies.
-
Click the Software caches tab, and then click Add to create a software cache and specify the server and details to host the cache.
-
After creating the software cache, from the actions list, select Sync to ensure that the cache is up to date.
Live Mount page
It is not necessary to make changes to these settings.
Advanced options page
On this page, you can provide the ISO to be used to recover the domain controller with the Recover to new VM full System State method. If you are not using this method to recover the domain controller, no selections are required.
-
For 1-Touch ISO path Windows, enter the path to the WinPE5.1 ISO you downloaded.
-
Click Submit.
Note
-
You don't need to provide a UNIX ISO.
-
Leave the default values for the CPU and memory configuration settings so that the recovered domain controller has the same virtual hardware configuration as the backed-up server.
-
You don't need to enable an association to a server group now. You can select a server group to associate recovered DCs with later, when you configure the runbook settings.
-
-
Close the Add Microsoft Hyper-V target wizard.