Proxmox Restore Fails

[HardHitter03]

Hi All,

I'm trying to restore a VM to Proxmox and am getting a strange error.

Code: Select all

2024-11-02 22:49:43.7260 00075 [8048] INFO  | [Worker][e4eb41af-c622-4a69-a8d8-bc36ddf670a2][veeamworker03]: Core service 76e641ae-3c6a-4f70-befa-e3be9c8f127f was successfully initialized
2024-11-02 22:49:44.1786 00075 [8048] INFO  | [ProxmoxNode][prox01][03000200-0400-0500-0006-000700080009]: Start Locked VM creation
2024-11-02 22:49:44.2200 00066 [8048] INFO  | [TaskServiceClientExtensions]: Waiting for the Restore task eda5e754-098f-411c-bf7b-e47885cf0d45 to complete
2024-11-02 22:49:54.2508 00075 [8048] INFO  | [TaskServiceClientExtensions]: Awaiting the Restore task eda5e754-098f-411c-bf7b-e47885cf0d45...
2024-11-02 22:49:54.2508 00075 [8048] ERROR | [TaskServiceClientExtensions]: Failed to await the Restore task eda5e754-098f-411c-bf7b-e47885cf0d45: Veeam.Communication.TypeProvider.Invoke.RpcCallException: taskset: failed to set pid 4225's affinity: Invalid argument
2024-11-02 22:49:54.2508 00075 [8048] ERROR | [TaskServiceClientExtensions]:    at Veeam.SPP.Communication.TypeProvider.InvokeResult.ThrowIfError(Boolean enableRpcErrors)
2024-11-02 22:49:54.2508 00075 [8048] ERROR | [TaskServiceClientExtensions]:    at Veeam.SPP.Communication.TypeProvider._RemoteProxy.Invoke_ReturnVoid_WithParameters(InvokeArg invokeArg, String methodName, Object[] parameters)
2024-11-02 22:49:54.2508 00075 [8048] ERROR | [TaskServiceClientExtensions]:    at VCF.RuntimeAssembly.Proxy.32335152-a85f-43d9-8e8e-901c43987918.AwaitTask(Guid)
2024-11-02 22:49:54.2508 00075 [8048] ERROR | [TaskServiceClientExtensions]:    at Veeam.Vbf.Project.Utilities.Extensions.TaskServiceClientExtensions.AwaitTask(ServiceReference serviceReference, Guid taskId, TaskType type)
2024-11-02 22:49:54.2508 00075 [8048] ERROR | [BackupServiceClientExtensions]: Failed to restore the VM NULL using the worker "ebbd1f02-1f78-43bf-bdef-fae72aaca9e2:100": Veeam.Communication.TypeProvider.Invoke.RpcCallException: taskset: failed to set pid 4225's affinity: Invalid argument

The setup:
2 x Proxmox hosts
192.168.0.2 (Prox01) is connected over a 1GB network.
172.16.40.20 (PVE) is connected over a 10GB network.
The VBR server is connected to both via separate interfaces.

To reproduce this error all I need to do is take a backup of a VM take from host 172.16.40.20 and restore it to host 192.168.0.2. If a take a backup that was originally done on the same host it works as expected.

What I have tried....

• Made sure VBR is updated (12.2.0.334)
• Removed and re-added both PVE hosts and both workers.
• Workers are updated as when I re-deployed them the logs indicated they installed a few updates.
• Tried a fresh FULL backup of the VM I'm trying to restore after re-adding both hosts.
• Updating the problem PVE host to 8.2.7.
• Rebooting the problem host.

This is a setup I'm using at home with an NFR license.

[HardHitter03]

Hi All,

Just incase anyone else comes past this i have figured this out. During the restore process it looks like the VM you are restoring is booted in some way so everything in your VM's config needs to be valid on the host you are restoring to.

This includes things like hardware passthrough and CPU affinity (limiting CPU to x cores).

I'm not sure how Veeam could handle this as you could want to restore a VM from 1 hardware to another and PCIE info or CPU core counts can be very different and you do not get the option to edit the config before the restore starts.

[rovshan.pashayev]

Hello Chris,

Thank you for information.