Exchange 2007 CCR after reseeding storage group copies

[QH]

We have an Exchange 2007 CCR cluster that sits on two Windows Server
2008 Enterprise nodes. Due to problems with one node, I evicted it
from the cluster and rebuilt it, reinstalling Exchange using the
custom / install passive node setup. I used 'Update Storage Group
Copy' (with the option selected to 'Delete any existing log files in
the target path') to reseed the active databses. It seemed to go OK,
and the storage groups status in the Database Management window became
'healthy'. However, when I tried to move the clustered mailbox server
on to the new node for test purposes, it failed with this message:

The version on the target node is not compatible with the version on
the source node. The source (Node1) version is 8.2.176.2, and the
target (Node2) version is 8.1.240.6.

Googling this does not bring anything up, in fact I am not even sure
if the 'version' it refers to is the copy of the database or the
patches / updates for Exchange itself. Has anyone else re-added a w2k8
\ exchange 2007 node, and can tell me how to get around this problem?

Thanks,

QH

[Ed Crowley [MVP]]

Apply SP2 to the passive node like it's apparently applied to the active
node.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
.

"QH" <quenti...@hotmail.com> wrote in message
news:dadb3235-5baa-46c7...@l2g2000yqd.googlegroups.com...

[QH]

Yes, you are entirely correct. I thought this myself after I left work
and was walking home, and was suitably embarrassed. Thanks for the
advice. However, even though I have been able to re-add the second
node to the cluster, the public folder services are never failing
over. Why is this? Could it be due to the fact that we still have
users and public folders on an Exchange 2003 server that is yet to be
decommissioned?

Thanks,

QH

On 14 Nov, 07:11, "Ed Crowley [MVP]" <cursp...@nospam.net> wrote:
> Apply SP2 to the passive node like it's apparently applied to the active
> node.
> --
> Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> .
>

> "QH" <quentinhud...@hotmail.com> wrote in message

>
> news:dadb3235-5baa-46c7...@l2g2000yqd.googlegroups.com...
>
>
>
>
>
> > We have an Exchange 2007 CCR cluster that sits on two Windows Server
> > 2008 Enterprise nodes. Due to problems with one node, I evicted it
> > from the cluster and rebuilt it, reinstalling Exchange using the
> > custom / install passive node setup. I used 'Update Storage Group
> > Copy' (with the option selected to 'Delete any existing log files in
> > the target path') to reseed the active databses. It seemed to go OK,
> > and the storage groups status in the Database Management window became
> > 'healthy'. However, when I tried to move the clustered mailbox server
> > on to the new node for test purposes, it failed with this message:
>
> > The version on the target node is not compatible with the version on
> > the source node. The source (Node1) version is 8.2.176.2, and the
> > target (Node2) version is 8.1.240.6.
>
> > Googling this does not bring anything up, in fact I am not even sure
> > if the 'version' it refers to is the copy of the database or the
> > patches / updates for Exchange itself. Has anyone else re-added a w2k8
> > \ exchange 2007 node, and can tell me how to get around this problem?
>
> > Thanks,
>

> > QH- Hide quoted text -
>
> - Show quoted text -

[Ed Crowley [MVP]]

What happens? Anything in the event log? Any error messages?

Be aware that hosting public folders on a CCR cluster is not supported
unless it's the only public store in the organization. Not because it won't
fail over, but because you can have a race condition with updated data
resulting in potential data loss associsted with a failover.

--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
.

"QH" <quenti...@hotmail.com> wrote in message
news:60373f82-4ec3-41f9...@u7g2000yqm.googlegroups.com...