Veeam 4.0 Backup failure after upgrade

[tflan81]

Since I upgraded to 4.0 my backup jobs are failing. I get the following error:

Analyzing object "Filesrv"
Failed to login to "192.168.1.8"(ESX 3i, 3.5.0) by SOAP, port 443, user "root", proxy srv: port:0
Unable to connect to the remote server
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 192.168.1.158:8080

Backup mode: Network Backup
Enable VEEAM VSS integration is enabled

I confirmed the root password on both ESX hosts and it matches the SOAP connection credentials in the Veeam software.
Server -> Properties -> SOAP Connection

This started occurring immediately after the upgrade.

[Gostev]

Strange port number for ESX host there. Can you please logon to Veeam Server using the same credentials used by Veeam Backup and FastSCP service, and see if you can open http://192.168.1.158/mob? If this fails, correct the Internet Options for this account in Windows settings until you are able to connect.

We had certain architecture changes in v4 which made the service account more "involved" in the backup process, so while v3 could work with the same account, v4 may not work with it without making some changes.

If you need any assistance, don't hesitate to contact our support at support@veeam.com.

[tflan81]

It appears that was the problem. I logged out of the Veeam Server and logged back in using the same credentials used in the Veeam Backup and FastSCP service.

The backup did not fail but now it seems to hang. Actually, I can't tell if it's hanging. It's been close to 2 hours on the first (of eight) VM's. The statistics show the following:

0 of 0 files processed

Total VM size: 15.02 GB
Processed size: 0.00 KB
Processing rate: 0 KB/s
Backup mode: agentless
Start time: 10/29/2009 10:35:57 AM
Time remaining: 00:00:00

Constructing rollback file name

[Gostev]

Thanks for letting us know the resolution for original issue.

As for the second issue, could it be the v3 storage upgrade issue from the stickied thread about upgrade for v3?
Please contact our support to obtain the fix.