© 2005 global knowledge network, inc. all rights reserved. section 2: high availability clustering...

© 2005 Global Knowledge Network, Inc. All rights reserved.

Section 2: High Availability

Clustering Network Load Balancing Geographical Clustering Remote Recovery and Disaster Recovery

Solutions Strategic Authentication and Name Resolution

Ultimate Exchange Server 2003:Heighten Security, Consolidation, and Availability


Section Objectives

After completing this section, you will be able to: Define high availability in a Microsoft Windows

environment Build an Exchange Server 2003 cluster Explain how network load balancing works Formulate a load-balancing solution for Microsoft

Exchange Server 2003 Name third-party software for geographical

clustering Define a remote recovery solution Describe the best practices regarding authentication

and name resolution for Exchange Server 2003

Knowledge Guide

2-2


Availability vs. Reliability

Availability: Percentage of availability = (total elapsed time – sum

of downtime)/total elapsed timeReliability (MTBF):

MTBF = (total elapsed time – sum of downtime)/number of failures

2-3


Availability Percentages 2-3

% Availability Annually

24/7 ShopStandard Business

(8 hr Days)

90%876 hours (36.5 days)

291.2 hours (12.13 days)

99%87.6 hours (3.65 days)

29.12 hours (1.21 days)

99.999% 5.256 minutes 1.747 minutes


Provides100 percent hardware

redundancyRapid failoverRolling updatesScales up to seven

active EVSs

Provides100 percent hardware

redundancyRapid failoverRolling updatesScales up to seven

active EVSs

Clustering Pros and Cons 2-5

Vulnerable toShared storage

failuresNetwork services

failuresOperational errorsNatural or unnatural

disasters

Vulnerable toShared storage

failuresNetwork services

failuresOperational errorsNatural or unnatural

disasters


Exchange 2003 Cluster Advantages 2-7

Eight-node clustersKerberos authenticationNew resource-dependency hierarchyVolume mount points


New Resource-Dependency Hierarchy 2-8

IMAP4

POP3

HTTP

Microsoftsearch

SMTP

Exchange 2000 Exchange 2003

Systemattendant

Routing

Informationstore

MTA

MTA

Systemattendant

Informationstore

Routing


Volume Mount Points 2-9

Each storage group in the cluster is assigned a drive letter for storing Exchange data.

Each storage group’s logs and SMTP queues are assigned space using mount points to overcome the limitation of drive letters.

EVS1

EVS2

EVS3

EVS4

M

N

O

P

SG1 logs

SG2 logs

SG3 logs

SG4 logs

SMTP queues

Q

R

S

T

SG1 logs

SG2 logs

SG3 logs

SG4 logs

SMTP queues

E

F

G

H

SG1 logs

SG2 logs

SG3 logs

SG4 logs

SMTP queues

I

J

K

L

SG1 logs

SG2 logs

SG3 logs

SG4 logs

SMTP queues


Exchange Clustering Concepts 2-10

Active

Active

Active

PassiveFour-node cluster

Fiber Fiber

Fiber Fiber

NIC 1

NIC 1

NIC 1

NIC 1

NIC 2

NIC 2

NIC 2

NIC 2

Fiberswitch

Publicswitch

Privateswitch

SAN

ActiveDirectory,

DNS, clients

EVS1

EVS3

EVS2


Cluster Terminology

Shared nothing architectureResourcesGroupsExchange Virtual ServersQuorum diskHeartbeat networkActive/ActiveActive/Passive

2-11


Failover 2-13

Node 1Resources go offline

Node 2Resources go online

EVS1 EVS1


Preferred Owners List 2-14


Disk 8: Quorum

Disk 9: MSDTC

Disk Configurations 2-15

SAN or DAS

Disk 1: SMTP/MTA

Disk 2: SG1 and SG2 databases

Disk 3: SG1 logs

Disk 4: SG2 logs

Disk 5: SG3 and SG4 databases

Disk 6: SG3 logs

Disk 7: SG4 logs

Node 1 (active)EVS1

Node 2 (passive)EVS1


Network Load Balancing 2-17

NLB

Busy Idle OfflineFailed

service

DNSround robin

DNS: GK.com

OWA.GK.com

NLB clustermembers

owa.gk.comowa.gk.comowa.gk.comowa.gk.com

172.30.1.100172.30.1.1172.30.1.2172.30.1.3172.30.1.4

172.30.1.1172.30.1.2172.30.1.3172.30.1.4


Windows Server 2003 NLB 2-19


Hardware NLB 2-20

W2K W2K3 UNIX Novell

HardwareNLB

Sessions

HTTP:80 HTTP:80 HTTP:80 HTTP:80


Anatomy of a Geographical Cluster 2-21

Mirrored

Corporate office Recovery site

Node4Node3Node2Node1

VLAN

SAN SAN

Disk 2Disk 1

Disk 4Disk 3


Disaster-Prone Areas 2-22

Earthquake

Medium

High

Very high

Tornado

Medium

High

Hurricane

Medium

High


Evaluating Cluster Operation and Deployment

When evaluating vendors, use the following checklists from Microsoft: “Architecture Basics”checklist “Operational and Deployment Procedures” checklist

2-23


Remote Recovery and Disaster Recovery Solutions

http://www.xosoft.com/ http://www.nsisoftware.com/ http://www.lefthandnetworks.com/ http://www.softek.com/ http://www.netapp.comhttp://www.emc.com/ (GeoSpan)

2-26


NSI GeoCluster 2-27


XOsoft WanSync 2-29


2-30

WANSync ExchangeMaster Site

M1

WANSync ExchangeReplica Site

R1Resource Transfer:Server IP Address

(single-network scenario)

Server DNS Lookup(multiple-network scenario)

Microsoft Exchange Server Microsoft Exchange Server

Automatic/instantaneous routing ofusers in case of failure

Users

XOsoft WanSync (cont.)


Strategic Authentication and Name Resolution

DNSDomain controllersGlobal catalog service

2-31


DNS High Availability 2-31

ADI DNS zonePrimary private

ADI DNS zonePrimary private

ADI DNS zonePrimary privateStandard zone

Primary public

NLBcluster

Internet

Standard zoneSecondary public

NLBcluster

External DNS

DMZ DNS

AD site2Subnet C Subnet D

AD site1Subnet A Subnet B

AD site3Subnet E Subnet F


Domain Controller High Availability

Centralized deploymentsDecentralized deploymentsMixed deployments

2-33


Centralized Domain Controllers 2-34

DC

DC

DC

DC

DC


Decentralized Domain Controllers 2-35

DC DC

DC

DCDC


Mixed Domain Controllers 2-36

DC

DC

DC

DC

DC

E2K3

200users


Global Catalog High Availability 2-37

AD site4

DCGC

DCGC

(2) E2K3 servers

AD site1DCGC

AD site3

(8) E2K3 servers

AD site2DCGC

(6) E2K3 servers

(4) E2K3 servers

DCGC

DCGC

DCGC

DCGC

© 2005 global knowledge network, inc. all rights reserved. section 2: high availability clustering...

Documents

global knowledge network

availability slide

knowledge guide

microsoft exchange server

exchange data

minutes slide

exchange clustering

network load balancing