Re: is data mirroing online? exchange2003 cluster

From: Matthew Byrd [MSFT] (matbyrd_at_online.microsoft.com)
Date: 06/17/04


Date: Thu, 17 Jun 2004 12:16:59 -0400

Hi Eric,

First Microsoft does not recommend an A/A configuration as it has
limitations that the A/P configuration does not. These are outline in the
cluster doc.

With that said it appears that some additional information on How cluster
works would help to clarify things.

Windows Cluster does NOT replicate exchange data in any way manner or form.
What you do is setup a set of shared disks that are connected to two
physical Servers. Only ONE of the servers can access a given set of shared
disk at one time. What you gain with a cluster is protection against
hardware failure with the server hardware. You can also get some gains in
doing updates and maintenance to the software as you can do the maintenance
on the passive node then fail over.

So in an A/P configuration this is how a failover would occur.

Node A is currently active and running Exchange
A hardware Failure occurs on Node A
Node B determines that Node A has gone offline
Node B takes over the shared disks and starts brining Exchange back online
On Node B Exchange Does a soft recovery and brings the (Exact same) database
online
Users are now able to connect again

This scenario is EXACTLY the same in an A/A configuration except that after
the failover there would be two Exchange Virtual servers running on the same
physical Box. Each Exchange Virtual Server in an A/A configuration has its
own databases, its own separate shared disks, and its own set of users.

Hopefully this has addressed your question

-- 
Matthew Byrd
Microsoft PSS
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
"eric romero" <e.romero@cgnet.com> wrote in message 
news:eT%23uEV%23UEHA.2972@TK2MSFTNGP11.phx.gbl...
> Hi Matthew,
>
> That document  does not explain what do they do to keep exchange database
> synchronized in an active/active configuration.
>
> Do you know if in active/active "some mechanism" replicates "all the time"
> data from NodeA to NodeB, so in the vent of NodeA going offline then NodeB
> takes place? and also I do not understand why do they alert on number of
> storage per server..is it that NodeB and NodeA can have diffente number of
> staorages? should not they be two identical servers/databases/paths.
>
> thx
>
> "Matthew Byrd [MSFT]" <matbyrd@online.microsoft.com> wrote in message
> news:ODnVUr9UEHA.2816@TK2MSFTNGP11.phx.gbl...
>> Hi Eric,
>>
>> From your post it appears that you are looking for an Exchange High
>> Availability solution but that you are not clear on what clustering does
> to
>> assist that.
>>
>> I would recommend taking a look at the following whitepaper I think it
> will
>> answer many of your High Availability questions:
>>
>> Exchange Server 2003 High Availability Guide
>>
> http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/highavailgde.mspx
>>
>> Hope this Helps,
>>
>> -- 
>> Matthew Byrd
>> Microsoft PSS
>>
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>>
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>>
>> "eric romero" <e.romero@cgnet.com> wrote in message
>> news:%23H8k1B9UEHA.2544@TK2MSFTNGP10.phx.gbl...
>> > Hi all,
>> >
>> > Could you please tell me and show me some documents that explains what
>> > happens with the exchange databases on an Exchange2003 cluster (2 
>> > nodes)
>> > config?
>> > I am interested to know if we can have 2 nodes each node with its own
> hard
>> > disks and data from active server is copying online to the standby
> server
>> > so
>> > it is ready to serve the clients if the active node fails.
>> >
>> > Is it true that on active/pasive I can have just 1 place to install the
>> > exchange databases, what happens if this "shared disk" fails? what is
> the
>> > cluster useful for at thismoment?
>> > on active/active I think I can have both server available at any time,
> how
>> > are the exchange databases synchronized? or is it in active/active that
>> > you
>> > set some mailboxes to be serverrd by node1 and the rest by node2, is
> this
>> > is
>> > the case what if one of the nodes fail?
>> >
>> > thx
>> >
>> >
>>
>>
>
> 


Relevant Pages

  • Re: setup custer - one node already in production
    ... First, in a single-instance configuration, you only have to license the ... some installations beef-up the passive node to be able to ... To run SQL Server 2000 x86 editions, unfortunately, you can only run on up ... 8-node cluster configurations are supported. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Exchange 2007 SP1 Standard Edition - SCR on a Windows 2003 Clu
    ... Mailbox roles and manually start Exchange ... services in case a windows cluster fail-over occurs (Windows cluster active ... active node as an SCR source and the passive node as an SCR target? ... the windows cluster so that they don't have to change Exchange server IP/name ...
    (microsoft.public.exchange.setup)
  • Exchange 2007 cluster install - interesting note on an SCC installation
    ... I got my client/hub server setup just fine, and then when I went to my ... the install was going smoothly but then I noticed in the cluster ... I was using during the Exchange install was 10.40.32.170. ...
    (microsoft.public.exchange.setup)
  • Re: Exch 2003 SP2 - applied on one node, but cant move resources
    ... resources to Node2, the failover did not complete because 'system attendant' ... Virtual Exchange server and failover occurred normally again upon taking ... cluster resources oline. ...
    (microsoft.public.exchange.admin)
  • Re: Exch 2003 SP2 - applied on one node, but cant move resources
    ... only upon taking the resources "offline" in the Cluster administrator tool. ... Virtual Exchange server and failover occurred normally again upon taking the ... We recommend that you upgrade one Exchange cluster node at a time. ...
    (microsoft.public.exchange.admin)