Misleading messages during restore from backup
-
Hi,
I have seen this before, but not reported it. During a restore of a backup of a VM, to another host, the message during restore is a bit misleading.
I'm restoring from the remote named "xcp-ng-appservers" to (as indicated by the ongoing status) "Local h2 SSD new". The misleading part is "(on xcp-ng-1)", as I restore it to a SR on "xcp-ng-2" (and will run it from there).Maybe a simple fix would be to just make the meaning of the "on" a bit clearer, or just remove it (the backed up machine runs on 'xcp-ng-1', and I will have my duplicate from the latest backup started on 'xcp-ng-2')
-
Hi,
What do you mean, like it's a local SR? (so it should be on the host with the local SR?)
-
@olivierlambert The source machine for the backup is on local SR on 'xcp-ng-1'. I'm restoring it to a local SR on 'xcp-ng-2' (the backup is read from a remote SR)
-
I'm not sure to get it. If it's a restore, the source is not a SR but a BR. The question is the destination SR, so you do confirm it's a local SR to h2?
-
@olivierlambert I can make it even more confusing
But first, you're correct about me misnaming the BR as "Remote SR".
Just found out that the machine I backed up is NOT running on xcp-ng-1, but on xcp-ng-3 (I assumed it was xcp-ng-1 because of the message):
-
XO doesn't care where the previous/existing VM is running, restore creates an entirely new VM, so I'm not sure to get it either
-
@olivierlambert but the "importing content" message is incorrect:
"on SR Local h2 SSD new (on xcp-ng-1)"That's the problem (not to where it's restored to, and has to be run from because it's a local SR)..
In the message, what do "xcp-ng-1" have to do with this operation ? It's not involved at all..
-
It's where the task is hosted. XO does not invent it, just fetch it from XAPI. It's using exactly the "resident on" field from there: https://xapi-project.github.io/xen-api/classes/task.html
So it's not an XO "problem". I don't know the mechanism behind the "resident on" logic, so pinging @Team-XAPI-Network
-
@olivierlambert Thanks, that explains the "on .." part of the message, and as you mention, it's not a "problem", but just confusing in the context of that full message.
The optimal would of course be that the task was launched on the host that is "closest" to the SR, in this case a local SR on xcp-ng-2.This one (unrelated list of previous tasks) makes the message more clear what the "on.." part is about:
-
@olivierlambert as you said the resident-on field of a task is set by the helper which creates the task. So the value should be the name of the host where the task has been created.
-
And I assume the task is created on the master regardless the restore place is?
