Creating a Virtual Exchange Server for Exchange 2003 Clustering
In this article I will show you in details the Steps that are necessary to create an Exchange Virtual Server for Exchange Server Clustering with Windows Server 2003. This article goes beyond my first article about clustering. In this article I gave you only the basic Steps that were necessary to create an Exchange 2003 Cluster.
Note: This article is published with permission from www.msexchange.org
This article begins by creating the Exchange Virtual Server which is the heart of the Exchange Cluster because this object presents the Exchange Server for all users and other resources.
You must have completed the following steps:
- Installing and configuring Windows Server 2003 Enterprise
- Implementing the Shared Storage (SAN, NAS) for the Quorum and the Exchange Databases
- Creating a Cluster with Cluster Administrator
- Installing Exchange Server 2003 Enterprise and Service Pack 2 on each Cluster Node
After installing Exchange Server 2003 on the Cluster Nodes you will see several Cluster Resource in Cluster Administrator which was installed during the Exchange Server Setup.
Create a new Cluster Group
The first step is the creation of a new Cluster Group. A cluster Group will be used to group Resources which are necessary for the Exchange Cluster creation. If a Failover occurs the whole Cluster Group will move to another Cluster Node.
You must give the Cluster Group a name and a optional description.
In the next step you must select the preferred owners of the Resource Group. A Failover can only by initiated between Preferred Owners.
Create a Cluster IP
After successfully creating the Cluster Group you must create a Cluster IP Resource. The Cluster IP Resource is used to give the Exchange Virtual Server an IP Address. The Network for the Cluster IP address is the LAN network.
Create a Cluster Name
Now, create a Cluster Name. The Cluster Name will be used as the logical Cluster Name. The Cluster Name Resource must be created in the Cluster Group for Exchange.
Possible Owners are NODE1 and NODE2.
The Cluster Name is dependant from the Cluster IP.
The name of the Cluster is DECCLUS. The Cluster setup will create the necessary DNS records in the DNS console. New with Exchange Server 2003 is the Support for Kerberos Authentication when you enable the Checkbox Enable Kerberos Authentication.
Now it is time to create the Cluster Disc Resource. The Cluster Disk is from the Physical Disk Resource Type.
The Cluster Disk is dependant from the Cluster IP and Cluster Name Resource.
The Cluster Disk for the Cluster in this Article is Disk E:
Create the Exchange Virtual Server
Now it is time to create the Exchange Virtual Server. Right click the Cluster Group and click – New – Resource and select Microsoft Exchange System Attendant as the Resource Type. This will create the Exchange Virtual Server.
Possible Owners of the Exchange Virtual Server are NODE1 and NODE2.
The Exchange Virtual Server is dependant from the Cluster IP, Cluster Name and Physical Disk Resource.
Select the Exchange Administrative Group, where the Virtual Exchange Server should be installed. If your Exchange Organization has only one Administrative Group you have no choice for selecting the administrative Group.
Select the Routing Group
Install the Exchange Virtual Server in the Exchange Routing Group where the Cluster Nodes are physically located.
The Default path for the Exchange Databases is the Cluster Disk Resource that you previously created and the Path \EXCHSRVR like a normal Exchange Server installation.
Read the summary carefully and after reviewing the configuration, click Finish.
After successfully creating the Cluster Group and the Exchange Virtual Server, right click the new Cluster Group and select Bring Online. This will bring all Resources -based on their Dependencies – in the Cluster Group Online.
The process of taking the Resources Online takes a while.
The Exchange Virtual Server in the Exchange System Manager
The Exchange Virtual Server (EVS) is listed as a normal Object in the Exchange System Manager (ESM).
The Exchange Virtual Server looks like a normal Computer object like every other physical Computer object. The Exchange Virtual Server is also listed in the Active Directory Users and Computers console.
Congrats. You have successfully created the Virtual Exchange Server and you are now Cluster Ready. Depending on the number oft Cluster Nodes you can create additional Virtual Exchange Server objects in the Cluster Administrator console.
Remove the Exchange Virtual Server
If you want to remove The Exchange Virtual Server from Exchange you can use Cluster Administrator to do that but keep in mind that this will remove the entire Exchange Server from your Exchange Organization. If you only would like to remove one Cluster node from the Exchange Cluster you must evict the Node from the Cluster.
The high level steps to remove the Exchange Virtual Server are the following:
- Backup critical Exchange Data
- Move all Mailboxes and Public Folder from the Exchange Virtual Server to another Exchange Server
- Take the Exchange System Attendant Resource in the Exchange Cluster Group offline
- Remove the Exchange Virtual Server
- Delete remaining Cluster Resources
The deletion of the Exchange Virtual Server also deletes all Exchange Resources in the Cluster Administrator.
In my first article I showed you the high level Steps how to implement a Two Node Exchange Cluster with the Windows Server 2003 Cluster Services. In this article I tried to explain the Steps how to create the Exchange Virtual Server. It is really simple to create an Exchange Virtual Server which can be used as a clustered Exchange Server.
Implementing a Two Node Cluster with Windows 2003 Enterprise
Cluster Configuration Checklist from IT Showcase for Exchange Server 2003
Just say NO to A/A
Marc Grote is a MCSA/MCSE Messaging & Security and Microsoft Certified Trainer. He is working as a freelance IT Trainer and Consultant in the north of Germany and as an part time employee of Invenate GmbH in Hanover (Germany). He is working there as an consultant for Microsoft Server infrastructure. You will find more information about Invenate here http://www.invenate.de. He is specialized in ISA, SMS, Exchange, Security on Windows 2000 and Windows Server 2003 designs, migrations and implementations and Citrix Metaframe / Cisco implementations. His efforts have earned him recognition as a Microsoft MVP for ISA Server. You can visit his homepage on www.it-training-grote.de
Note: This article is published with permission from www.msexchange.org
More in Exchange Server
Microsoft Releases Exchange Server Updates to Improve Security of PowerShell Payloads
Jan 11, 2023 | Rabia Noureen
Microsoft Warns About New Zero-Day Vulnerabilities in Exchange Server
Sep 30, 2022 | Rabia Noureen
Microsoft Exchange Servers Hit By Stealthy IIS Backdoors
Jul 27, 2022 | Rabia Noureen
Kaspersky Discloses New 'SessionManager' Backdoor Targetting Microsoft Exchange Servers
Jul 1, 2022 | Rabia Noureen
M365 Changelog: (Updated) Safe Links Global Settings Migrated to Custom Policies
Jun 28, 2022 | Petri Staff
Microsoft Postpones the Release of Next Version of Exchange Server Until 2025
Jun 3, 2022 | Rabia Noureen
Most popular on petri