Exchange Server

alanocguy · Guest

I am looking for information on ownership of resources. I always thought the
active node is supposed to own resources in both the cluster group, as well
as the exch application group.

However i have a client (active/passive 2 node cluster) that failed over to
node B yesterday due to mail traffic issues. SMTP outbound traffice was
getting stuck in the queue. Also outbound mail to their old exch2k3
(standalone server) wasn't going through either. Mail from the old server to
the cluster came through just fine, however (all servers are in the same org,
same RG and admin group).

Here's my question(s):
I am onsite now and i see that the active node (B) owns resources in the
Exch app group, but the cluster group resources (include the quorum) are
still owned by the other node (A). Is this okay?
Also, as for the mail traffic issue on node A, does anyone have suggestions
on how to best troubleshoot that?

Thanks,
Alan

alanocguy · Guest

Hi Seth,
Sorry I wasn't specific about the failover in my post. Yes, the mail went
through just fine when failed over to Node B. Whenever it was failed back to
A (for testing, troubleshooting, etc), we had the same problem. Most of the
day we just left it on B so the mail would go through. Towards the end of the
day, after not making much headway in diagnosing the problem on Node A, we
rebooted A. That resolved the mail flow issue on Node A. However, I'd still
like to know why it happened -- I wouldn't want to tell the client to just
reboot the Node if it happens again.
As for the event logs prior to failing over to Node A, I will try to get
access to them and paste them here.
Thanks for the response!

seth · Guest

first, it's fine that the second node is controlling the exchange group; i'd
say leave that the way it is at the moment until you find out what your
exchange issue is.

second, i have a some questions of my own.

1) does the mail still get 'stuck' when running on node b?

2) what errors are occuring prior to the failover (event logs)?
specifying any event id's or even pasting the error here would help greatly
in identifying the problem

	Exchange Server Forum Index -> Connectivity	All times are GMT
Page 1 of 1