Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Exchange Server / Clustering / July 2008

Tip: Looking for answers? Try searching our database.

exchange 2003 standby cluster procedures

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Aldous Leung - 10 Jul 2008 22:57 GMT
Hi,

I have two exchange clusters (both two nodes A/P) (one hosting all
mailbox store and one hosting public folders). I would like to build two
single node standby cluster and move both exchange cluster to these
single node (e.g. exc-mbox-vs1 move to exc-mbox-stdby and exc-pf-vs2
move to exc-pf-stdby). I have read the MS exchange deployment guide
about the procedures but I am still confuse. Therefore, I'm hoping to
get some help here. Thanks.

Would anyone verify my procedures below, please?

- On standby, install Win 2003 Enterprise with same patches as in
production cluster (if possible)
- Connect the standby to same network and join to the same domain as
member server
- On standby, Start the cluster admin and "Add" as a cluster node to the
existing production cluster (This is where I am not sure)
- On standby, Create windows cluster's IP (new), network name (new) and
Disk resources (all local disk but matching drive letters as in exchange
production cluster).
- On standby, Install Exchange 2003 and Exchange 2003 SP2 (same in
production)

- Take all Production Exchange Virtual server off line (i.e. all
production clusters should be still running but Exchange VS off line) -
not sure this?
- On standby, create Exchange IP resources (IP address must be the same
as in production exchange cluster)
- On standby, create Exchange Network name resources (Network name must
be the same as in production exchange cluster and "DNS Registration must
succeed" and "Enable Kerberos" check boxes selected)
- On standby, bring "Network name" online
- On standby, create "Exchange System Attendant" resource. Select only
the standby node as possible owner (not sure this?) and all resources
- On standby, bring all resources online
- Copy all database from Production cluster to the standby cluster and
restart all exchange resources to mount the data stores. (I am planning
to direct copy all database from the existing server instead of restore
from backup). Will direct copy work?

In addition, I have another question about the patches:
- I am trying to not to touch my production at all but the Windows OS
patches on the productions are not up-to-date but I can't find all the
patches to install to my standby (maybe some old patches replacement by
others but not installed to my production). If I just install the latest
patches to standby, will this work? (Exchange patches are in SP2 +DST
only and I should be able to make this the same)

Unfortuately, I must complete this on coming weekend, therefore, I have
not way to build anything to test. Please help

Thanks very much,
Aldous
Leif Pedersen [ MVP] - 19 Jul 2008 11:11 GMT
Hi,

Do you add the standby cluster server to the production cluster!!

Leif

> Hi,
>
[quoted text clipped - 50 lines]
> Thanks very much,
> Aldous
Leif Pedersen [ MVP] - 19 Jul 2008 14:40 GMT
Hi,

Meant to say don't add the server to the cluster.

Leif

> Hi,
>
[quoted text clipped - 56 lines]
>> Thanks very much,
>> Aldous
Aldous Leung - 24 Jul 2008 15:29 GMT
Thanks. I added as new cluster and everything is working now.

> Hi,
>
[quoted text clipped - 64 lines]
>>> Thanks very much,
>>> Aldous
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.