Article number
000003046
Affected Versions
All
Source Hypervisor
Hyper-V
Target Hypervisor
Hyper-V

Error: “Failed to move C:ZertoVMsZ-VRA-hostnamevra_bin.vhd to C:ZertoVMsZ-VRA-vra_binTemp.vhd host:[Host GUID, server GUID]” when Upgrading a VRA on a Hyper-V Host

Viewed 285 times

Summary

An administrator may come across a VRA upgrade failure in a Hyper-V environment with the error stating an inability to move a file.

Root Cause

Leftover files on the host from a previous failed attempt with the same filenames exist.

Symptoms

Upgrade VRA fails due to following error in the GUI:

Upgrading VRA on host <hostname> from version <old version> to version <new version>. Failed: Failed to move C:\ZertoVMs\Z-VRA-hostname\vra_bin.vhd to C:\ZertoVMs\Z-VRA-hostname\vra_binTemp.vhd host:[Host GUID, server GUID]

In the ZVM logs, the following exception is seen:

VraUpgradeTask,UpgradeVraFuncLocked,"Upgrade failed, set upgrade failed status","Zerto.Zvm.ScvmmServices.Scvmm.ScvmmException Void Move(System.String, System.String, Zerto.Zvm.Common.VirtualizationManager.VCenter.HostIdentifier) Zerto.Zvm.ScvmmServices.Scvmm.ScvmmException: Failed to move C:\ZertoVMs\Z-VRA-hostname\vra_bin.vhd to C:\ZertoVMs\Z-VRA-hostname\vra_binTemp.vhd host:[Host GUID, server GUID] ---> Zerto.HyperVAgent.AgentResponseException: Cannot create a file when that file already exists.

Solution

To workaround this issue, follow the below steps:

  1. Restart ZVM service on the local ZVM for the VRA of which the upgrade failed.

  2. Check Hyper-V host folder to see if "C:\ZertoVMs\Z-VRA-{hostname}\*Temp.vhd" exists and remove as necessary.

  3. Retry the VRA upgrade.