-
- Influencer
- Posts: 15
- Liked: never
- Joined: Mar 10, 2010 1:01 am
- Full Name: Dan
- Contact:
Issue after upgrade to ESX 4.1
Hi,
I have posted a support case to support@veeam.com
Scenario - we have just upgrade our replication target host from Vmware 4.0 to 4.1 (re-install rather than upgrade via the VI Client) and changed over the network adapters (so new NICs/MAC address) everything went fine we re-connected the VMFS partitions and re-added the VMFS partitions which was fine replicated vms where all there, so in our veeam server we kicked off the replication jobs which then errored immediately with the error "failed to login to "10.1.70.200" by SOAP, port 443, user "root", proxy srv: port:0 input string was not in a correct format... I m guessing either the upgrade of the version or the change of service console/physical NIC has affected the mapping to host...???
we have kept the root password the same, ssh is enabled (tested via putty) and we can browse the host through SCP no problem!! please help the virtual machines are nearly 1 TB in size and i dont want to have to re-replicate them all again
thanks in advance
I have posted a support case to support@veeam.com
Scenario - we have just upgrade our replication target host from Vmware 4.0 to 4.1 (re-install rather than upgrade via the VI Client) and changed over the network adapters (so new NICs/MAC address) everything went fine we re-connected the VMFS partitions and re-added the VMFS partitions which was fine replicated vms where all there, so in our veeam server we kicked off the replication jobs which then errored immediately with the error "failed to login to "10.1.70.200" by SOAP, port 443, user "root", proxy srv: port:0 input string was not in a correct format... I m guessing either the upgrade of the version or the change of service console/physical NIC has affected the mapping to host...???
we have kept the root password the same, ssh is enabled (tested via putty) and we can browse the host through SCP no problem!! please help the virtual machines are nearly 1 TB in size and i dont want to have to re-replicate them all again
thanks in advance
Re: Issue after upgrade to ESX 4.1
Hello Dan,
Which version of Backup and Replication are you using? ESX 4.1 is only supported with Veeam B+R v4.1.2.
Which version of Backup and Replication are you using? ESX 4.1 is only supported with Veeam B+R v4.1.2.
-
- Enthusiast
- Posts: 52
- Liked: 2 times
- Joined: Sep 20, 2010 4:39 am
- Full Name: David Reimers
- Contact:
Re: Issue after upgrade to ESX 4.1
I'm getting a similar issue (ESXi 4.1 and VB&R 4.1.2):
Formatting vbk storage
FormatStorage failed
Client error: Cannot authenticate user.
Soap fault. Detail: '', endpoint: ''
Failed to reconnect to storage. Storage: [stg:4c92e94e-f2e3ba58-e94e-00215e73df32,nfchost:ha-host,conn:esxdr.holdfast.sa.gov.au]. Storage display name: [SANRAID6].
Formatting vbk storage
FormatStorage failed
Client error: Cannot authenticate user.
Soap fault. Detail: '', endpoint: ''
Failed to reconnect to storage. Storage: [stg:4c92e94e-f2e3ba58-e94e-00215e73df32,nfchost:ha-host,conn:esxdr.holdfast.sa.gov.au]. Storage display name: [SANRAID6].
Re: Issue after upgrade to ESX 4.1
Hello David,
Please refer to our support team with all technical issues. Our technical team will be able to assist you in resolving the issue after reviewing all the log files.
Thanks!
Please refer to our support team with all technical issues. Our technical team will be able to assist you in resolving the issue after reviewing all the log files.
Thanks!
-
- Chief Product Officer
- Posts: 31749
- Liked: 7253 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Issue after upgrade to ESX 4.1
P.S. Please note that these two issues are absolutely different (for future readers).
Who is online
Users browsing this forum: AdsBot [Google], Bing [Bot], mkretzer, Semrush [Bot] and 124 guests