Prepare your Microsoft Hyper-V environment for protection

Before you configure backups, decide where to place access nodes and how to use them. In most environments, the default settings work without adjustment. And if you plan to restore Hyper-V VMs to other platforms, prepare the source VMs.

Prepare for access nodes

Where to place access nodes

You deploy access nodes when you configure backups. You don't need to deploy them separately before you start.

Install the Commvault package directly on a standalone Hyper-V server or on a node in a Hyper-V failover cluster, not on a separate VM. You can use that server or node as an access node.

In a Hyper-V failover cluster, using multiple cluster nodes as access nodes provides load distribution and load balancing, improving backup and restore performance.

Avoid routing backup traffic across high-latency or restricted networks.

How to use access nodes

Commvault can automatically select the best available access node for backup and restore operations based on your configuration. During restores:

  • Standalone Hyper-V server: Access nodes are assigned by host match.

  • Hyper-V failover cluster: Access nodes run on cluster nodes. Work is assigned based on where VMs are stored:

    • Cluster Shared Volumes (CSV): Access nodes are assigned by CSV owner match.

    • Local drives or SMB shares: Access nodes are assigned by host match.

In some cases, you might need to select a specific access node.

Scenario Use when
Automatic access node selection (default) In most cases, including when you first configure backups.
When to select a specific access node • Your environment has segmented or restricted networks
• You need to control where backup or restore operations run
• You need additional capacity for concurrent operations
• You want to dedicate a specific access node for guest file restore operations

Prepare for cross-platform restores

If you plan to restore Hyper-V VMs to another platform, such as VMware vSphere, Amazon Web Services, or Azure Virtual Machines, you must prepare source VMs before backup and plan for post-restore configuration steps.

Before backing up the source Hyper-V VM

  • Network configuration: Configure VMs to use DHCP. Static IP addresses are not restored during cross-platform conversion.

  • For Linux VMs to VMware vSphere: Add required SCSI drivers and recompile the initrd file. Without this step, VMs fail to power on.

  • For Red Hat Enterprise Linux (RHEL) VMs to VMware vSphere: Install VMware-compatible drivers.

After restoring to VMware vSphere

  • VMware Tools are not installed automatically. Install VMware Tools manually using vSphere client.

  • Windows VMs: Disks might be offline. Bring them online manually.

  • UEFI boot VMs: Might require manual disk assignment updates.

For more cross-platform restore guidance, see Cross-Hypervisor Restores.

Prepare restore targets

Before restoring Microsoft Hyper-V VMs, review the target requirements for your restore method.

For information about preparing a target for live mount operations, where you run a VM directly from backup storage, see Provisioning Target Options for Hyper-V.

×

Loading...