In short, I am seeing the message "Unable to get disk information" in the "Datastore" step of the Restore dialog:
Short summary of what I've done to get this warning:
- Backed up VMs from an ESXi host just as usual. Worked fine.
- Changed IP on this ESXi host, and also recreated its datastore.
- In Veeam (the B&R console/application), removed the old ESXi host from Servers, and added the new one (practically the same but with another IP and datastore).
- Tried restoring VMs from the backup, but got the error "Host with id 'some long number' was not found" when selecting which VM to restore (the VM is actually put in the list, but in subsequent views throughout the Restore dialog it doesn't show up, which is a showstopper).
- Removed the backup from under Backups and used Import Backup to get it back.
Now the previous error no longer shows, but I do get the warning mentioned first in this post. If I continue with the restore, Veeam does seem to restore all the disks for the VM (two in this case) - I just can't see information about them, and can't set their new type, in the restore dialog).
Is this expected or unexpected, based on the information above?
I also discovered a workaround for this. If, when in the Datastore step and seeing this error, you go back three steps to the Restore Mode view, and then forward again to the Datastore view, the disks are updated and visible (i.e. normal behavior). My impression is that it's because this time, when the switch from Restore Mode -> Host happens, the correct/new host is already selected for the VM. I base this on the fact that I tried going back only two and one steps, but this had no effect. It's when you go back at least three times, so that the Restore Mode -> Host view change happens, that it "works" again.
It would be nice if someone could confirm this. I do not know if this is a local/isolated issue or can be reproduced in other environments as well. I can reproduce it here though.
I should also mention that this warning is shown regardless of whether I do Import Backup or Rescan Repository in order to get past the first error I mentioned ("Host with id 'some long number' was not found").
Let me know if you have any questions. Thanks.