Windows 2003 clustering issue with Exchange 2007 (0/1)

Nick · Joined: 09 Jan 2008 Posts: 8

Hi

We have a 2 node Windows 2003 cluster ( MNS quorum ) running Exchange
2007. I have noticed that the "Cluster Group" failover times vary on
each node, one takes a few seconds, the other takes approx 1 minute
and generated a "windows write delay" error as below.

I have the MNS shared out successfully on the Hub Transport server.

Can anyone advise how to solve this.

Thanks

Nick Thompson

Archived from group: microsoft>public>exchange>clustering

Edwin vMierlo [MVP] · Joined: 05 Aug 2007 Posts: 18

"Nick" wrote in message@4ax.com...
> Hi
>
> We have a 2 node Windows 2003 cluster ( MNS quorum ) running Exchange
> 2007. I have noticed that the "Cluster Group" failover times vary on
> each node, one takes a few seconds, the other takes approx 1 minute
> and generated a "windows write delay" error as below.
>

Please post the error, although there should not be a write delay error, as
you cluster group should not contain any disk resources
rgds,
edwin.

Oliver Moazzezi [MVP] · Joined: 02 Oct 2007 Posts: 583

Do you only get the one write delay? Or is this continuous?

Oliver

Nick · Joined: 09 Jan 2008 Posts: 8

Hi Oliver

The write delay error only seems to happen when one of the nodes is
rebooted, we havent had any issues with the database disks. Just want
to make sure the cluster and Exchange is good before migrating user.

Thanks

Nick

On Mon, 21 Jan 2008 13:35:05 -0000, "Oliver Moazzezi [MVP]"
wrote:

>
>Do you only get the one write delay? Or is this continuous?
>
>Oliver
>

Nick · Joined: 09 Jan 2008 Posts: 8

Hi Edwin

I have already posted the errors. It is an event ID 50 error, the
error seems to appear when either of the nodes are rebooted.

I want to make sure that the server is good before migrating users.

Thanks

Nick

On Mon, 21 Jan 2008 10:15:28 -0000, "Edwin vMierlo [MVP]"
wrote:

>
>"Nick" wrote in message
>@4ax.com...
>> Hi
>>
>> We have a 2 node Windows 2003 cluster ( MNS quorum ) running Exchange
>> 2007. I have noticed that the "Cluster Group" failover times vary on
>> each node, one takes a few seconds, the other takes approx 1 minute
>> and generated a "windows write delay" error as below.
>>
>
>Please post the error, although there should not be a write delay error, as
>you cluster group should not contain any disk resources
> rgds,
>edwin.
>

Oliver Moazzezi [MVP] · Joined: 02 Oct 2007 Posts: 583

The only time i've seen write delays has been in the lab. The cluster was a
VM and it was a disk configuration issue within ESX.

I would call PSS, or revert your updates (did the version of storport.sys
change?) and see if the issue is removed.

Oliver

Nick · Joined: 09 Jan 2008 Posts: 8

Thanks for the reply. The issues appear to be with crs.log which I
presume is on the HUb Transport share for the MNS quorum. When a node
is rebooted you get a popup message saying write delay error to
crs.log.

The cluster does failover successfully and Exchange does work fine.

I havent had any issues with the data. I just want to be sure
everything is good.

We have had this issue for some time.

Nick

On Mon, 21 Jan 2008 18:35:59 -0000, "Oliver Moazzezi [MVP]"
wrote:

>The only time i've seen write delays has been in the lab. The cluster was a
>VM and it was a disk configuration issue within ESX.
>
>I would call PSS, or revert your updates (did the version of storport.sys
>change?) and see if the issue is removed.
>
>Oliver
>

Edwin vMierlo [MVP] · Joined: 05 Aug 2007 Posts: 18

Nick,

didn't see those until now.

As you can see this is indeed something with your network/share, as the
Event ID 50 complains about \Device\LanmanReDirector. Sot this is a Delayed
Write Failed, but not on a local disk.

Can you check that in your cluster, for both (!) Private and Public
Networks, in TCP/IP you have enabled "Client for Microsoft Network"

thanks,
Edwin.

"Nick" wrote in message@4ax.com...
> Hi Edwin
>
> I have already posted the errors. It is an event ID 50 error, the
> error seems to appear when either of the nodes are rebooted.
>
> I want to make sure that the server is good before migrating users.
>
> Thanks
>
> Nick
>
>
> On Mon, 21 Jan 2008 10:15:28 -0000, "Edwin vMierlo [MVP]"
> wrote:
>
> >
> >"Nick" wrote in message
> >@4ax.com...
> >> Hi
> >>
> >> We have a 2 node Windows 2003 cluster ( MNS quorum ) running Exchange
> >> 2007. I have noticed that the "Cluster Group" failover times vary on
> >> each node, one takes a few seconds, the other takes approx 1 minute
> >> and generated a "windows write delay" error as below.
> >>
> >
> >Please post the error, although there should not be a write delay error,
as
> >you cluster group should not contain any disk resources
> > rgds,
> >edwin.
> >

Exchange 2007 SP1 SCR on Windows 2003 Hi I am currently looking into utilising Exchange 2007 SP1 SCR to provide recovery at our D.R site. We currently have 2 x two node Exchange 2007 SP1 clusters (MNS Quorum) running on Windows 2003 R2 with SP2. I have enabled the appropriate storage groups f

Shutting down an A/A/P Windows 2003 / Exchange 2007 We are having a power outage this weekend, I need to shutdown the entire cluster. We have an Windows 2003 SP2 / Exchange 2007 cluster. Do I do the following: 1st shutdown passive node 2nd - shutdown active node - At this point will t

Clustering in Exchange 2007 I know in Exchange 2007 the mailbox-role servers have to have only that role to enable Exchange clustering. My question is how would one go about providing redundancy for the rest of the system. i.e. the Edge-role server and the multi-role server? Can th

Exchange 2007 Clustering Hi, Please send me a complete step by step guide to cluster exchange 2007. Thanks Neeraj Mehra

Exchange 2007 Clustering Hurdle All, I'm working on building a 3 node SCC Cluster (AAP) and having a bit of a hard time getting the active node to install properly. I've followed all the best practices in setting the cluster nodes up, setting up the Quorum and shared drives (without Wr