Shulou(Shulou.com)05/31 Report--

This article mainly introduces the relevant knowledge of the function of Exchange2003 cluster, the content is detailed and easy to understand, the operation is simple and fast, and it has a certain reference value. I believe you will gain something after reading this article on the function of Exchange2003 cluster. Let's take a look at it.

1. When a cluster that supports up to eight nodes uses Windows Server 2003 Enterprise Edition or Windows Server 2003 Datacenter Edition, Exchange can support active / passive clusters with up to eight nodes.

2. Support volume mount point when using Windows Server 2003 Enterprise Edition or Windows Server 2003 Datacenter Edition, Exchange supports volume mount point.

3. Improving failover performance Exchange reduces the time it takes for the server to fail over to the new node, thus improving cluster performance.

4. Improve security Exchange clustered servers are now more secure. For example, the permission model in Exchange 2003 has changed and the Kerberos authentication protocol is enabled by default.

Improved prerequisite checks Exchange performs more prerequisite checks to help ensure that the clustered server is deployed and configured correctly.

Support for clusters with up to eight nodes

Exchange 2003 enhances clustering capabilities by introducing support for eight-node Exchange clusters. Eight-node clusters are supported only if you are running Windows Server 2003 Enterprise Edition or Windows Server 2003 Datacenter Edition. Another requirement for a cluster with three or more nodes is that at least one node must be passive. For complete details on cluster configurations based on Windows and Exchange version support, see "Windows and Exchange version requirements" in understanding Exchange Server 2003 clusters.

Support for volume mount point

Now, if the cluster node is running Window Server 2003 Enterprise Edition or Windows Server 2003 Datacenter Edition, the shared disk supports volume mount points. The volume mount point is a directory that points fixedly to the specified disk volume. (for example, C:\ Data can be configured to point to a disk volume. With mount points, there is no need to associate each disk volume with a drive letter, thus exceeding the limit of 26 drive letters.

Improve failover performanc

For clusters in Exchange 2003, the time it takes for one node to fail over to another node is reduced, thus improving overall performance. The following sections describe improvements in failover time.

Improve the correlation hierarchy of Exchange services

To reduce the time required for server failover, Exchange 2003 improves the dependency hierarchy of Exchange services. Specifically, in Exchange 2000, Exchange protocol services rely on Microsoft Exchange Information Store services. In Exchange 2003, these services rely on Microsoft Exchange system attendant services.

Exchange correlation hierarchy in Exchange 2000

Exchange correlation hierarchy in Exchange 2003

If a failover occurs, this improved hierarchy allows Exchange mailbox stores, public folder stores, and Exchange protocol services to start at the same time. As a result, all Exchange resources (except the system attendant service) can be started and stopped at the same time, thus reducing failover time. "in addition, if Exchange storage is stopped, the system does not have to wait for dependent resources to go offline before the storage resources come back online."

Improve the detection of available nodes

When you run Exchange 2003 on Windows Server 2003, the cluster service automatically detects available nodes. The total time it takes for Exchange to fail over to available nodes is reduced. As a result, both planned and unplanned failovers reduce downtime.

Improve security

The Exchange 2003 cluster includes the following security features:

The cluster permission model has changed.

By default, Kerberos is enabled on the Exchange virtual server (EVS).

Back-end servers from the front-end server to the cluster are supported using Internet Protocol Security (IPSec).

By default, IMAP4 and POP3 resources are not added when the EVS is created.

Each of these features is discussed in detail in the following sections.

Cluster permission model change

In Exchange 2003, the permissions required to create, delete, or modify EVS were modified. The * * way to understand these modifications is to compare the Exchange 2000 permission model with the new Exchange 2003 permission model.

Exchange 2000 privilege model

For Exchange 2000 cluster administrators who create, delete, or modify EVS, the cluster administrator account and the cluster service account require the following permissions:

If EVS is * EVS in your organization, you must have Exchange administrator (full control) privileges at the organization level.

If EVS is not * EVS in your organization, you must have Exchange administrator (full control) privileges at the administrative group level.

Exchange 2003 privilege model

In Exchange 2003, the permission model has changed. The Windows cluster service account is no longer Exchange specific. This means that the cluster service account no longer needs to apply the Exchange administrator (full control) role to itself, either at the Exchange organization level or at the administrative group level. The default permissions of the cluster service account in the forest are sufficient for it to operate in Exchange.

When using Exchange 2000, the cluster administrator requires the following permissions:

If EVS is * EVS in your organization, the cluster administrator must be a member of a group to which the Exchange administrator (full control) role is applied at the organization level.

If EVS is not * EVS in your organization, the account used by the cluster administrator must be a member of a group to which the Exchange Administrator (full Control) role is applied at the administrative group level.

However, this depends on the mode in which the Exchange organization is running (native mode or mixed mode) and the topology configuration, and the cluster administrator must have the following additional permissions:

When the Exchange organization is in native mode, if the EVS is in a routing group that spans multiple administrative groups, the cluster administrator must be a member of a group to which the Exchange administrator (full control) role is applied at the administrative group level for all administrative groups that the routing group spans. For example, if EVS is in a routing group that spans * administrative groups and a second administrative group, the account used by the cluster administrator must be a member of a group that has the role of Exchange administrator (full control) for both * administrative groups and the second administrative group.

In a topology such as a parent domain / child domain, where the cluster server is * Exchange servers in the child domain, you must have Exchange administrator privileges at the organizational level to specify the server responsible for recipient update services in the child domain.

Kerberos is enabled by default on the Exchange virtual server

Kerberos is the authentication protocol in Microsoft Windows 2000 Server, and later it provides mutual authentication. However, prior to Windows 2000 Service Pack 3 (SP3), the cluster service did not support Kerberos-enabled cluster groups. For this reason, the earlier version of the authentication protocol NTLM is the default authentication protocol for Exchange servers running in the cluster.

Because Kerberos is supported on Windows 2000 SP3 and later or clustering services on Windows Server 2003 and Exchange 2003, when you create EVS on a server running Windows Server 2003 or Windows 2000 SP3, Kerberos is enabled by default.

Support IPSec for back-end servers from front-end servers to clusters

IPSec can be used if a secure channel is needed between the front-end and back-end clustered servers. This configuration is fully supported if both the front-end and back-end servers are running Exchange 2003 on Windows Server 2003.

IMAP4 and POP3 resources are not added by default

To improve security, IMAP4 and POP3 protocol resources are no longer created when the EVS is created. For more information about enabling IMAP4 or POP3, see "Managing Exchange clusters" in Exchange Server 2003 Administration Guide.

Check cluster prerequisites

To ensure that the cluster meets specific requirements, Exchange 2003 performs more prerequisite checks on the cluster than in previous versions of Exchange. For example, to ensure that Exchange is installed correctly on cluster nodes, Exchange 2003 performs more pre-installation checks on cluster nodes. Similarly, to ensure that EVS is configured correctly, Exchange 2003 performs more checks on the cluster when the EVS is created and deleted.

This is the end of the article on "what are the functions of Exchange2003 clustering?" Thank you for reading! I believe you all have a certain understanding of the knowledge of "what are the functions of Exchange2003 clusters". If you want to learn more, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.