Exchange 2003 High Availability & Site Redundancy . Wil Westwick | Dedicated Supportability Services EMEA eXchange Center of Excellence (UK Competence Centre Lead) MICROSOFT CORPORATION. Welcome to this TechNet Event. FREE bi-weekly technical newsletter
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Wil Westwick | Dedicated Supportability Services
EMEA eXchange Center of Excellence (UK Competence Centre Lead)
We would like to bring your attention to the key elements of the TechNet programme; the central information and community resource for IT professionals in the UK:
To subscribe to the newsletter or just to find out more, please visit www.microsoft.com/uk/technet or speak to a Microsoft representative during the break
(3rd party investments)
= Alignment to business Service Level Agreements and a measurement of availability (% of uptime).
“What are the 4 9’s and how do I measure them ?”
Microsoft Exchange 2003 and Partner technologies help IT Professionals provide solutions to these modern day business requirements.
Design Fundamental: Multi-Site Data Availability
- Clones (VSS)
Short Common Questions
unavailability of the production datacenter.
subnets on the DR site.
created to the same destinations with higher costs and are online.
however smaller size since we don’t need space for data restore.
values of the production clusters (same IP and same name EVS1).
of empty databases.
and meets customer requirements.
between the production and standby clusters.
Connect or Work Offline.
infrastructure can not be afforded/qualified.
corresponding ‘standby server’ in Site B. For example:
EXC1 -> EXC04 EXC2 -> EXC05 EXC3 -> EXC06
The Exchange Servers in Site B will take ownership/responsibility of serving all corporate messaging requirements and provide users with access to all mailbox data with no data loss.
- AD attributes such as HOMEMDB and HOMEMATA will become incorrect. The following process details the steps required:
1. Site A goes down.
2. Open up ADU&C and use the multiple select options to select each of the mail-enabled user objects that were homed on Exchange Servers.
3. Right Click the combined group selection and choose Exchange Tasks. The Exchange Task Wizard will launch. Follow through the wizard to
delete each of the mail-enabled user objects mailboxes.
NOTE: Pre-defined LDAP queries (querying the AD for HOMEMDB and HOMEMTA) can be created and saved into the ADU&C MMC. This will
facilitate the quick identification of users homed on the failed servers.
4. Move the DB's as planned. (Storage level – executed by the presentation of target LUNS).
5. Mount appropriate databases within the RECOVERY MAILBOX CENTER (RMC).
6. Using the RMC select all non-connected mailboxes using either the CTL or Shift Key.
7. Right click and select FIND MATCH. Matching wizard will launch and establish GUID matches for each deleted MBX for an active user account.
8. Right click the group selection for a second time and choose the RECONNECT option.
9. The Mailbox connection feature will reconnect each of the deleted mailboxes with their original user account thus updating the HOME_MDB and
HOME_MTA attributes with the new ‘dead server’ name where the mailbox will now be homed.
10. Change the MAPI profile via network script/PROFMAN tools.
Multi-site data replication support for Exchange 2003 and Exchange 2000:
Deployment Guidelines for Exchange Server Multi-Site Data Replication:
Jetstress Tool is available from:
Achieving High Availability with Exchange Server at Microsoft:
Windows Server Catalogue: Geographically Dispersed Cluster Solutions: