Exchange AIR Wizard - Unable to access mailbox

[mjgreen81]

Hi all,

Recently I had to recreate our SureBackup jobs for Veeam Air due to a problem with the vlab.

I seem to have most things working now but have hit a snag when trying to run the Exchange AIR Wizard.

When running through the Wizard I hit the error:

_______________________________________

Microsoft Exchange AIR Wizard

Unable to access mailbox:

The remote server returned an error: (503) Server Unavailable

_______________________________________

As I say, I have had this working in the past but since recreating the vlab, application groups etc I have hit this problem.

Any help appreciated.

[foggy]

Might be a silly question, but are DC and Exchange in the vlab up and running and reachable from the machine you're running AIR Wizard on (by their masquerade IP addresses)?

[mjgreen81]

Not a stupid question at all! Can you confirm how I can test this?

[foggy]

You can check the masquerade subnet address in the virtual lab settings and try to ping the VMs in the lab.

[mjgreen81]

Ok great, I am just launching the job now (normally takes around 20 mins until its ready) and will post back shortly

Thanks for your help

[mjgreen81]

Ok, my DC and Exchange server are now up and running in the vLab.

I am still a bit confused about how I ping the servers within the vLab as dont they have the same IP address as my live production server?

Oh, and the Masquerade network address in the vLab is shown as 172.31.4.D

Sorry if I am being a bit dunce about this. I taught myself all this stuff when I configured the surebackup jobs around a year a go and seem to have forgotten most of it

[foggy]

The masquerade IP address resembles the IP address in the production network: for example, if the IP address of a VM is 172.16.4.13, the masquerade IP address may be 172.31.4.13.

[mjgreen81]

Ok, I re-entered my vlab details and it automatically changed the masquerade IP to 172.30.4.D.

I ran through the process again and noticed that my 'BACKUP CAS' was listed as 172.30.4.24 (my production mail server is 172.16.4.24).

I tested that I could ping 172.30.4.24 from the server where I have the AIR wizard running and can confirm that I can ping it.

However, I still get the error:

Unable to access mailbox:

Unable to connect to remote server

(which is slightly different to before)

[Vitaliy S.]

Hello Mike,

Are you using Exchange 2007 in your environment? Have you reached our support team to review the debug log files?

Thank you!

[mjgreen81]

We are using Exchange 2003, no I have not contacted support yet as when I previously had AIR working this forum was a great source of information and managed to help me with any problems.

[foggy]

Probably the most efficient way would be to contact them, since the exact reason of the connection failure can be identified by reviewing the logs.

[mjgreen81]

Hi all,

Sorry to bring this one back from the dead....

I contacted support and their advice was to update to Veeam 6.5 (we were running 6.1). Due to the Christmas rush I was unable to do this until yesterday.

We are now on the latest version of 6.5 (with Patch 3) but still get the problem (although the error message is slightly different):

"Unable to access mailbox:

The underlying connection was closed: An unexpected error occurred on the receive"

Whilst I am waiting for support to respond, I just wondered if anyone here had any further thoughts as to what might be causing this problem?

Thanks

[mjgreen81]

Just as a quick update to this (I am currently waiting to hear back from support)....

I have noticed that although my DC & Exchange VM's are booting up inside the vLab, hey are running ridiculously slowly. For example I attempted to log on to my Exchange server and it took around 30 minutes in total. I have also noticed in vSphere that these VM's keep warning of disk latency issues.

Hopefully support will be able to pin down why this is happening. As mentioned before, I have had SureBackup Exhange-AIR working well in the past so I know it can work successfully on my system!

[Vitaliy S.]

Hi Mike, what is your repository? Is it a dedupe device by any chance?

[mjgreen81]

Hi Mike, what is your repository? Is it a dedupe device by any chance?

Im sorry but I don't know what that is - cam you explain please?

[Vitaliy S.]

What server do you use as a backup repository? Just a Windows Server? Datadomain? any other NAS?

[mjgreen81]

Just a Windows Server with some large shared drives.

[Vitaliy S.]

Since you're saying that you observe high latency on the vPower NFS storage, then the issue might be in the target storage (Windows Server with shared drives). I would also investigate SB job log file to see what operation takes most of the time. Do you have a possibility to test your backups (run Exchange AIR) on the some other storage?

[mjgreen81]

I dont think I have any other storage I can use.

The strange thing is, I have had this working without a problem in the past with the same setup.

However, I had a problem with my vlab so had to recreate the vlab, application groups and surebackup jobs. Ever since then it just has not worked properly.

[Vitaliy S.]

Well...it's hard to argue with latency issues reported by the vCenter Server, but let's see what our support can say after reviewing full log files.