Salta al contenuto principale

compatibility with VMware 5.5

Thread needs solution

Hi,

Just wondering if there is any timeline about testing VMP9 compatibility with Vmware vsphere 5.5?

Thanks,
Aldous

0 Users found this helpful

Sorry, just realize that sphere 5.5 is not available to the public yet. It was just an announcement. Just ignore me.
Thanks
Aldous

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 22
Commenti: 3800

Hi Aldous,

In fact we do have plans to support vSphere 5.5 once it is released and since we are VMware partners - we have access to beta test of vSphere 5.5 to ensure compatibility of our products (not only vmProtect, but ABR as well).

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

We have plans to update our servers to 5.5 next week, is VMprotect 9 ready to support this?
Thanks you.
Carlos.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 22
Commenti: 3800

Hi Carlos,

The testing of vmProtect 9 vs vSphere 5.5 is still ongoing, so it's early to make the final conclusion. What we have confirmed for sure is that backup+restore functionality does work on the released build of vmProtect 9 on vSphere 5.5. I assume that other functionality also won't be affected, but before stating that we need to complete the full test pass. The other tests are time consuming and I'll update the thread once we manage to complete them (this won't happen within a week - likely 2-3 weeks).

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Configuration backup does NOT work with 5.5:

Fehlercode: 37
Module: 458
Zeileninfo: 268dac6975739e9c
Felder:
Nachricht: Ein Backup der ESXi-Version 5.5.0 wird nicht unterstützt.

When can we expect a beta or test version for 5.5?

Replication does not work either:

Fehlercode: 133
Module: 83
Zeileninfo: c7610e0a857bedc1
Felder:
Nachricht: Erwarteter Task 'CreateSnapshot' fehlgeschlagen. Ursache: SOAP-Fehlercode: '28', Beschreibung: 'Host not found', Detail: 'get host by name failed in tcp_connect()'.
--------------------'.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 22
Commenti: 3800

Hi Tinus,

The ESXi configuration backup is likely to stop working with vSphere 5.5 since this functionality works through relatively non-commonly used API which may be changed in vSphere 5.5 as opposed to common vStorage API (used for usual VM backup). We are aware of this issue and will fix it in an update for vmProtect 9. This is pending to be released in the end of this year (that's the current plan).

What concerns replication failure - it looks more like a DNS problem, where the address of the ESXi host provided from vCenter cannot be resolved to IP address from vmProtect Agent (appliance) - likely there is a name resolution issue due to non-configured DNS settings on the vmProtect appliance side. To check it you can ping the ESXi hosts (source and target used during replication) via host names from the command prompt of appliance console opened in vSphere client (to switch to command prompt press Ctrl+Shit+Alt+Space+F1, then Alt+F2).

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Vasily,

We've started the update on our testing enviroment today.
Will you please, inform us as are the tests?
We have special interest in backup vmdks with more of 2tb.

Thanks you in advance,
Carlos.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 22
Commenti: 3800

Hi Carlos,

The .vmdks with more than 2TBs should be processed properly as the 2TB limitation was on lower level than the vStorage API. I'm also attaching the preliminary testing table of the tests which we performed with vSphere 5.5. As you can see the ESXi configuration backup so far is the only feature that doesn't work on vSphere 5.5.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Allegato Dimensione
140905-109882.png 25.38 KB

Vasily, it's not a DNS problem. I can ping both machines. DNS is configured correctly.
It was working in the same configuration with vSphere 5.1. Now both hosts are updated to 5.5. Everything is working expect vmProtect.

That's the error in vSphere:
Ausführen der Replikationsaktion fehlgeschlagen.
Kann Maschine '52F05F49-52D2-9FD8-EC37-70CF637830F3' nicht zu 'SBS 2008 PE2600_vmpreplica' replizieren.
Kann Maschine '52F05F49-52D2-9FD8-EC37-70CF637830F3' nicht als Quellmaschine zum Kopieren erhalten.
Kann einen Accessor der virtuellen Maschine 'SBS 2008 PE2600' nicht erstellen.
Aufrufen der Funktion fehlgeschlagen.
Öffnen der virtuellen Maschine fehlgeschlagen ([DataStore2k] SBS 2008 PE2600/SBS 2008 PE2600.vmx).
Erwarteter Task 'CreateSnapshot' fehlgeschlagen. Ursache: SOAP-Fehlercode: '28', Beschreibung: 'Host not found', Detail: 'get host by name failed in tcp_connect()'.

Thanks
Martin

Vasily,

Then if I understand correctly, the problem is in the VMProtect storage (maximun 2tb) no?
Has Acronis plans to support large storages?
Thanks for testing table.
Thanks you again,
Carlos.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 22
Commenti: 3800

Tinus wrote:

Vasily, it's not a DNS problem. I can ping both machines. DNS is configured correctly.
It was working in the same configuration with vSphere 5.1. Now both hosts are updated to 5.5. Everything is working expect vmProtect.

That's the error in vSphere:
Ausführen der Replikationsaktion fehlgeschlagen.
Kann Maschine '52F05F49-52D2-9FD8-EC37-70CF637830F3' nicht zu 'SBS 2008 PE2600_vmpreplica' replizieren.
Kann Maschine '52F05F49-52D2-9FD8-EC37-70CF637830F3' nicht als Quellmaschine zum Kopieren erhalten.
Kann einen Accessor der virtuellen Maschine 'SBS 2008 PE2600' nicht erstellen.
Aufrufen der Funktion fehlgeschlagen.
Öffnen der virtuellen Maschine fehlgeschlagen ([DataStore2k] SBS 2008 PE2600/SBS 2008 PE2600.vmx).
Erwarteter Task 'CreateSnapshot' fehlgeschlagen. Ursache: SOAP-Fehlercode: '28', Beschreibung: 'Host not found', Detail: 'get host by name failed in tcp_connect()'.

Thanks
Martin

Martin, in our tests the replication worked properly with vSphere 5.5 so it must be something specific in your setup. The problem according to the log file is in the name resolution from vmProtect Agent side, i.e. it cannot resolve the name of the ESXi host to its IP address. Can you please send me a screen shot of the ping attempt (from appliance side) + screen shot of how the hosts are configured in vCenter (of vSphere client) in a private message so that I can advise you further?

This night, the replication was successful. I have not changed anything. Will have an eye on it.

Thanks for helping.

Regards
Martin

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 22
Commenti: 3800

Carlos Segura wrote:

Vasily,

Then if I understand correctly, the problem is in the VMProtect storage (maximun 2tb) no?
Has Acronis plans to support large storages?
Thanks for testing table.
Thanks you again,
Carlos.

The maximum size of the disks attached to vmProtect Virtual Appliance is still limited to 2TB which is basically a MBR limitation rather than vSphere one, since appliance can write backups to MBR disks only (assuming locally attached disks only of course). We do have plans to increase this limit and support GPT disks attached to appliance in 10th version of vmProtect, though the final scope is not yet defined. The alternative is to attach such large disks to some Windows machine and install vmProtect Windows Agent there which doesn't have such limitations.

Hi all,

let me comment this thread regarding the 2TB limit of VMware *.vmdk files and e.g. the error "File is larger than the maximum size supported by datastore" reported by vmProtect (Version 8 on a ESXi 5.1.0). (Sorry but I found the informations in this thread a little bit confusing. First you were talking about VMDK files and 2TB limit. But at the end of this thread you're talking about the 2TB regarding the max HDD size supported.)

So here's my experience regarding VMDK size > 2TB.

- I increased one of my VM's by mistake to 2,02 TB. ( VMware ESXi 5.1.0)
- Due to ESXi limits of taking snapshots of vmdk's > 2TB the vmProtect 8 backup now failed.
- Shrinking the virtual disk size in a ESXi Essential is somehow not so easy! Very complicated or/and time consuming.
- I read, that ESXi 5.5 now supports files up to 64TB.

So I called hotlines at VMWare, Acronis and Dell:
- Somehow there was no 100% answer at all of them ;-) But everyone assumed that this might work.

So long story short. After upgrading to ESXi 5.5 and vmProtect 9 there are no errors reported any more. Backup finishes with a vmdk file larger 2TB.

Hope this helps somebody who might be in the same situation like I was.

Greetings, FS