We are trying to restore a VM onto our storage, at 99% the following error appears: Failed to update VM configuration Restore job failed Error: Failed to get planned VM (ID: 8e92ff70-b052-48f4-82a0-fd......
Solved
Veeam B&R Full VM Restore Error
Best answer by matheusgiovanini
This error is commonly caused by issues such as lack of datastore space, existing snapshots, or missing configuration files. You should check these aspects first.
Additionally, try re-running the restore using a different VM name and a different location. Restoring as a new VM can force the hypervisor to generate a new unique ID, which often resolves conflicts.
You can also use Instant VM Recovery to quickly verify the integrity of the backup before performing a full restore.
If possible, please provide the job log, the hypervisor details (e.g., vSphere version), and the type of restore you are performing (full VM, instant, to original or new location) as Antonio mentioned earlier. That will help us give you more specific guidance.
+11Hi
Please can you add more info about your infrastructure?
Hypervisor (I guess it's Hyer-V) and datastore have space to restore and VM and there aren’t conflicts in saved state data (network adapter names, disk type etc)… so are you trying to restore in another host?
To have a good troubleshooting please check for errors in Veeam logs (typically located on the backup server in the %ProgramData%\Veeam\Backup folder) for the restore task.
Please add more info and check errors in Veeam logs.
let us know what you find
+6This error is commonly caused by issues such as lack of datastore space, existing snapshots, or missing configuration files. You should check these aspects first.
Additionally, try re-running the restore using a different VM name and a different location. Restoring as a new VM can force the hypervisor to generate a new unique ID, which often resolves conflicts.
You can also use Instant VM Recovery to quickly verify the integrity of the backup before performing a full restore.
If possible, please provide the job log, the hypervisor details (e.g., vSphere version), and the type of restore you are performing (full VM, instant, to original or new location) as Antonio mentioned earlier. That will help us give you more specific guidance.
Hi
Please can you add more info about your infrastructure?
Hypervisor (I guess it's Hyer-V) and datastore have space to restore and VM and there aren’t conflicts in saved state data (network adapter names, disk type etc)… so are you trying to restore in another host?
To have a good troubleshooting please check for errors in Veeam logs (typically located on the backup server in the %ProgramData%\Veeam\Backup folder) for the restore task.
Please add more info and check errors in Veeam logs.
let us know what you find
Hi
I hope you’re well.
We have a standalone VEEAM server restoring to a separate Hyper-V server. The storage space is available. When the restore job begins, it states that original VM not found for other successful restore jobs this is not the case. Find below logs
<17> Error (3) Failed to restore vm. Name: [DC]
<17> Error (3) Failed to get planned VM (ID: 8e92ff70-b052-48f4-82a0-fdfa827540ad) state. Failed to find planned VM object. (Veeam.Backup.ProxyProvider.CHvWmiProxyErrorException)
<17> Error (3) at Veeam.Backup.ProxyProvider.CHvWmiReconnectableRemoteCommand.InvokeInThread(Delegate dlg, Object[] args) <17> Error (3) at Veeam.Backup.ProxyProvider.CHvWmiReconnectableRemoteCommand.DoInvoke(CHvWmiProxyRequestContextNdw context, Int32 reconnectsCount, Delegate dlg, Object[] args)
<17> Error (3) at Veeam.Backup.ProxyProvider.CHvWmiReconnectableRemoteCommand.Invoke[Ret](CHvWmiProxyRequestContextNdw context, Func`1 dlg)
<17> Error (3) at Veeam.Backup.ProxyProvider.CHvWmiPlannedVmRemoteManager2015.GetVmState(Guid vmId)
<17> Error (3) at Veeam.Backup.Core.HyperV.CHvWmiVmMethodsPlannedVmImpl.GetVmState(Guid vmId)
<17> Error (3) at Veeam.Backup.Core.HyperV.CHvVmWmiRenamer.RemoveSavedState()
<17> Error (3) at Veeam.Backup.Core.HyperV.CHvVmWmiRenamer.UpdateVmConfiguration(Boolean isReplica)
<17> Error (3) at Veeam.Backup.Core.CHvVmRestoreAlg2015.UpdateVmConfiguration(CHvWmiUtils wmiUtils, Guid vmId, CHvWmiConfig wmiConfig, Dictionary`2 targetDiskSpec, CHvSharedDiskExcludeChecker sharedDiskExcludeChecker, ISessionLogger logger, Boolean isReplicaFailBack, Boolean restoreToOriginalLocation)
<17> Error (3) at Veeam.Backup.Core.CHvVmRestoreAlg2015.RestoreVmObject(ISessionLogger logger, IStopSessionSync sync, CHvWmiUtils wmiUtils, CHvVmRestoredFileCollection restoredFilesCanBeNull, Boolean isReplicaFailBack, Boolean restoreToOriginalLocation)
<17> Error (3) at Veeam.Backup.Core.CHvVmRestoreAlg2015.RestoreVmObject(IStopSessionSync sync, ISessionLogger logger, Boolean isReplicaFailBack, Boolean vmSrcAndTgtHostsAreSame, CHvWmiUtils wmiUtils, CHvVmRestoredFileCollection restoredFilesCanBeNull, CHvVmSwitchPortInfo[]& restoreSwitches, Boolean restoreToOriginalLocation)
<17> Error (3) at Veeam.Backup.Core.CHvVmRestoreAlg2015.DoRestore(IStopSessionSync sync, ISessionLogger logger, Boolean isReplicaFailBack, Boolean restoreToOriginalLocation, CHvVmRestoredFileCollection restoredFiles)
<17> Error (3) at Veeam.Backup.Core.HyperV.CHvVmRestorer.RestoreVmOnNode(CHvDbHost trgHost, IHvVmBackupRestoreDataSource dataSource, IDiskProcessor diskProcessor, CRestoreFilesParallelProgressWriter progress, IStopSessionSync sync, ITask scheduledTask, CRestoreTaskSession taskSession)
<17> Error (3) at Veeam.Backup.Core.HyperV.CHvVmRestorer.Veeam.Backup.Core.IVmRestorer.DoRestore(IStopSessionSync sync, IStorageAccessor accessor)
<17> Info (3) Job Restore Task operation result: 'Failed to get planned VM (ID: 8e92ff70-b052-48f4-82a0-fdfa827540ad) state. Failed to find planned VM object.'
<17> Info (3) Job Restore Task session '067eb086-7c5b-4a15-931c-3be726985dd3' has been completed, status: 'Failed', details: '
<17> Info (3) Initializing restore
<17> Info (3) Failed to get planned VM (ID: 8e92ff70-b052-48f4-82a0-fdfa827540ad) state. Failed to find planned VM object.
<17> Info (3) '
Regards
Brian
+7We have a standalone VEEAM server restoring to a separate Hyper-V server. The storage space is available.
Is this a restore original VM or are you restoring to a new VM?
If its the original VM what happens of you restore to a new name?
+9base on logs, looks that issue is on platform itself - try to restore as new VM or delete VM first and then restore it. Maybe we will find issue, when you will start with deletion, where is the issue.
+12Are you restoring to a separate (standalone) Hyper-V server? In case you do, you have to select “restore to different location” since the VM ID Veeam is working with is obviously not available on the targeted (secondary) Hyper-V server.
In case you run a Hyper-V cluster you should select the cluster object itself as target.
Best
Lukas
Restored to a New VM and issue was resolved. Thank you guys for the guidance, a very helpful forum.
+6Happy to see the issue was resolved!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.