> There are 180 users at the site. The remote site is just for backup.There
> are no users there.
>
> Rodney R. Fournier [MVP] wrote:
>> Put in as many DC's as are needed. How many users at each site? You might
>> only need 1 DC at each site, though 2 is always nice to have - just in
>> case.
>>
>> Cheers,
>>
>> Rodney R. Fournier
>> MVP - Windows Server - Clustering
>>
http://www.nw-america.com - Clustering Website
>>
http://msmvps.com/clustering - Blog
>>
http://www.clusterhelp.com - Cluster Training
>> ClusterHelp.com is a Microsoft Certified Gold Partner
>>
>>
>> "Andrew" <andrew[ at ]rd.com> wrote in message
>> news:e1w%23H07wHHA.4544[ at ]TK2MSFTNGP05.phx.gbl...
>>> Rodney,
>>>
>>> Thanks for for detailed response. I just have a question regarding
>>> response:
>>>
>>> 1. If i'm trying to replicate the entire network for redundancy on a
>>> remote site how would the users log on if the domain controller went
>>> down? Are you suggesting two domain controllers at the host site?
>>>
>>> Andrew
>>>
>>> Rodney R. Fournier [MVP] wrote:
>>>> When you say PDC, I am going to assume you mean the FSMO role PDC
>>>> Emulator which runs on a Domain Controller. NEVER CLUSTER A DC. NEVER.
>>>> With that said you don't need to cluster a DC anyway. Just have 2 or
>>>> more, since FSMO roles never automatically transfer. Use AD integrated
>>>> DNS too, so that DNS is available.
>>>>
>>>> 1. Cluster over a WAN? With one node a each location? Only if you have
>>>> third party replication for the shared storage and two SANS. Exchange
>>>> Server 2007 has other options when SP1 comes out, but nothing right
>>>> now. You will need to have under 500ms access times between the
>>>> servers. You will need 2 VLANS for the clustered nodes, one for the
>>>> heartbeat, one for the public traffic. This is a must, same subnet for
>>>> the nodes!!!
>>>>
>>>> 2. If you still have bandwidth available, what else runs on it? Do a
>>>> ping test, and see number 1 for issues.
>>>>
>>>> 3. Exchange can. NEVER CLUSTER A DC!
>>>>
>>>> Hopefully this makes sense.
>>>>
>>>> Cheers,
>>>>
>>>> Rodney R. Fournier
>>>>
>>>> MVP - Windows Server - Clustering
>>>>
http://www.nw-america.com - Clustering Website
>>>>
http://msmvps.com/clustering - Blog
>>>>
http://www.clusterhelp.com - Cluster Training
>>>> ClusterHelp.com is a Microsoft Certified Gold Partner
>>>>
>>>>
>>>> "Andrew" <andrew.smith[ at ]rd.com> wrote in message
>>>> news:%23b9Mq2ywHHA.2304[ at ]TK2MSFTNGP06.phx.gbl...
>>>>> Hi,
>>>>>
>>>>> I've been tasked to set up a PDC/Exchange server that is currently
>>>>> running Windows server 2003 std R2 With a redundancy solution that
>>>>> would involve having another server at a remote site. Whenever the PDC
>>>>> at the host site goes down it must failover to the remote site with
>>>>> minimal fuss.
>>>>>
>>>>> I'm aware that the current setup /software/OS won't work with
>>>>> clustering and wanted to purchase server enterprise edition and
>>>>> exchange enterprise edition at both sites to comply with the
>>>>> requirements of the task.
>>>>>
>>>>> The connection is a 2Mbps bonded ADSL line.
>>>>>
>>>>> I have a few questions about whether the setup would actually work
>>>>> over a WAN cnnection. I've read various documents and articles on the
>>>>> net saying that this is no problem but had a few questions regarding
>>>>> it:
>>>>>
>>>>>
>>>>> 1. Is it possible to cluster a server and exchange 2003 over a WAN
>>>>> connection?
>>>>>
>>>>> 2. Would a bonded 2Mbps ADSL line be enough to allow replication over
>>>>> the WAN link
>>>>>
>>>>> 3. Would a Cluster server do what I want i.e allow the node to
>>>>> failover and allow network users not to notice that the PDC had fallen
>>>>> over?
>>>>>
>>>>> Thanks for any insight anyone can give me into this subject.
>>>>>
>>>>> Andrew
>>>>