PRestoring the WIndows2019 is not restore ok,  the W2019, appear a error: INNACESSIBLE_BOOT_DEVICE , i not run.

The backup solution is not consistent and secure.

Thx

Hi neos,

I will check your backup and restore logs and get back to you. 

Looking at the VMware error message (invalid configuration for device '5'), the problem is with the IDE controller of the VM or in one of the attached virtual devices. One common issue is that the original VM had a virtual Cdrom attached pointing to an ISO file that is no longer accessible. Normally, Archiware Pure will work around this by changing the virtual Cdrom configuration to a more generic setting precisely to avoid such errors. I will check the logs to see if this is the case here and will investigate further if something went wrong. If possible, please check the VMware logs also (the logs are probably very large so best to try the restore again so that error appears again). They will include a similar message (invalid configuration for device) but accompanied with other, more detailed messages.

Another error we encountered a few times is that when a VM is backed up using a vCenter server and a restore is attempted directly to an ESXi host that is still attached to the vCenter, VMware will create the VM but will fail at one of the subsequent steps of reconfiguring the VM (all part of the VM creation and all outside our control). I believe this is either a permission issue or possibly even a design decision on VMware's part requiring that such operations be performed through the vCenter server managing the vSphere. Restore to a standalone ESXi server should work as expected.

---

As for the Windows 2019, it is most likely an issue with nvram (virtual bios) not being copied properly during the restore. As per VMware instructions, automatically generated bios on VM creation is not to be used. Backup software should save a copy during backup and overwrite it during restore. If your logs include the restore of this VM also, I will check to make sure the bios was correctly restored. Since the VM creation does generate a new bios file and this works for most operating systems, Pure will not interrupt the restore in case the backup copy could not be restored. Unfortunately, newer versions of Windows OS (especially those using EFI bios) occasionally have issues with VMware generated bios (e.g. if boot device order changes, Windows will show the INACCESSIBLE_BOOT_DEVICE error). We are actively working on improving Archiware Pure to work around these problems so your log files will be of great help.

I knew there was something very familiar with this 'invalid configuration for device' error!

I cross checked our previous support tickets and sure enough, there was a very similar error experienced by one of our users. Here is the answer that solved the problem for him:

From what I was able to reproduce in our system, the problem is caused by the VM Video Card having the incorrect setting for videoRamSizeInKB. Your vCenter reports this value to be 0 (for several VMs, not only this one) and so this is the value that Pure uses for restore. According to the VMware documentation, this value does not need to be set so having it set to 0 should not be a problem.

Although you seem to be using the latest vSphere version, the issue is very similar, at least in the effects, to the one described here:
https://kb.vmware.com/s/article/65205

Changing the videoRamSizeInKB value from 0 to 4096 resolves the problem in our test system.

Try changing this value in VMware GUI and do another backup so that Pure can pick up the updated VM info. If the restore still doesn't work, please send me the '/var/log/vpxa.log' file from the ESXi host you are trying to restore the VM to.