Upgrade legacy VHR to Veeam Infrastructure Hardened Repository

In this guide, we will discuss the steps to “Upgrade legacy VHR to Veeam Infrastructure Hardened Repository”. According to Rick’s naming convention of VHR generation one (1). This blog post aims to demonstrate the “steps to upgrade legacy VHR to Veeam Infrastructure Hardened Repository“. Please, see what Ransomware Recovery looks like when the clock is ticking, and how to fix Unable to Remove Orphaned VHR Repository v2 from VBR v13.
As you can see below, the Managed Hardened Repository (VHR) v2 is deprecated. Also, when resolving the following error, “Upgrade Host Components: Unable to reinstall Deploy Service SSH“.
We were also alerted that there is a new version of the VHR. Because of this, I will be showing you how to upgrade Hardened Repository v2. Please see “Possible Impacts of Removing the Machine Where Veeam Is Installed From a Domain“.


Upgrade Veeam Hardened Repository v2 to VIHR
To do this, please download the VIA ISO from here. Below is the remote console of my VHR.

Upon landing on the page, please scroll down

Under the Additional Downloads, click on the download button as shown below.

Please, see how to set up Devolusion Remote Desktop Manager on Windows. Also, see Hardening Your Infrastructure: A Guide to VMware VBS and MS GPO Credential Guard in VBR v13, and Why does the legacy PXE not work on Generation 2 VM?
Upload ISO to Proxmox
In the attached NFS storage, we added to Proxmox “Add Synology NFS Storage to Proxmox VE for VMs and Backups“. We will have to upload our downloaded VIA image as shown below.

Browse to the path where the image resides on my PC, and it will be uploaded very shortly.

We have successfully uploaded the image as shown below.

Attach Image to VM
The steps below can be found here: “How to deploy and integrate VHR with VBR, and also see How to Resize or Expand Proxmox Hard Drive“. Under Hardware, we will add the CD/DVD image.

Please select the storage where the image was uploaded to, and select the Image.

Click on OK.

Now, you will have to change the boot order. Click on “option” and select the boot order as shown below.

Move the device up (ide0) and click OK.

Please, see How to set up a VM via PXE boot on a Generation 1 VM, how to Update Veeam Backup for Proxmox Plugin to support PVE 9.0, and how to setup Veeam Software Appliance v13.
Boot Veeam Hardened Repository
When the ISO boots up, as shown on the splash screen above. Select the “Veeam Hardened Repository.

Click on “Upgrade – upgrade Hardened repository to latest version”.

Shortly, the systemd boot sequence flashes as shown below

Please, see how to create a backup job for Proxmox VMs using VBR, how to delete a VM and Storage in Proxmox, and how to resize or expand Proxmox Hard Drive.
Note: Ensure you take a look at the official guide for the requirements in order to avoid errors of this nature below and have a flawless upgrade.

I initially provisioned the virtual disk at the minimum recommended size of 110 GB as specified for VHR. I then expanded the virtual disk to 120 GB at the hypervisor (Proxmox) level to reflect the new VIHR requirements.



Click “Yes” to perform the upgrade and replace my current system and its settings.

As you can see, the installation is now in progress.

When the installation completes, either uncheck the device Ide0 in my case or move it downwards as shown below.

Please, see Migrate Windows Servers from Hyper-V to Proxmox Correctly, how to set up the OOTBI Virtual Appliance on Proxmox VE, and Unknown Error occurred when installing Veeam Software Appliance.
Perform Initial Upgrade for VIHR
Accept the EULA as shown below

Enter the Hostname

Here, I will set the static IP. I have not covered the entire process in this guide.

Ensure you select the right time zone

Will select Berlin and Hit Enter

Click on Next to proceed.

Set the Host Administrator password

Select “Show Password”.

Select Show QR-code

Enter the Code displayed on yourAuthenticator.

Let’s click next to proceed.

We will do the same for the Security Officer (Veeamso) and enter the password.

Note that, at this time, you cannot set the MFA for the veeamso. You can only do this during logon. Click on OK.

Hit the Finish button.

Shortly, services will be started.

Below are the URL and IP address, etc., for the Host Management.

Please, see Bypassing BitLocker Loop by Unlocking or Disabling or PC Reset, how to create a two-way Active Directory Trust, and how to create a new Azure SQL Database [PaaS].
Access Veeam Host Management
You can now access the Host Management Console via the URL below. Enter the host management account and password.

Please, see Restore MSSQL Server on Azure VMs using Azure Backup, MSSQL Server Error 833: Synthesis of Real-World Case Studies, and Pull and Push Commvault Images to Azure Container Registry.
Step 2: Integrate with VBR
Note: FQDN works reliably in VBR/VSA v13 due to strict reverse DNS requirements for certificate authentication, SSH, and agent deployment on Linux. IPs skip PTR lookups and often fail validation.
Because of this, launch DNS Manager and create an “A Record” as shown below for the new VIHR server.

You can do this via the VBR console or Web UI if you have upgraded to VBR v13.

Navigate to the Backup Infrastructure and select “Managed Server” as shown below. Then edit and enter the FQDN and select the first authentication method to connect via using certificate-based authentication.

Select yes to trust the server. Here is a guide on how to fix Failed to connect to Deployer Service Error to resolve this issue just in case you run into it.

As you can see, it is connecting to the installer service. Please, see how to Unable to Remove Orphaned VHR Repository v2 from VBR v13.

As you can see below. The following will be installed on the target host.

Operations performed successfully.

As you can see below, the server has been saved with some warnings.

We have successfully upgrade form the legacy Veeam Hardened Repository to the Veeam Infrastructure Appliance Hardened Repository.

I hope you found this guide on how to upgrade legacy VHR to Veeam Infrastructure Hardened Repository very useful. Please, feel free leave a comment below.
FAQs
This error occurs in Proxmox VE because the boot order still includes ide0 (IDE CD-ROM), even though the device is not present.
This XCP-ng/Xen error indicates the Storage Repository (SR) backend cannot access or mount the SR due to a missing runtime mount point. This is because I had manually deleted some folders on the NFS on Synology.
I hope you found this blog post on “Upgrade legacy VHR to Veeam Infrastructure Hardened Repository” very useful. Please, feel free to leave a comment below.