VMProtect 8 problem after upgrade
Hello, I have upgraded vmprotect 7 to 8 as windows agent.When I edit existing backup task, step 1 wants configure esx(i)hosts.(sshot-6).But, its already added.Then I have clicked Configure->ESX(i) Hosts, its show localhost esx vcenter.(sshot-7) I removed/added esx(i) hosts several times, same.
What's your suggestions, thanks.
Anhang | Größe |
---|---|
sshot-6.jpg | 75.11 KB |
sshot-7.jpg | 47.66 KB |

- Anmelden, um Kommentare verfassen zu können

Thanks you Anton, I have sent pm.
- Anmelden, um Kommentare verfassen zu können

Hello hbceylan,
Thank you for your response.
After checking the logs I can see the following:
First of all please specify the IPv4 address instead of hostname (STRATOSPHERE.ilab.com.tr) when adding vCenter into vmProtect interface
If that doesn’t help please add the ESX host directly instead of vCenter and see if it works or not.
The error is returned from the ESX host which cannot be contacted by vmProtect Agent with the following error:
<![CDATA[There is no connection to server 'fb5b00f2-891f-414f-8ef3-6e17c3a15d2b'.
Additional info:
--------------------
Error code: 27
Module: 426
LineInfo: cf93a6e1beb0475e
Fields:
Message: There is no connection to server 'fb5b00f2-891f-414f-8ef3-6e17c3a15d2b'.
--------------------
Error code: 32859
Module: 114
LineInfo: cf93a6e1beb04596
Fields:
Message: Failed to get instances from server with ID 'fb5b00f2-891f-414f-8ef3-6e17c3a15d2b' and resource name 'host-49'.
--------------------
Error code: 116
Module: 83
LineInfo: 41aa269c0490627f
Fields:
Message: Failed to get the object's property 'NetworkId'.
--------------------
Error code: 257
Module: 83
LineInfo: 242258ad58c707a2
Fields: faultTypeId : 0
Message: SOAP fault code: '12', Description: 'A general system error occurred: Not initialized', Detail: '<SystemErrorFault xmlns="urn:vim25" xsi:type="SystemError"><reason>Not initialized</reason></SystemErrorFault>'
--------------------]]>
This error may mean that the connection to the host through vCenter cannot be established and therefore you need to connect directly to this host from vmProtect or that the host is in faulty state and you should reboot it (if adding the ESX host directly doesn’t help). If the problem still persists after these steps, please send us the vCenter logs (we need the latest vpxd-xxx.log) from C:\ProgramData\VMware\VMware VirtualCenter\Logs\ folder on vCenter to check the connection state with the ESX host.
Please let me know if you have additional questions.
Thank you.
- Anmelden, um Kommentare verfassen zu können

Or how about adding a static entry on your local host file, that might also do the trick.
- Anmelden, um Kommentare verfassen zu können