Exchange protection requirements, Exchange – HP Storage Mirroring Software User Manual
Page 49

Storage Mirroring Recover requirements
Page 48 of 677
Exchange protection requirements
In addition to the
general application requirements
, you must also meet the following
requirements to protect Exchange.
l
Exchange versions—Storage Mirroring Recover can protect Microsoft Exchange
2003 or Exchange 2007, with the following requirements and limitations.
l
The version of Exchange on the source and target must be identical.
l
Storage Mirroring Recover does not check the edition of Exchange 2007
(Enterprise or Standard). However, it is able to differentiate between service
pack levels. If you have Exchange 2007 Enterprise on the source and
Exchange 2007 Standard on the target, you will be limited to only failing over
the number of databases or storage groups supported by Exchange 2007
Standard. See the
information on the Microsoft website.
l
For Exchange 2007, in a consolidated role environment only the mailbox role
is protected. The Hub Transport and Client Access roles are not protected or
failed over because they are already installed on the target.
l
For Exchange 2007, replication and failover between a distributed role
source configuration to a consolidated role target configuration is permitted
as long as the source Mailbox Server role is installed on a standalone server
or cluster with the other roles residing on different servers, and the target
configuration is a standalone server with the Mailbox, Hub Transport, and
Client Access roles installed. In these configurations, Storage Mirroring
Recover will not replicate any data associated with the Hub Transport/Client
Access data, however, the target Hub Transport/Client Access roles function
properly when failing over the source Mailbox role, allowing necessary
operations to resume.
l
Server and network configuration—The following requirements and limitations
apply to your Exchange server and network configuration.
l
You can use a
for Exchange protection. You cannot
use a one-to-many, many-to-one, or chained configuration.
l
The source and target servers must be in the same root forest domain.
l
In a parent/child domain, at least one domain controller in the child domain
must be designated as a global catalog server.
l
The target server cannot be a domain controller.
l
Exchange and a domain controller cannot be on the same node of a cluster.
l
Exchange 2003 on a domain controller is not a recommended configuration.
However, if you must run Exchange 2003 on a domain controller, review