Adding Hyper-V Host for Backup (Local Network)
It is mandatory to add the Hyper-V host containing the virtual machines (VMs) to the production infrastructure of the BDRSuite Backup Server before starting to configure a backup job.
Prerequisites
- The Microsoft Hyper-V Server you want to add must be a licensed version.
- The Hyper-V Server must be running Windows Server 2012 R2 or later.
Adding a Hyper-V Host
Local Network
Step 1: Access Hypervisors Section
Log in to the BDRSuite Backup Server.
- Navigate to Hypervisors, Servers & Endpoints in the menu.
- Go to Data Sources > Hypervisors > Hyper-V.
You will see a page displaying the previously added Hyper-V hosts.
- If no hosts are added, you will see the message: "No host added for backup."
Step 2: Add a New Hyper-V Host
- Click Add Hyper-V Server to initiate the process of adding your Hyper-V server to the Data Source of your BDRSuite Backup Server.
Step 3: Specify Deployment Location
- The Hyper-V Server can be added as a data source from either a local or remote network.
- Select Local Network for Hyper-V servers deployed within your organization’s on-premises network infrastructure.
Step 4: Provide Host Details
- Enter the Server Name or IP Address of the Hyper-V host you wish to add.
Step 5: Add Credentials
Select the administrator credentials for the entered Hyper-V host from the dropdown menu.
- If no credentials are available, click Add Credential to add new administrator credentials.
- [Click here to learn more about adding credentials.]
Step 6: Specify the Communication Port
- Enter the port number used by the BDRSuite Backup Server to communicate with the Hyper-V host.
- Click Save to add the Hyper-V host to the Data Sources.
Notes
- By default, BDRSuite communicates with the Hyper-V Server using port 5985 for HTTP and 5986 for HTTPS.
- You can modify the port number based on your configuration.
Managing Hyper-V Hosts
- Navigate to the Add & Manage Hyper-V Servers tab to view all the added Hyper-V hosts.
From this interface, you can:
- Edit Hosts: Update the server name/IP address, credentials, or port by clicking on the Edit icon.
- Delete Hosts: Remove a Hyper-V host by clicking the Delete icon. Confirm by selecting Yes, Delete to permanently remove the host.
Additional Notes
- Before Deleting a Host: Ensure all backup jobs associated with the Hyper-V host are deleted before removing it from the Data Sources.
Unsupported Scenarios:
- Hyper-V free versions are not supported for agentless backups as they lack the necessary APIs.
- Backing up encrypted VMs is not supported for certain Hyper-V configurations.
- Error Handling: Backup may fail due to compatibility or permission issues. Verify host configurations in such cases.
Related Articles
Adding Hyper-V Host for Backup (Remote Network)
The Remote Proxy in BDRSuite/BDRCloud is a component designed to extend backup and recovery capabilities to remote environments, particularly for backing up virtual machines (VMs), physical servers, or hypervisors that are not directly connected to ...
Adding VMware ESXi & vCenter Server for Backup (Local Network)
You need to add the VMware ESXi/vCenter Server containing the VMs to the production infrastructure of the BDRSuite Backup Server before starting to configure a backup job. Prerequisites The VMware ESXi or vCenter Server you want to add should be of ...
Quick Start Guide for Hyper-V Backup & Replication
About Hyper-V Backup & Replication BDRSuite offers a comprehensive solution for protecting Hyper-V virtual machines with features like agentless, image-level backups, incremental backups, and application-aware processing. It supports granular ...
Configuring Remote Proxy for Hyper-V Backup
The Remote Proxy in BDRSuite/BDRCloud is a component designed to extend backup and recovery capabilities to remote environments, particularly for backing up virtual machines (VMs), physical servers, or hypervisors that are not directly connected to ...
Troubleshooting: Unable to List VMs on Hyper-V Host
KB ID: 104057 Issue: The BDRSuite Backup Server is unable to display virtual machines from the added Hyper-V host/Cluster, resulting in an alert. Possible Causes and Solutions: Cause 1: Hyper-V Host/Cluster Not Reachable or Network Issues Solution: ...