نمایش نتایج: از شماره 1 تا 3 از مجموع 3

موضوع: Instal., Config. and Test. an Exchange 2007 Cluster Continuous Replication (CCR) Based Mailbox Serve

  
  1. #1
    نام حقيقي: 1234

    مدیر بازنشسته
    تاریخ عضویت
    Jul 2009
    محل سکونت
    5678
    نوشته
    5,634
    سپاسگزاری شده
    2513
    سپاسگزاری کرده
    272

    Instal., Config. and Test. an Exchange 2007 Cluster Continuous Replication (CCR) Based Mailbox Serve

    کد:
    http://www.msexchange.org/tutorials/Installing-Configuring-Testing-Exchange-2007-Cluster-Continuous-Replication-Based-Mailbox-Server-Part1.html

    PART-1


    Introduction

    Exchange Server 2007 introduces several new high availability features, one of them is the Cluster Continuous Replication (CCR) feature. This feature takes the new Exchange Server 2007 Log file shipping and replay features and combines them with the features that are available in a more traditional 2 node Windows 2003 active/passive cluster setup. A traditional 2 node active/passive cluster certainly has its benefits, but it also has one major drawback and that is you still have a single point of failure when it comes to Exchange databases.
    Prerequisites

    In order to follow the steps throughout this article series, you need the following:

    • A Windows 2003 Active Directory forest with at least one Domain Controller (raised to 2000 or 2003 forest functional level).
    • Two Windows 2003 Server R2 Enterprise Editions or Windows 2003 Server SP1 Enterprise Editions.
    • One Windows File share Witness (MS recommends this to be an Exchange 2007 Hub Transport Server in the existing Exchange 2007 organization)


    Note
    Remember to apply the update mentioned in MS KB article 921181 to both servers that will act as nodes in the Exchange Server 2007 Clustered Mailbox setup. The update adds a new file share witness feature to the current Majority Node Set (MNS) quorum model. The file share witness feature lets you use a file share that is external to the cluster as an additional "vote" to determine the status of the cluster in a two-node MNS quorum cluster deployment, which is a requirement in order to make use of the cluster continuous replication (or CCR in short) functionality in Exchange Server 2007.

    In addition to the above prerequisites you should be aware of the following general requirements as well:

    • When dealing with CCR environments you must use/can only use one database per storage group.
    • You cannot create a public folder database in a CCR environment if you already have more than one public folder database in your organization.
    • You can create up to 50 storage groups and 50 databases on a CCR cluster. Bear in mind though, that you should create only one database per storage group.
    • The cluster in which Exchange 2007 is installed cannot contain Exchange Server 200x, or any version of Microsoft SQL Server. Running Exchange 2007 in a cluster with any of these other applications is not supported.

    Warning
    Since Exchange Server 2007 Beta 2 isn’t supported in a production environment, unless you’re participating in the Rapid Deployment Program (RDP) or Technology Adopter Program (TAP), you should install the mailbox cluster in a test domain.


    Configuring the Network Settings for the Cluster nodes

    When you start the servers that are to be the nodes in the cluster, start by naming the machines E2K7Node1 and E2K7Node2 or whatever naming scheme you want to use (these names have nothing to do with the Exchange server name which your clients will be configured to connect to later on). Now name the two network connections Public and Private for the external and the internal network respectively (remember to do this on both nodes).

    Figure 1: Network Connections
    Click Advanced > Advanced Settings, if it’s not already the case, make sure Public is listed first on the binding order list, then Private and lastly Remote Access Connections.

    Figure 2: Binding order
    Before Exchange 2007 SP1 released, it was also recommended to disable File and Printer Sharing for Microsoft Networks for the private network as shown in Figure 3. However, when SP1 released this guidance changed, since Exchange 2007 SP1 introduced a new cmdlet named Enable-ContinuousReplicationHostName. This cmdlet makes it possible to specify over which network log files should be ship and seeded. So no matter whether you deploy CCR on Windows 2003 or Windows 2008 based servers, please don’t disable File and Printer Sharing for Microsoft Networks for the private network.


    Figure 3: Disabling File and Printer Sharing for Microsoft Networks
    Configure the Public network with the respective network settings you use in your test environment.

    Figure 4: Configuring the Public network
    Configure the Private network with an IP address and a subnet mask. Nothing else is required since this network is only used for communication (heartbeats) between the nodes in the cluster.

    Figure 5: Configuring the Private network
    Now click Advanced then select the DNS tab. Here you should untick both Register this connection's addresses in DNS and Use this connection's DNS suffix.

    Figure 6: Configuring DNS settings for the Private network
    Click the WINS tab. Untick Enable LMHOSTS lookup and select Disable NetBIOS over TCP/IP.

    Figure 7: Configuring WINS settings for the Private network
    Click OK three times and close the network connections window.
    Now add both Windows 2003 Servers as member servers in your Active Directory test domain.


    Creating and Configuring the Windows 2003 Server Cluster

    Now that the two servers are ready to act as nodes in a Windows 2003 cluster, it’s time to create the actual Windows 2003 Server Cluster. In order to do so logon to E2K7Node1 with a Domain admin account, then click Start > Administrative Tools > Cluster Administrator, and select Create new cluster in the drop-down box. Now click OK.

    Figure 8: Creating a new cluster
    Note
    You can also open a command prompt and type Cluster.exe /create /wizard in order to start the cluster wizard.
    Click Next.

    Figure 9: Cluster Wizard
    Specify the domain name as well as the cluster name (name for the Windows 2003 cluster NOT the Exchange cluster name which the clients will connect to), then click Next.

    Figure 10: Cluster Name and Domain
    Type the name of the Windows 2003 server that is to be the first node in the cluster, in this case E2K7Node1, then click Next.

    Figure 11: Adding the First Cluster Node
    Let the cluster wizard determine the cluster configuration and click Next.
    Note
    You can ignore the two warnings in Figure 12, since the nodes in a cluster continuous replication based mailbox server setup aren’t going to share the same disk subsystem.

    Figure 12: Analyzing Cluster Configuration
    Now enter the IP address that the cluster management tools should use to connect to the cluster, in this case 10.10.1.216, then click Next.

    Figure 13: Specifying the IP address the Cluster Management Tools should connect to
    Enter the credentials of the cluster service account (When speaking test environments I’m often too lazy to create a specific cluster service account and instead tend to use the Administrator account which will have the appropriate permissions) and click Next.

    Figure 14: Entering the credentials of the Cluster Service Account
    Now click Quorum and select Majority Node Set as the resource type, then click Ok and Next.

    Figure 15: Proposed Cluster Configuration

    Figure 16: Setting Majority Node Set as the Resource Type
    Now wait for the cluster to be configured, then click Next.

    Figure 17: Creating the Cluster
    When the cluster has been completed successfully you can click Finish.

    Figure 18: Cluster Wizard Successfully Completed
    We now have a full working Windows 2003 cluster running, but since there’s only one node it’s not very fault tolerant. So let’s add the second Windows 2003 server too. We can do this by right-clicking E2K7Node1 in the left pane of the Cluster Administrator, then selecting New > Node as shown in Figure 19 below.

    Figure 19: Adding a second node to the Cluster
    The Add Nodes Wizard will launch and you can click Next.

    Figure 20: Add Nodes Wizard
    Enter the name of the server that is going to be the second node (in this case E2K7Node2), then click Next.

    Figure 21: Entering the name of the second node
    Again let the Add Notes Wizard determine the cluster configuration, then click Next.

    Figure 22: Analyzing Cluster Configuration
    Enter the password for the cluster service account (in this case the Administrator account), then click Next.

    Figure 23: Entering the password for the Cluster Service Account
    When you are verified, you want to add the second node to the cluster with the configuration shown in Figure 24, click Next.

    Figure 24: Proposed Cluster Configuration for node 2
    When the cluster has been configured properly without any errors or warnings, click Next.

    Figure 25: Cluster is configured for the second node
    When the Add Notes Wizard has completed successfully, click Finish.

    Figure 26: Completing the Add Nodes Wizard
    The second Windows server is now part of the cluster as can be seen in Figure 27 below.

    Figure 27: Cluster Administrator with two nodes
    Alright we have reached the end of part one, but you can look forward to part two of this article series in the near future. Until then have a nice one!





    موضوعات مشابه:

  2. #2
    نام حقيقي: 1234

    مدیر بازنشسته
    تاریخ عضویت
    Jul 2009
    محل سکونت
    5678
    نوشته
    5,634
    سپاسگزاری شده
    2513
    سپاسگزاری کرده
    272
    کد:
    http://www.msexchange.org/tutorials/Installing-Configuring-Testing-Exchange-2007-Cluster-Continuous-Replication-Based-Mailbox-Server-Part2.html
    PART-2

    Introduction

    In part one of this article series we went through the installation of the Windows 2003 cluster. In this second article we’ll install the Windows components required by Exchange Server 2007 as well as configure the Majority Node Set (MNS) Quorum with File Share Witness. Finally we’ll finish off by enabling and configuring the transport dumpster on the Hub Transport server in the Active Directory site.
    Installing the necessary Windows Components

    Before we move on and try to install the Exchange Server 2007 Beta 2 bits, we need to make sure the required Windows components have been installed. All types of Exchange Server 2007 installations (no matter what server role we're talking about) needs the Microsoft .NET Framework 2.0 component installed.
    Note
    If you have installed Windows Server 2003 Enterprise Edition with Service Pack 1 on the nodes, you need to download the Microsoft .NET Framework Version 2.0 Redistributable Package (x86), since it’s only a standard Windows component when speaking Windows Server 2003 R2.

    Figure 27: Installing the Microsoft .NET Framework 2.0 Windows Component
    Since we’re installing the Mailbox Server role in the cluster, we also need to install the below IIS 6.0 components:

    • Enable network COM+ access
    • Internet Information Services
    • World Wide Web Service

    Note
    Remember to install these components on both cluster nodes.


    Configuring the Majority Node Set (MNS) Quorum with File Share Witness

    I bet some of you are thinking: What the heck is a Majority Node Set (MNS) Quorum with File Share Witness? And I understand why as this is a completely new type of quorum model, which is made available by installing the update (MS KB article 921181) mentioned in the beginning of this article series. The update makes it possible to make use of a file share witness that is external to the cluster as an additional "vote" to determine the status of the cluster in a two-node MNS quorum cluster deployment, which is a requirement in order to make use of the cluster continuous replication (or CCR in short) functionality in Exchange Server 2007.
    The file share for this file share witness can be located on any type of Windows Server in your environment, but best practice is to use an Exchange 2007 Hub Transport Server in the Active Directory server site containing the nodes in the respective cluster. We’ll also use a Hub Transport Server in this article series.
    The first thing you need to do is to create the file share on the Hub Transport server. You can do this either via the CLI or by using the GUI. In this article we’ll do so using the GUI. So log on to the Hub Transport server with a domain admin account, then open Windows Explorer and create a new folder called MNS_FSQ_E2K7CLUSTER on the C: drive or wherever you want it to be created.

    Figure 28: Majority Node Set File Share Quorum folder
    Now take Properties for the newly created folder, and click Sharing.

    Figure 29: Majority Node Set File Share Quorum Folder Share
    Click Permissions and configure the share permissions so only the Administrator (or the Cluster Service Account if created) are allowed access to the share.

    Figure 30: Share Permissions for Majority Node Set File Share Quorum folder
    Click OK then select the Security tab.

    Figure 31: Security permissions to the Majority Node Set File Share Quorum folder
    Here you should give Full Control to the local administrator and the domain administrator account or cluster service account. Make sure you untick Allow inheritable permissions from the parent to propagate to this object and all child objects when doing so, then click OK twice and log off the server.
    Back on E2K7Node1 you should set the Majority Node Set Private Property attribute to point to the file share we just created, we do so by opening a command prompt then issuing the following command:
    Cluster res “Majority Node Set” /priv MNSFileShare=\\EDFS03\MNS_FSQ_E2K7CLUSTER

    Note
    Make sure to replace server name so it matches the name of the Hub Transport Server in your environment.
    You will get a warning that all properties were stored but not all changes will take effect until the next time the resource is brought online, just like it’s shown in Figure 32 below.

    Figure 32: Configuring the Majority Node Set on E2K7Node1


    In order to force all changes to take effect, we will move the cluster group from one node to the other (will take the cluster group offline and online again). Do this using the below command:
    Cluster Group “Cluster Group” /Move

    When you have done so you will see that the cluster group is now online on E2K7Node2, as is the case in Figure 33 below.

    Figure 33: Moving the cluster group from one node to the other
    Now let’s verify the 7Priv property is set correctly, this can be done by issuing the below command:
    Cluster Res “Majority Node Set” /Priv
    As you can see in Figure 34 below, this property has been set correctly for the purpose of this article series.

    Figure 34: Verifying the property of /Priv is set correctly
    Configuring the Transport Dumpster

    When using a CCR in your environment you should consider to configure the transport dumpster on the Hub Transport Server. Microsoft recommends that you configure the MaxDumpsterSizePerStorageGroup parameter, which specifies the maximum size of the transport dumpster queue for each storage group, to a size that is 1.25 times the size of the maximum message that can be sent. For example, if the maximum size for messages is 10 megabytes (MB), you should configure the MaxDumpsterSizePerStorageGroup parameter with a value of 12.5 MB. In addition they recommend you configure the MaxDumpsterTime parameter, which specifies how long an e-mail message should remain in the transport dumpster queue, to a value of 07.00:00:00, which is 7 days. This amount of time is sufficient to allow for an extended outage to occur without loss of e-mail. When using the transport dumpster feature, additional disk space is needed on the Hub Transport server to host the transport dumpster queues. The amount of storage space required is roughly equal to the value of MaxDumpsterSizePerStorageGroup multiplied by the number of storage groups.
    You use the Set-TransportConfig CMDlet to enable and configure the Transport Dumpster. So in order to, for example, configure the maximum size of the dumpster per storage group to 25 MB with a dumpster life of 10 days, you would need to run the following command:
    Set-TransportConfig -MaxDumpsterSizePerStorageGroup 25MB -MaxDumpsterTime 10.00:00:00 In order to see the MaxDumpsterSizePerStorageGroup and MaxDumpsterTime configuration settings, you can type Get-TransportConfig as I did in the figure below.

    Figure 35: Transport Configuration Settings
    Alright we have reached the end of part two in this article series, but fear not you can look forward to seeing part three being published here on MSExchange.org in the very near future.







  3. #3
    نام حقيقي: 1234

    مدیر بازنشسته
    تاریخ عضویت
    Jul 2009
    محل سکونت
    5678
    نوشته
    5,634
    سپاسگزاری شده
    2513
    سپاسگزاری کرده
    272
    کد:
    http://www.msexchange.org/tutorials/Installing-Configuring-Testing-Exchange-2007-Cluster-Continuous-Replication-Based-Mailbox-Server-Part3.html
    PART-3

    Introduction

    In part two of this articles series we installed the necessary Windows components, enabled and configured the Majority Node Set (MNS) Quorum with File Share Witness as well as the transport dumpster on the Hub Transport Server. In this part three we’ll install Exchange Server 2007 on both nodes in the Windows 2003 cluster. We’ll then finish off by verifying that the CCR functionality works as expected.
    Installing the Active Clustered Mailbox Role on E2K7Node1

    It’s time to install the Exchange Server 2007 Beta 2 bits on each node, we’ll start with E2K7Node1. First, if you haven’t already done so, I recommend you copy the Exchange Server 2007 Beta 2 binaries to a drive locally on each node. When you have done so double-click Setup.com.

    Figure 36:
    Launching Exchange Setup
    The Exchange Server 2007 Installation Wizard will start, and as you can see Step 1: Install .NET Framework 2.0 and Step 2: Install Microsoft Management Console (MMC) have already been completed.
    Note
    If you have installed Windows Server 2003 with Service Pack 1 on each node, you need to download Microsoft Management Console (MMC) 3.0 and install it manually (by following the link in Step 2). But since I’m using Windows 2003 R2 Servers in my test environment, the MMC 3.0 is installed by default.

    Figure 37: Exchange Server 2007 Installation Menu
    As you can see we still need to complete Step 3: Install Microsoft Command Shell (MSH), before we can start installing Exchange. Therefore click the link to download MSH then unzip and install it.

    Figure 38: Installing Microsoft Command Shell (MSH)

    The Exchange Server 2007 Installation Wizard should refresh automatically, so now click Install Microsoft Exchange. Click Next then accept the License Agreement and Next once again. Decide whether you want to enable Error Reporting or not (a good idea to enable this functionality since the Exchange Product Group will receive any obscure errors you should experience in your cluster setup) then click Next.

    Figure 39: Enabling Error Reporting
    Now select Custom Exchange Server Installation then click Next.

    Figure 40: Selecting a custom Exchange Server installation
    Tick Active Clustered Mailbox Role and click Next.

    Figure 41: Selecting to install an Active Clustered Mailbox Role
    Now select Cluster Continuous Replication then specify a name for the mailbox server (the name you want your Outlook clients to connect to) and a unique IP address on your public network. Finally specify the path for the clustered mailbox server database files or use the defaults (as is the case in this article series) then click Next.

    Figure 42: Selecting to install a Cluster Continuous Replication cluster and specifying name and IP address of the clustered mailbox server
    Let the readiness check complete, and if no issues are found click Next to begin the installation.

    Figure 43: Exchange Server 2007 Clustered Mailbox Role Readiness Check
    The Exchange Server 2007 installation wizard will now copy the needed Exchange files, install and configure the Mailbox Role then finally create and configure the clustered mailbox server resources locally and create the object in Active Directory. When each step has been completed untick Exit Setup and open Exchange System Manager (yes this will be corrected in a later build), then click Finish. We don’t want to open the Exchange Management Console just yet, we’ll install Exchange on the second node first.
    Installing the Passive Clustered Mailbox Role on E2K7Node2

    Log on to E2K7Node2 with a domain admin account and do the exact same steps as we did when installing Exchange Server 2007 on E2K7Node1. Only difference is you should tick Passive Clustered Mailbox Role instead of Active Clustered Mailbox Role as shown in Figure 44 below.

    Figure 44: Installing the passive clustered mailbox role on the second node
    Verifying the functionality of the Cluster Continuous Replication based Mailbox Server

    It’s time to verify that our Exchange 2007 clustered mailbox server is working as expected. Let’s first open the Cluster Administrator and check whether the respective Exchange Resources have been created. If you take a look at Figure 45 below it looks good, we have both nodes listed in the left pane and all Exchange resources have been created and are currently owned by E2K7Node2.

    Figure 45: Listing all Exchange cluster resources in the cluster administrator
    Try to open the Exchange Management Shell by clicking Start > All Programs > Microsoft Exchange Server 2007 > Exchange Management Shell on one of the nodes, then type Get-ClusteredMailboxServerStatus –Identity E2K7CCR. As you can see in Figure 46 below the status of the clustered mailbox server is Online, and E2K7Node2 is currently the active node.

    Figure 46: Requesting the online status of the clustered mailbox server
    Now that we have verified the clustered mailbox server is online, let’s try to move the Exchange resources from node one to node two using the Move-ClusteredMailboxServer CMDlet. In the test environment used in this article, we do so by issuing below CMDlet:
    Move-ClusteredMailboxServer -Identity:E2K7CCR -TargetMachine:E2K7Node1 -MoveComment:"This is a test!" You’re then asked to confirm this action, type Yes then hit Enter. After a while the clustered mailbox resources will have been moved to the first node.

    Figure 47: Moving the clustered mailbox resources to the first node
    Note
    Even though it’s possible to move the cluster resource groups between nodes using the Cluster Administrator console, you should always do so using the Move-ClusteredMailboxServer CMDlet as the Move Group task in the Cluster Administrator console isn’t Exchange 2007 aware.
    Let's also take a look at the clustered mailbox server in the Exchange Management Console. To do so click Start > All Programs > Microsoft Exchange Server 2007 > Exchange Management Console, then drill down do Server Configuration > Mailbox. Notice the clustered mailbox server which we named E2K7CCR is listed in the Result pane and that it’s recognized as a cluster server.

    Figure 48: Viewing the clustered mailbox server in the Exchange Management Console
    Let’s try to take a look at the transaction log file replay from one node to the other. The easiest way to do that is to generate a few log files by sending a couple of test messages with an attachment or two.


    Note
    Since the new transaction log file size in Exchange Server 2007 is 1 MB instead of 5 MB as was the case in previous versions of Exchange. It’s not required to attached files larger than 1 MB in order to generate these log files.
    As you can see in Figure 49 below, the log files were replayed to E2K7Node2 within the same minute as they were generated on E2K7Node1.

    Figure 49: Log file replay
    Simulating a failover from E2K7Node1 to E2K7Node2

    Okay let’s try to simulate a fail over from E2K7Node1 (which currently is the active node) to E2K7Node2, so that we can see what will happen from the Outlook client perspective. In order to switch from one node to the other we’ll issue below CMDlet which we also used earlier on in this article:
    Move-ClusteredMailboxServer -Identity:E2K7CCR -TargetMachine:E2K7Node2 -MoveComment:"This is a test!" When a manual move or a failover occurs, the balloon shown in Figure 50 will appear as all services needs to be stopped on E2K7Node1 before they are brought online on E2K7Node2.

    Figure 50: Connection to the Exchange Server has been lost
    Depending on the amount as well as size of the databases in your Cluster Continuous Replication setup, this will take somewhere between 10 seconds to approximately 1 minute, which shouldn’t cause panic for the end-users. When E2K7Node2 has taken over, the end-users will be notified that the connection to the Exchange Server has been restored (Figure 51).

    Figure 51: Connection to the Exchange Server has been restored
    Conclusion

    You benefit from several advantages when you choose to install the Exchange 2007 Mailbox Server role in a Cluster Continuous Replication setup in your organization. The primary reason here is that you no longer have a single point of failure, when talking about the Mailbox/Public Folder databases. Should the database on one node crash, an automatic fail over to the other node containing the secondary database is completed. This also means you no longer need to use a shared storage system in the CCR setup, as is the case with Exchange 2007 Single Copy Clusters as well as cluster setup in previous versions of Exchange. In addition the two nodes in the CCR setup can even be placed in two different locations, as long as they belong to the same subnet. Not only that, the installation of the Exchange 2007 cluster has also been further simplified over previous versions. Since CCR setup makes use of log file shipping and replay to a secondary database, you also don’t have to do full online backups far as often as was the case in Exchange 200x and earlier versions. Last but certainly not least, the fail over process been improved in several areas now that the new file share witness model have been introduced.






کلمات کلیدی در جستجوها:

complete guidance of exchange server 2008

ارسال 2008 inbox sur rdp

EX2007 Node Config Unable to retrieve configuration from

a file share witness has not configured.Set the MNSFilesharemove the cluster group twice on single copy cluster

how to verify ccr cluster instalation

Cluster res “Majority Node Set” /priv MNSFileShare=\EDFS03MNS_FSQ_E2K7CLUSTER meaning

1

enable-continuousreplicationhostname example

in exchange shell the command completed successfully but no changes...

test replication ccr

Enable-ContinuousReplicationHostName Cluster validation failed The clustered mailbox servers specified IP address could not be used because it is already in us

instalasi GUI

The following warning(s) occurred while saving changes:set-TransportConfig Completed Warning:The command completed successfully but no changes were made

CCR-based messages

testing clustering in exchange 2007

move-ClusteredMailboxServer error the mailbox role is not configured

Move-ClusteredMailboxServer THE MAILBOX SERVER ROLE IS NOT CONFIGURED

exchange 2007 cluster administrator

unable to find resource path cluster /res majority node set

exchange 2007 cluster drill test

برچسب برای این موضوع

مجوز های ارسال و ویرایش

  • شما نمی توانید موضوع جدید ارسال کنید
  • شما نمی توانید به پست ها پاسخ دهید
  • شما نمی توانید فایل پیوست ضمیمه کنید
  • شما نمی توانید پست های خود را ویرایش کنید
  •