Skip to main content

Failed to Open Virtual Machine

Thread needs solution

We are running on agent less Acronics 11.7 and able to take back up of virtual machines using virtual applience.  Our Esxi host is running onV5.5.

Backup is working without any issue but i am unable to restore machine directly from Acronis management console. 

It is giving error Failed to open virual machine while creating recover task.  

Giving following errors. I am using vcenter admininistrator with full access to Esxihost to recover machine still it is giving acces erros. 

-----------------------------------------------------------------------------------------------------------
Error
-----------------------------------------------------------------------------------------------------------
Failed to open the virtual machine.
-----------------------------------------------------------------------------------------------------------
Details:
    Code: 11,141,162(0x00AA002A)
<u>LineInfo:</u> 0xACBE64BF5E29CF1F;

    Module: console_virtual_machines_vs_44367
    Message: Failed to open the virtual machine.

    Code: 9,764,912(0x00950030)
<u>LineInfo:</u> 0xE64F8AC0F3F921CB;

    Module: disk_bundle_tape_off_glx_pic_44367
    Message: Cannot open emulated machine.

    Code: 9,764,877(0x0095000D)
<u>LineInfo:</u> 0xD1AB7FA1E56EC83E;

    Module: disk_bundle_tape_off_glx_pic_44367
    Message: Failed to perform the requested operation.

    Code: 1,048,812(0x001000EC)
<u>LineInfo:</u> 0x7BB42EFE3C733241;

    Module: disk_bundle_tape_off_glx_pic_44367
    Message: Internal error: Attempt to access emulated disk for non-initialized object.

    Code: 5,439,511(0x00530017)
<u>LineInfo:</u> 0xC61573F663F5D8D6;

    Module: esx_srv_glx_pic_44367
    Message: Failed to get access to hard disk '[ESXIPROD03:datastore1] STADUAL02/STADUAL02_1-000001.vmdk'.

    Code: 5,439,582(0x0053005E)
<u>LineInfo:</u> 0xC61573F663F5D85F;

    Module: esx_srv_glx_pic_44367
    Message: Failed to open virtual disk file '[ESXIPROD03:datastore1] STADUAL02/STADUAL02_1-000001.vmdk'.

    Code: 13(0x0000000D)
<u>LineInfo:</u> 0xC61573F663F5D75D;

    Module: esx_srv_glx_pic_44367
    Message: You do not have access rights to this file

-----------------------------------------------------------------------------------------------------------
 

 

 

 

 

 

 

1 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Dave,

The typical reason for such problems is missing network route between the appliance and particular ESXi host "management network" interface. You need to make sure the following:

1) The vSwitch port group where virtual appliance is connected has network route to management network of the ESXi host where you try to perform VM recovery

2) Make sure that the virtual appliance can resolve the ESXi _hosts_ (not only vCenter but underlying hosts as well) names to IPs if these hosts are registered under vCenter using hostnames. To check that you can open appliance console in vSphere client -> press Ctrl+Shift+F2 to switch to command prompt -> issue "ping [ESXi_host]" command. If pinging doesn't get through then switch back to appliance GUI via Alt+F1 and check the DNS settings.

If the above doesn't help please contact our support team for further assistance.

Thank you.

Thanks Vasily

From virtual appliance console I can ping everywhere i.e to Esxi host and all virtual machines. Ping from management to other network is working. 

We can take backup of any machine  from Acronis management center. 

I have given all access to Acronis user in Vcenter. 

Appriciate if you have can share any other idea or do you reccommned to contact support team ? 

 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Dave,

Yes it makes sense to contact our support team for further assistance with the issue. The possible temporary workaround for the recovery issue (if you need to restore right now) would be to use Acronis Backup bootable media, i.e. create an empty VM->boot it from Acronis Backup bootable media -> run recovery wizard and proceed from there.

Thank you.

Actually, I have 2 on-premise solutions (2 different customers) where the agent can ping vcenter and ESXi but can't resolve by name. And the backup process is without any problem...

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Olenka Moreno Acosta wrote:

Actually, I have 2 on-premise solutions (2 different customers) where the agent can ping vcenter and ESXi but can't resolve by name. And the backup process is without any problem...

Hi! Do you receive any error message or the issue with the DNS doesn't affect any operations with backups?

Ekaterina wrote:
Olenka Moreno Acosta wrote:

Actually, I have 2 on-premise solutions (2 different customers) where the agent can ping vcenter and ESXi but can't resolve by name. And the backup process is without any problem...

Hi! Do you receive any error message or the issue with the DNS doesn't affect any operations with backups?

I realized it doesn't affect when the Management Server is in the same network segment of AD/DNS, because I have another solution, where the backup network and DNS network are different, and if I did not indicate the IP of the DNS in the agents, the backups would not be carried out

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 0
Comments: 2016

Hello Olenka.

Your hosts are added to vCenter by their IP addresses. That is why Acronis Backup Appliance receives addresses from vCenter by IP addresses. It is good for small environments. However, for large environments, it is recommended to add hosts to vCenter using hostnames.