Module 7: Planning Server Roles and Placement v
Customization Information
This section identifies the lab setup requirements for a module and the
configuration changes that occur on student computers during the labs. This
information is provided to assist you in replicating or customizing Microsoft
Official Curriculum (MOC) courseware.
Lab Setup
The following list describes the setup requirements for the labs in this module.
!"
For each student, a Microsoft Management Console (MMC) custom console
must be created. This custom console must include both the
Active Directory Users and Computers snap-in and the Exchange System
snap-in, and must be named your_firstname Console.
!"
For each student, a personalized user account must be created in the
appropriate domain. This user account must be added to the Domain
Admins group, and assigned a mailbox on the server running
Exchange 2000 that the student is using.
!"
For each student, a user profile must be created on the student’s computer
that enables the student to access their mailbox by using Microsoft
Outlook
®
2000.
!"
The students sitting at the City-MBX1 computers will need the
IMAP4Stresser application that is located at c:\moc\1573a\labfiles
Lab Results
Performing the labs in this module introduces the following configuration
changes:
!"
Network Load Balancing is configured for the City-FE1 and City-FE2
servers.
!"
DNS is configured to have a front-end namespace for each routing group.
!"
The City-FE1 and City-FE2 servers in each routing group are converted to
front-end servers.
!"
All mailboxes are moved from the City-FE1, City-FE2, and City-PF1
servers to the City-MBX1 server in each routing group.
!"
The City-MBX1 server in each routing group is configured so that the
private information store databases point to the City-PF1 server in it’s
routing group.
Module 7: Planning Server Roles and Placement 1
Overview
!
Introduction to Planning Server Roles and Placement
!
Planning Mailbox Servers and Public Folder Servers
!
Planning Connector Servers
!
Planning Front-end/Back-end Servers
!
Planning for Servers Running Active Directory
!
Discussion: Planning Server Placement
Microsoft
®
Exchange 2000 organizations designed for the enterprise usually
deploy several different servers. Although it is possible to install the entire
functionality of Exchange 2000 on a single server, it is usually better to
distribute the functions among several servers. Architects designing an
Exchange 2000 organization need to be able to identify and plan for the
deployment of each of the types of servers that a company needs.
In addition to identifying server roles, the necessary planning tasks include
determining the number of each type of server that a company requires, as well
as where to place each server. To complete these tasks, you must understand the
various roles of the different types of servers, and of the design effects
associated with their deployment.
After completing this module, you will be able to:
!"
Plan mailbox servers and public folder servers.
!"
Plan connector servers.
!"
Plan front-end/back-end servers.
!"
Plan servers running the Microsoft
®
Active Directory
™
directory service.
!"
Identify the factors to be considered when designing server placement.
Topic Objective
To provide an overview of
the module topics and
objectives.
Lead-in
In this module, you will learn
about the Exchange 2000
server roles, and how to
plan and place servers for
an effective Exchange 2000
organization.
2 Module 7: Planning Server Roles and Placement
Introduction to Planning Server Roles and Placement
User
Internet Front End
Servers
Back End
Servers
Mailbox Server Connector Server Internet
User
Mailbox Server
Public Folder Server
Although each server running Exchange 2000 often performs several roles in a
smaller organization or in a remote office, it is often preferable to dedicate
servers to perform specific roles.
Distributing functions among several different servers enables you to provide
faster response time and reduced downtime. Distributing roles also helps
prevent servers from becoming overloaded, and removes the dependencies
between services.
Planning server roles and placement will help you decide which hardware to
purchase and will affect the performance of your messaging system. It is
important to have your budget settled prior to planning your server roles,
because dedicating servers to specific roles may significantly increase the
number of servers that you will need to purchase.
Topic Objective
To outline the different types
of servers that a company
may deploy.
Lead-in
There are several ways to
deploy servers running
Exchange 2000.
Module 7: Planning Server Roles and Placement 3
#
##
#
Planning Mailbox Servers and Public Folder Servers
!
Capacity Planning
!
Planning Considerations
!
Planning Storage Needs
!
Partitioning Databases
Developing an effective design strategy for mailbox servers and public folder
servers involves taking into account the capacity that each server can handle, as
well as such considerations as service level agreements, retention policies, and
storage needs.
Topic Objective
To outline the design
considerations that are
associated with planning
mailbox and public folder
servers.
Lead-in
There are several design
considerations to take into
account when planning
mailbox and public folder
servers.
4 Module 7: Planning Server Roles and Placement
Capacity Planning
Storage limits
Time required to perform a backup
Time required to recover from a disaster
Time required to restore a single database
Time required to restore a single mailbox
Capacity Planning for Mailbox Servers
Capacity Planning for Mailbox Servers
Capacity Planning for Mailbox Servers
Service levels
Response time
Capacity Planning for Public Folder Servers
Capacity Planning for Public Folder Servers
Capacity Planning for Public Folder Servers
The number of users and public folders that each server can support depends
primarily on the usage profile for each user.
Mailbox Servers
The most important factors to consider when calculating the number of
mailboxes to store on each server are: the storage limits, the time required to
perform a backup, the time to recover from a disaster, the time to restore a
single database, and the time to restore a single mailbox.
Public Folder Servers
Service levels and response time are the primary factors to consider when
determining whether to dedicate a server to public folder storage. For example,
if your company builds custom applications into multiple public folder
hierarchies, it is recommended that you place these hierarchies on a separate
server so that people gaining access to these custom application folders do not
increase the response time for people checking their mailboxes.
Topic Objective
To provide capacity
planning information for
mailbox and public folder
servers.
Lead-in
The number of users and
public folders that each
server can support depends
primarily on the usage
profiles for each user.
Module 7: Planning Server Roles and Placement 5
Planning Considerations
What is the default storage limit on mailboxes?
What is the default storage limit on mailboxes?
What is the retention policy for deleted items?
What is the retention policy for deleted items?
Which protocols are enabled for mail?
Which protocols are enabled for mail?
How many mailboxes on each server are related to service level
agreements with customers?
How many mailboxes on each server are related to service level
agreements with customers?
How long will data be stored on the server?
How long will data be stored on the server?
Although Exchange 2000 does not impose a limit on the number of mailboxes
or public folders that can reside on any one server, you must consider storage
limits, data storage, retention policies, protocols, and service level agreements
when planning mailbox servers and public folder servers:
Default Storage Limit on Mailboxes
The default storage limit on mailboxes, combined with the number of users that
you support, will help you to determine how many mailbox servers you need.
For example, if you have 500 users, and if you limit each user mailbox to a
maximum size of 50 megabytes (MB), then you need to plan for a minimum of
25 gigabytes (GB) of mailbox space.
Storing Data
You can control the amount of data that is stored on a server by using tools such
as the Mailbox Cleanup Agent to search databases and to delete old messages.
You can also configure Post Office Protocol version 3 (POP3) and Internet
Message Access Protocol version 4 (IMAP4) client applications to move
retrieved messages to their local client. The less data you store on your server,
the less storage space you need.
Retention Policy
If you want to archive or to retain deleted items, you need to develop a retention
policy that accounts for the additional space that you will require. Consider the
average size of the messages that your users receive, as well as the average
number of messages that users delete per day.
Protocols
If you enable users to use POP3, IMAP4, or Microsoft Outlook
®
Web Access to
retrieve mailbox data, then you may need to configure servers in a
front-end/back-end configuration so that you can remove all authentication and
offload processing tasks from the mailbox server.
Topic Objective
To outline the planning
considerations that are
related to mailbox and
public folder server roles
and placement.
Lead-in
There are several
considerations to take into
account when planning
mailbox and public folder
servers.
6 Module 7: Planning Server Roles and Placement
Service Level Agreements
You must consider the number of mailboxes on each server that are related to
service level agreements. If large mailbox stores exist, consider splitting each of
them into several smaller ones. In the past, service level agreements often
required the deployment of multiple servers to ensure recovery within the time
constraints of the service level agreement. Creating multiple storage groups and
databases enables you to consolidate these servers into one larger server that
has multiple mailbox stores and databases.
Module 7: Planning Server Roles and Placement 7
Planning Storage Needs
Servers
First Storage Group
Default Mailbox Store
Executives
Second Storage Group
News Store
Third Storage Group
Public Folders
Server 1
You can use storage groups to store data on your mailbox servers and on your
public folder servers.
Microsoft Exchange 2000 Enterprise Server supports a maximum of four
storage groups with a maximum of five databases in each storage group. Each
mailbox and each public folder store is a member of a storage group. All
mailboxes and all public folder stores in each storage group share a single set of
transaction log files. You can place one or more storage groups on each server.
The following table outlines a possible Exchange 2000 store configuration.
Storage Group Database
First storage group User mailbox store and Executives
mailbox store
Second storage group Network news
Third storage group Public folders
Creating Multiple Storage Groups
If you plan to create multiple storage groups on one server, make sure that you
can place the transaction logs and the database onto separate disk spindles. The
primary reasons for separating the transaction logs from the database are to
increase performance while logging transactions, and to take advantage of
sequential writes. Storing transaction log files on their own dedicated disk
spindle also aids in the database recovery process. If your transaction log files
are stored on their own dedicated disk spindle, and if you have circular logging
disabled, then if a database associated with those transaction log files becomes
damaged, it is possible to recover all data that was entered up to the time when
the database became damaged.
Topic Objective
To outline the storage
requirements that are
associated with mailbox
servers and public folder
servers.
Lead-in
You can use storage groups
to store the data on your
mailbox servers and on your
public folder servers.
Delivery Tip
Have the students discuss
alternative storage group
options to those outlined in
the table on this page.
8 Module 7: Planning Server Roles and Placement
Partitioning Databases
!
Makes database management easier and more logical
!
Reduces the effects of a malfunctioning database
Storage Group 2Storage Group 1
Mailbox Server
If you do not have enough disk drives available, you can store all of your
databases on the same partition. However, if you do have enough disk space to
allow for placing separate databases on separate partitions, it is recommended
that you do so.
Placing database files from different storage groups on separate partitions:
!"
Makes database management easier and more logical.
!"
Reduces the effects of a malfunctioning database. If the drive array that
houses one storage group of databases goes offline, the failure will not
affect databases in any other storage group.
If you distribute databases from multiple storage groups over a single drive
array, and that drive array goes offline, then all databases associated with
those storage groups will go offline temporarily, even if some of those
databases are located on other arrays. The damaged database will be marked
as down, and the working databases will remount. Ordinarily, this type of
outage will only last for a few minutes. At the end of that period, Messaging
Application Programming Interface (MAPI) clients such as
Outlook will
recover their connections.
Topic Objective
To explain how to partition
databases.
Lead-in
There are several reasons
for storing database files
from separate storage
groups on separate
partitions.
Không có nhận xét nào:
Đăng nhận xét