In
Exchange 2003 and earlier, organizations that wanted geographical fault tolerance needed to turn
to third parties to provide data replication. A typical scenario in Exchange 2003 was an Exchange
cluster attached to a SAN for hardware/software replication of Exchange data to a second SAN.
This solution could be costly and some solutions had no support from Microsoft. Clustering in
general is more complicated and requires well - defined processes. For example, the hardware
selection and software installation differs significantly compared to a non - clustered server.
Unfortunately, many administrators were not trained adequately, and outages could actually
become longer or more severe due to administration mistakes.
In response to the growing demand for a supported, less costly, and easier to administer cluster
design, Exchange Server 2007 introduces three forms of continuous replication ??” Local
Continuous Replication (LCR), Clustered Continuous Replication (CCR), and new in Service Pack
1 ??” Standby Continuous Replication (SCR). In addition, Exchange still offers traditional Single
Copy Clusters (SCCs).
Part III: Working with PowerShell in a Production Environment
328
In this chapter you learn about:
??‘ Installing different types of continuous replication
??‘ Seeding replications
??‘ Monitoring system health
??‘ Failover and fallback
Understanding Continuous Replication
Continuous replication is the new cluster model in Exchange Server 2007.
Pages:
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465