ccr exchange 2007 concept

65
Microsoft Exchange Server 2007 Cluster Continuous Replication (CCR) proof of concept Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Exchange 2007 continuous replication technology . . . . . . . . . . . . . 3 Cluster Continuous Replication (CCR) . . . . . . . . . . . . . . . . 3 Solution conguration . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Conguration overview . . . . . . . . . . . . . . . . . . . . . . . . 4 Network conguration . . . . . . . . . . . . . . . . . . . . . . . . . 4 Datacenter hardware conguration . . . . . . . . . . . . . . . . . . . 4 Active Directory conguration . . . . . . . . . . . . . . . . . . . . . 5 Server conguration . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Mailbox server . . . . . . . . . . . . . . . . . . . . . . . . . . 6 EVA SAN storage for mailbox servers . . . . . . . . . . . . . . . . 6 Hub transport server/Client access server . . . . . . . . . . . . . . 7 Active Directory Global catalog/DNS servers . . . . . . . . . . . . 8 LoadGen servers . . . . . . . . . . . . . . . . . . . . . . . . . 8 Exchange LoadGen conguration . . . . . . . . . . . . . . . . . . . . 8 Naming convention . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Storage conguration . . . . . . . . . . . . . . . . . . . . . . . . . 10 Storage planning . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Test objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Functional testing . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Exchange Best Practice Analyzer . . . . . . . . . . . . . . . . . . 12 Exchange Prole Analyzer . . . . . . . . . . . . . . . . . . . . . 13 Database seeding . . . . . . . . . . . . . . . . . . . . . . . . 14 Loss of storage connectivity . . . . . . . . . . . . . . . . . . . . . 15 Loss of network connectivity . . . . . . . . . . . . . . . . . . . . 16 Performance testing . . . . . . . . . . . . . . . . . . . . . . . . . . 17 LoadGen runs . . . . . . . . . . . . . . . . . . . . . . . . . . 17 LoadGen Run 080212 . . . . . . . . . . . . . . . . . . . . . . 19 Comparison of client workload . . . . . . . . . . . . . . . . . 20 Effect of server memory on database IOPS . . . . . . . . . . . . 21 Effect of server memory on processor use . . . . . . . . . . . . . 24 Effect of server memory on RPC averaged latency . . . . . . . . . 25 Effect of server memory on RPC requests . . . . . . . . . . . . . 26 Database cache size . . . . . . . . . . . . . . . . . . . . . 27 Hub transport (HT) delivery queues . . . . . . . . . . . . . . . 28 Test ndings summary LG Run 080212 . . . . . . . . . . . . . 29 LoadGen Run 080214 . . . . . . . . . . . . . . . . . . . . . . 29 Effect of server memory on disk transfers per second . . . . . . . . 30 Effect of server memory on processor use . . . . . . . . . . . . . 31 Effect of server memory on RPC averaged latency . . . . . . . . . 32 Effect of server memory on RPC requests . . . . . . . . . . . . . 32

Upload: sunilbansal1

Post on 18-Nov-2014

108 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: CCR Exchange 2007 Concept

Microsoft Exchange Server 2007 Cluster ContinuousReplication (CCR) proof of concept

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Exchange 2007 continuous replication technology . . . . . . . . . . . . . 3

Cluster Continuous Replication (CCR) . . . . . . . . . . . . . . . . 3 Solution configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Configuration overview . . . . . . . . . . . . . . . . . . . . . . . . 4 Network configuration . . . . . . . . . . . . . . . . . . . . . . . . . 4 Datacenter hardware configuration . . . . . . . . . . . . . . . . . . . 4 Active Directory configuration . . . . . . . . . . . . . . . . . . . . . 5 Server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Mailbox server . . . . . . . . . . . . . . . . . . . . . . . . . . 6 EVA SAN storage for mailbox servers . . . . . . . . . . . . . . . . 6 Hub transport server/Client access server . . . . . . . . . . . . . . 7 Active Directory − Global catalog/DNS servers . . . . . . . . . . . . 8 LoadGen servers . . . . . . . . . . . . . . . . . . . . . . . . . 8

Exchange LoadGen configuration . . . . . . . . . . . . . . . . . . . . 8 Naming convention . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Storage configuration . . . . . . . . . . . . . . . . . . . . . . . . . 10 Storage planning . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Test objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Functional testing . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Exchange Best Practice Analyzer . . . . . . . . . . . . . . . . . . 12 Exchange Profile Analyzer . . . . . . . . . . . . . . . . . . . . . 13 Database seeding . . . . . . . . . . . . . . . . . . . . . . . . 14 Loss of storage connectivity . . . . . . . . . . . . . . . . . . . . . 15 Loss of network connectivity . . . . . . . . . . . . . . . . . . . . 16

Performance testing . . . . . . . . . . . . . . . . . . . . . . . . . . 17 LoadGen runs . . . . . . . . . . . . . . . . . . . . . . . . . . 17 LoadGen Run 080212 . . . . . . . . . . . . . . . . . . . . . . 19

Comparison of client workload . . . . . . . . . . . . . . . . . 20 Effect of server memory on database IOPS . . . . . . . . . . . . 21 Effect of server memory on processor use . . . . . . . . . . . . . 24 Effect of server memory on RPC averaged latency . . . . . . . . . 25 Effect of server memory on RPC requests . . . . . . . . . . . . . 26 Database cache size . . . . . . . . . . . . . . . . . . . . . 27 Hub transport (HT) delivery queues . . . . . . . . . . . . . . . 28 Test findings summary − LG Run 080212 . . . . . . . . . . . . . 29

LoadGen Run 080214 . . . . . . . . . . . . . . . . . . . . . . 29 Effect of server memory on disk transfers per second . . . . . . . . 30Effect of server memory on processor use . . . . . . . . . . . . . 31 Effect of server memory on RPC averaged latency . . . . . . . . . 32 Effect of server memory on RPC requests . . . . . . . . . . . . . 32

Page 2: CCR Exchange 2007 Concept

HT delivery queues . . . . . . . . . . . . . . . . . . . . . . 33 Test findings summary − LG Run 080214 . . . . . . . . . . . . . 34

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 We value your feedback . . . . . . . . . . . . . . . . . . . . . . . . 36

Appendix A Performance measurement . . . . . . . . . . . . . . . . . . . 37 Performance counter objects . . . . . . . . . . . . . . . . . . . . . . 37

Appendix B Bill of materials . . . . . . . . . . . . . . . . . . . . . . . . 39 Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 EVA8100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Appendix C Exchange 2007 script samples . . . . . . . . . . . . . . . . . 41 Script reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

EVA configuration . . . . . . . . . . . . . . . . . . . . . . . . 41 Mailbox server management . . . . . . . . . . . . . . . . . . . . 41

Exchange provisioning for mailbox servers . . . . . . . . . . . . 44 Appendix D Server build checklist . . . . . . . . . . . . . . . . . . . . . . 62

Server build consistency . . . . . . . . . . . . . . . . . . . . . . . . 62 Appendix E EVA disk position . . . . . . . . . . . . . . . . . . . . . . . 64

Physical EVA configuration . . . . . . . . . . . . . . . . . . . . . . . 64 For more information . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Page 3: CCR Exchange 2007 Concept

Overview

Customers routinely request assistance from HP in validating the use of Microsoft Server Exchange

2007 and its new features, such as Cluster Continuous Replication (CCR), before they implement it into production.

For this proof of concept (POC) project, HP replicated 28,000 user mailboxes in an Exchange 2007

CCR configuration. This quantity is chosen by calculating the number of mailboxes that could be

supported on a single Enterprise Virtual Array (EVA) 8100, while allowing a portion of disks on

each EVA for fibre-attached ATA (FATA) drives to store disk-based backups. This design also allows for EVA growth by adding drives. The EVA 8100 is flexible and is capable of supporting different configurations based on different design criteria. The EVA configuration used fits the requirements of the design for this specific project.

A second EVA8100 and seven Exchange 2007 servers are used to host the CCR passive nodes of the mailbox servers.

Exchange 2007 continuous replication technology

The continuous replication model uses host-based replication to protect against both server and

storage failure.

Cluster Continuous Replication (CCR)

In this configuration, Exchange 2007 CCR nodes are deployed within the same datacenter. This allows for failover to a secondary node, with a separate copy of Exchange 2007 database data, in the event of an active cluster node failure.

An interesting feature of Exchange 2007 CCR is its ability to implement Exchange backups on the

passive node of the CCR cluster. This reduces the performance impact on the active node during

backup operations, which allows for a longer backup window. Backup is not tested as part of this project.

3

Page 4: CCR Exchange 2007 Concept

Solution configuration

Configuration overview

The general configuration represents a single datacenter site, which depicts the most likely

configuration for CCR deployment.

Figure 1. Configuration overview – Logical

Network configuration

For this proof of concept, the network configuration consists of HP ProCurve 2900 48G 48-port Gigabit Ethernet switches placed into the server racks. This particular switch platform is chosen to

provide VLAN capability for network traffic segmentation between Exchange CCR clusters, should

this functionality be needed for the required performance level.

Datacenter hardware configuration

Figure 2 shows the datacenter server hardware configuration.

4

Page 5: CCR Exchange 2007 Concept

Figure 2. Server hardware configuration - Physical

Active Directory configuration

Active Directory is configured as a single forest containing a single domain and single site. Multiple

global catalog servers are configured for redundancy and to ensure that directory lookups are not a

source of performance bottlenecks for this configuration.

DNS is implemented on all domain controllers and the DNS zones are configured as Active Directory

integrated with both forward and reverse lookup zones.

Server configuration

This design determines the proper server distribution and sizing, and the storage configuration. The

infrastructure component configurations have been maintained as closely as possible with Microsoft best practices to ensure a valid proof of concept. The configurations for Exchange 2007 CCR

represent a calculated approximation and are validated throughout testing. The configurations are

based on the use of the Microsoft Storage Planning Calculator and the HP Exchange 2007 Calculator.

5

Page 6: CCR Exchange 2007 Concept

Mailbox server

DL380 G5 − two processors x 4-core − 16 GB RAM

• Host bus adapters: One 4-Gb dual-port HBA (FC2242SR)

• Network: NC360T dual-port PCI-E GigE (private and public network)

• Microsoft® Windows® Server 2003 Enterprise x64 R2, Service Pack 2

• Exchange 2007 Enterprise, Service Pack 1

Table 1. Local storage - Mailbox server

Drive Purpose Size RAID type

C: Operating system 2 – 72 GB 15 K RAID 1

EVA SAN storage for mailbox servers

In this design, three LUN presentation methodologies are used in the configuration to compare

administrative usability:

• Single drive letter per LUN presented to the mailbox server

• Multi-root mount point with one anchor mount point per database and log LUN pair

• Dual-root mount point with one anchor mount point for all database LUNs and another anchor mount point for all log LUNs

Table 2. Single drive letter configuration

Drive Purpose Storage groups Size – RAID type

F: Database LUN 1 SG1 – SG7 431 GB – Vraid 1

G: Log LUN 1 SG1 – SG7 166 GB – Vraid 1

H: Database LUN 2 SG8 – SG14 431 GB – Vraid 1

I: Log LUN 2 SG8 – SG14 166 GB – Vraid 1

J: Database LUN 3 SG15 – SG21 431 GB – Vraid 1

K: Log LUN 3 SG15 – SG21 166 GB – Vraid 1

L: Database LUN 4 SG22 – SG27 370 GB – Vraid 1

M: Log LUN 4 SG22 – SG27 142 GB – Vraid 1

6

Page 7: CCR Exchange 2007 Concept

Table 3. Multi-root mount point configuration

Drive Purpose Storage groups Size – RAID type

F: SG01-07_MP

Database LUN 1 SG1 – SG7 431 GB – Vraid 1

Log LUN 1 SG1 – SG7 166 GB – Vraid 1

G: SG08-14_MP

Database LUN 2 SG8 – SG14 431 GB – Vraid 1

Log LUN 2 SG8 – SG14 166 GB – Vraid 1

H: SG15-21_MP

Database LUN 3 SG15 – SG21 431 GB – Vraid 1

Log LUN 3 SG15 – SG21 166 GB – Vraid 1

I: SG22-27_MP

Database LUN 4 SG22 – SG27 370 GB – Vraid 1

Log LUN 4 SG22 – SG27 142 GB – Vraid 1

Table 4. Dual-root mount point configuration

Drive Purpose Storage groups Size – RAID type

F: DB - Mount point anchor

Database LUN 1 SG1 – SG7 431 GB – Vraid 1

Database LUN 2 SG8 – SG14 431 GB – Vraid 1

Database LUN 3 SG15 – SG21 431 GB – Vraid 1

Database LUN 4 SG22 – SG27 370 GB – Vraid 1

G: Logs - Mount point anchor

Log LUN 1 SG1 – SG7 166 GB – Vraid 1

Log LUN 2 SG8 – SG14 166 GB – Vraid 1

Log LUN 3 SG15 – SG21 166 GB – Vraid 1

Log LUN 4 SG22 – SG27 142 GB – Vraid 1

Hub transport server/Client access server

The hub transport (HT) and client access servers (CAS) are combined in this implementation. The

CAS server provides Outlook clients with access to the availability service and auto-discovery service,

and also serves as the web-based distribution point for the offline address book (OAB).

The file share witness (FSW) for the mailbox cluster servers is placed on one of the

HT/CAS servers per Microsoft’s best practice recommendation. For more information, see

http://technet.microsoft.com/en-us/library/bb123996.aspx.

DL380 G5 - one processor x 4-core - 8 GB RAM

• Network: NC360T dual-port PCI-E GigE

• Windows Server 2003 Enterprise x64 R2, Service Pack 2

• Exchange 2007 Enterprise, Service Pack 1

7

Page 8: CCR Exchange 2007 Concept

Table 5. Local storage - HT/CAS server

Drive Purpose Size (drives) RAID type

C: Operating system 2 – 72 GB 15 K RAID 1

T: Transport queue 2 – 72 GB 15 K RAID 1

Z: DVD-ROM

Active Directory − Global catalog/DNS servers

DL580 G3 − two processors x 4-core - 16 GB RAM

• Network: NC7782 Gigabit Server Adapter

• Windows Server 2003 Enterprise x64 R2, Service Pack 2

Table 6. Local storage - AD server

Drive Purpose Size RAID type

C: Operating system 2 – 72 GB 15 K RAID 1

Z: DVD-ROM

LoadGen servers

DL385 G2 - 2 processors x 2-core - 4 GB RAM

• Network: NC373i dual-port PCI-E GigE

• Windows Server 2003 Enterprise x64 R2, Service Pack 2

• Each client is expected to run 3,500 LoadGen client sessions

• LoadGen Buddy Build 08.02.0020

Table 7. Local storage - LoadGen server

Drive Purpose Size RAID type

C: Operating system 2 – 72 GB 15 K RAID 0

Z: DVD-ROM

Exchange LoadGen configuration

Exchange mail message traffic is generated using Exchange 2007 Load Generator (LoadGen). LoadGen will simulate 28,000 Outlook clients, at 100% concurrency.

The LoadGen configuration consists of a master server that controls the LoadGen environment, and

up to eight remote servers that generate the load against the Exchange environment.

An average Outlook 2007 cached-mode workload—10 messages sent and 40 received per day—is targeted for use in load generation with an average message size of 104 KB. Each mailbox is initialized with approximately 205 MB of data.

LoadGen generates a steady workload across the entire simulated day and does not generate

workload peaks that are seen in a production environment. By contrast, the Microsoft Storage

Planning Calculator used to size this configuration generates sizing based on the peak two hours of the day—when it is expected that the majority of users will log in, read and reply to their e-mail

8

Page 9: CCR Exchange 2007 Concept

messages, and send new messages. This creates a difference in the type of work the mailbox servers are performing in the test environment, which results in a lower, more even load when using LoadGen.

Naming convention

Using a well-thought-out naming convention is critical for operational efficiency. It allows rapid

identification of server names, server roles, databases, and storage group names. The consistent use of a sound naming convention allows for more rapid development of a script library to enable

accurate and repeatable Exchange administration.

The following are the naming conventions used for objects in this configuration.

Active Directory domain suffix:

Cft.lab is the domain name.

General server:

HT denotes hub transport, and the 01 numeric suffix denotes uniqueness.

Mailbox server:

MB1 denotes Mailbox Cluster 1, and the N1 suffix denotes Node 1.

Storage group/database:

MB1 denotes Mailbox Cluster 1, SG01 denotes Storage Group 01, and DB01 denotesDatabase 01.

9

Page 10: CCR Exchange 2007 Concept

The naming convention can be expanded to include additional information for easy sorting of servers by location and function. The following example shows a site name that is added to the

beginning of the server name.

The advantage of this naming convention is that objects will first sort by site groups, then by object type groups, and finally by uniqueness number.

Storage configuration

The HP StorageWorks Enterprise Virtual Array (EVA) 8100 platform is used to host all Exchange

2007 SAN storage.

HP StorageWorks 4/32B SAN switches are used for Fibre Channel (FC) connectivity between

the server host bus adapters (HBAs) and the EVA. The switches are deployed in a stand-alone

configuration with two switches shared per EVA. Use of the HP MPIO full-featured DSM for EVA4x00/6x00/8x00 families of disk arrays permit multi-path I/O from the servers to the EVA for fault tolerance.

LUNs on the EVA are balanced across both controllers with both the database and log LUNs for a

particular set of Exchange storage groups hosted on the same controller.

Note

In this testing, it is important to understand the performance and capacity profiles for the user mailboxes to calculate the appropriate storage requirements. Since this is the testing objective, the tables below represent the best guess for this unique environment.

Storage planning

The Microsoft Exchange 2007 Storage Calculator v9.4 and the HP Storage Planning Calculator are used to generate the figures for this configuration. The configuration is based on a maximum

10

Page 11: CCR Exchange 2007 Concept

database size of 40 GB, not including overhead. Both performance and capacity are analyzed to

derive the tested configuration. For links to these calculators, see For more information.

Table 8. Storage overview for Exchange mailbox servers

Mailboxes/DB DB size DB size + overhead Log size + overhead

148 39 GB 47 GB 19 GB

Note

It is important to consider factors such as database white space, deleted items dumpster, content indexing, and maintenance in the total storage provisioning.

Table 9. Storage layout for 28,000 mailboxes per replica

Disk group # of disks Capacity – usable Contents

Database DG 133 ~ 17.8 TB (300 GB, 15 K RPM) Databases

Log DG 47 ~ 5.9 TB (300 GB, 15 K RPM) Logs

Best practice

EVA best practice is to have a number of disks divisible by eight. Formatted capacity of the 300 GB drive is ~ 279 GB.

11

Page 12: CCR Exchange 2007 Concept

Testing

Test objectives The objectives for this project include:

• Functional validation of Exchange 2007 SP1 CCR configuration

• Performance assessment of configuration to support 28,000 user mailboxes

Functional validation centers on simulating common equipment failure scenarios to ensure the impact of implementing CCR will not adversely affect the Outlook user’s experience. Functional testing is performed while running LoadGen to simulate Outlook client load and to closely simulate production

failures.

The following objectives are used to develop test scenarios:

• Validate StorageWorks EVA8100 configuration to support 28,000 mailboxes.

• Verify that acceptable server and storage performance occurs using the tested configuration.

• Verify that the failover and failback process works as expected under the following scenarios:

– Loss of HBA connectivity to FC switch

– Loss of HSV210B controller connectivity to FC switch

– Loss of HSV210B controller cache

– Loss of network connectivity at the server

– Loss of server power

– Loss of EVA cabinet power

Functional testing

Functional testing is performed to ensure the Exchange configuration is in a healthy state and is able

to operate as expected. Functional testing is also used to perform common operations required when

running an Exchange CCR configuration and to simulate failures while observing the results of the failure.

Issues identified during functional testing are noted below.

Exchange Best Practice Analyzer

Microsoft recommends using the Exchange Best Practice Analyzer (ExBPA) to generate a report depicting the health of the Exchange environment. ExBPA is included in the Exchange Management Console and is located in the toolbox. ExBPA automatically updates when running to ensure the most recent Microsoft best practices published are incorporated into the tool.

HP recommends that you run ExBPA when initially setting up the Exchange environment and run ExBPA

periodically, or when changes are made to Exchange, to make sure the configuration is healthy.

The ExBPA report shows the following results:

• Informational: Crash upload logging disabled.

This is expected since this is disabled by default.

12

Page 13: CCR Exchange 2007 Concept

• Informational: Outlook connection range.

This is expected since all versions of Outlook are permitted in this configuration.

• Warning: Dedicated heartbeat not found.

This is expected due to the current configuration.

• Warning: MaxUserPort missing or non-default.

The expected value is 60,000. However, Exchange 2007 SP1 sets this to a higher value of 65,000 by default.

Figure 3. Exchange Best Practices Analyzer results

Exchange Profile Analyzer

Exchange Profile Analyzer (ExPA) analyzes a set of Exchange servers and provides statistical information regarding the distribution of messages. ExPA allows the detailed analysis of the size

and quantity of messages at the server level, database level, and individual mailbox level, which

identifies the distribution of messages in an Exchange environment.

Figure 4 depicts the results captured by running ExPA against one of the CCR databases.

13

Page 14: CCR Exchange 2007 Concept

Figure 4. Exchange Profile Analyzer results

The calculation below gives the rough approximation of the average message size of 72.34 KB.

The discrepancy between the 104 KB original average message size and the tested value is due to

the newer LoadGen build and the reduction in average message size from the older version to the

newer version. The newer versions of LoadGen are used at the recommendation of the Microsoft LoadGen team during troubleshooting of LoadGen.

Database seeding

The Exchange CCR database seeding operation is responsible for the initial creation of data on the

passive node of the CCR cluster. The seeding operation is also performed when the database on

the passive node is out of date with the active node. This out-of-date condition may be caused by

several events, such as the prolonged unavailability of a server node or corrupt log files in the

passive node log sequence.

Testing is performed to determine the effect of the use of Cluster Administrator to manipulate the

passive node Windows cluster resources:

1. The passive node is evicted from the Windows cluster using Cluster Administrator.

14

Page 15: CCR Exchange 2007 Concept

2. The database and log data are deleted on the passive node.

3. The passive node is joined back into the Windows cluster using Cluster Administrator.

4. The data from the active CCR node is replicated to the passive CCR node.

Run the Update-StorageGroupCopy Cmdlet from the passive node, or copy the database

from the active CCR node to the passive CCR node.

During the seeding process, which is used to move data to the passive CCR node, we discover that the passive node is unable to perform the reseed operation. The following procedure is performed to

permit successful seeding of the passive CCR node.

1. Uninstall the passive mailbox server role on the passive node.

2. Ensure the file locations for database and transaction logs are empty.

3. Ensure the passive node is a member of the Windows cluster.

4. Reboot.

5. Install the passive mailbox server role on the passive node.

6. Reboot.

7. Turn off Microsoft Exchange Search Indexer service to reduce load while seeding.

8. Suspend storage group copy for all storage groups.

9. Update storage group copy from the passive node for all storage groups.

10. Wait for the database seeding to complete.

11. Ensure all storage groups report healthy.

12. Move the Exchange and Windows cluster resources to the passive node to verify that all functionality is restored.

Once the steps above are completed, seeding of the databases has successfully completed.

Loss of storage connectivity

Each node of the Exchange CCR cluster pair is connected to a separate EVA8100, unlike single

copy clusters (SCC) that use shared storage. Due to the use of CCR, two copies of the Exchange

database and log files exist. This provides the advantage of an up-to-date copy of the Exchange

data for recovery.

Testing is performed to determine if the loss of the dedicated Exchange storage from the active node

will adversely affect the availability of Exchange services to Outlook clients. This testing is performed

while LoadGen is running against three of the mailbox clusters.

The following test cases have similar results and are grouped together for convenience:

• Loss of HBA connectivity to FC switch

• Loss of HSV210B controller connectivity to FC switch

• Loss of EVA cabinet power

15

Page 16: CCR Exchange 2007 Concept

Figure 5. Storage or storage connectivity loss

Outcome

• Windows cluster resources (IP, cluster name and quorum) stay online.

This is expected.

• Exchange cluster resources (IP, network name, system attendant, and information store) stay online.

This is expected.

• Exchange database resources are dismounted upon loss of connectivity to storage.

This is expected.

Impact

• It is expected that the loss of storage on the active node will take the Exchange databases offline. This will have a significant impact to the users as they will lose connectivity to their mailboxes. This is due to the fact that there are no cluster disk resources when using Exchange CCR.

• In production, the use of E2K7 CCR will require monitoring of database states using a tool, such

as Microsoft Operations Manager, to alert the operations team that the Exchange databases are

in a dismounted state and require manual intervention.

Loss of network connectivity

Each Exchange CCR cluster node is configured with public and private network connections. The

public network is used by default for client and replication traffic, while the private network is used

for heartbeat traffic.

Testing is performed to determine if the loss of network connectivity by the active node will adversely

affect Exchange services availability to Outlook clients. This test is performed while LoadGen is running against three of the mailbox clusters.

The following cases had similar results and are grouped together for convenience:

16

Page 17: CCR Exchange 2007 Concept

• Loss of network connectivity at the server

• Loss of server power

Figure 6. Network loss or server power loss

Outcome

• Windows cluster resources (IP, cluster name, and quorum) failover to the passive node.

This is expected.

• Exchange cluster resources (IP, network name, system attendant, and information store) failover to the passive node.

This is expected.

• Exchange database resources failover to the passive node and are mounted.

This is expected.

Impact

• In production, the use of E2K7 CCR will require monitoring of database states using a tool, such

as Microsoft Operations Manager, to alert the operations team in the event that any Exchange

database is in a dismounted state. This condition can occur after the automated failover to

the passive node and will require manual intervention. The ability to automatically mount databases is affected by the AutoDatabaseMountDial attribute. This attribute can be set using

the Set-MailboxServer Cmdlet to one of three values: Lossless, Good Availability, and

Best Availability. Each of these settings determines the quantity of transaction logs that can be

missing, and the database still mounts successfully.

Performance testing

LoadGen runs

In the course of LoadGen testing, Microsoft was consulted due to concerns about using LoadGen

to generate a stable test run. Subsequent to this, multiple versions of LoadGen were built by the

17

Page 18: CCR Exchange 2007 Concept

Microsoft LoadGen team to improve the way LoadGen handles the interaction between the master server and the LoadGen remote clients. LoadGen version 08.02.0008 was used for this testing. Throughout the debugging process, as the LoadGen builds were changed and provided to us, the functionality of LoadGen changed, resulting in unexpectedly low per user IOPS. Subsequent investigation with Microsoft reveals that this is a function of the reduction of the LoadGen default average message size from 50 KB to 32 KB, and the reduction of the type of work being performed

by LoadGen. The reduction in I/O is revealed when analyzing the IOPS per user from test runs and

by working with Microsoft through additional debugging runs. For the specific testing performed

during this project, Microsoft recommended the use of the LoadGen online-heavy profile (20 sent/80

received) for subsequent test runs to increase the IOPS generated.

Based on Microsoft’s recommendation, LoadGen load balancing is not used with the remote load

generator configuration for this testing.

Initialization runs

• LoadGen is run multiple times to initialize the test environment due to the following:

– One run is required to create each of the seven server object organizational units (OUs) in

Active Directory (AD) during LoadGen topology creation. The objects are then populated

into the created OU. Each subsequent run creates the next server object OU and allows the

creation of objects into that OU. This issue has been reported to Microsoft.

– Initialization is run multiple times as new LoadGen buddy builds are released to address issues experienced.

Debugging runs

• The Microsoft LoadGen team spent many cycles performing debugging in this POC environment to address LoadGen issues, including the use of remote LoadGen servers.

• The LoadGen XML file and configuration used for debugging that specified Outlook 2007 online

heavy mode is used for subsequent testing.

• Testing reveals that LoadGen tasks are being queued across all of the LoadGen remote servers, and the Microsoft LoadGen developer recommends the reconfiguration of network resources. As part of this reconfiguration, the Scalable Network Pack TCP Chimney Offload feature in Windows 2003 R2 (and above) is disabled by running the following command:

Netsh int ip set chimney DISABLED

This results in the LoadGen task queues dropping as the tasks are processed until the queues are

empty. This behavior is consistent on all LoadGen remote servers. Microsoft has since released a

critical update for Windows Server 2003 that disables this feature. For more information, see

http://support.microsoft.com/?kbid=948496.

Performance capture runs

• The performance capture runs were completed with LoadGen in the post-debugging configuration

without any additional initializations or baselines being performed. The profile used is Outlook

2007 Online-Heavy per Microsoft recommendation.

• The LoadGen runs are configured for an eight-hour simulated day with a ten hour run time.

18

Page 19: CCR Exchange 2007 Concept

• Performance capture is only started after the LoadGen test engines are started on the LoadGen

master server. This is a requirement to successfully capture LoadGen engine performance data. Performance capture runs are configured to automatically stop after ten hours.

• A steady-state time period is chosen from the middle of the test run for analysis to ensure that LoadGen events, such as client logon and Exchange online maintenance, are not analyzed.

• Data captured is then compared against Microsoft-recommended thresholds to ensure an

acceptable client experience.

• Data represented for comparison is from the same database LUNs across all tests. Data from

multiple LUNs and counters are reviewed, and a representative sample is included in this document.

• LoadGen does not perform an identical workload on each server, and some variation is seen

in the data reported.

LoadGen Run 080212

Testing for LoadGen Run 080212 is performed using LoadGen Outlook 2007 Online-Heavy. LoadGen did not generate a high enough load to be able to extrapolate a normal user load. The

normal user load expected from LoadGen testing using the Outlook 2007 Online-Heavy profile is 0.40 IOPS or above.

Figure 7 depicts the disk transfers per second on database LUNs for the entire duration of LG

Run 080212. The data shows the initial LoadGen logon and ramp up, and the start of online

maintenance.

19

Page 20: CCR Exchange 2007 Concept

Figure 7. LG Run 080212 - database LUN - overview

The data contained in Figure 7 is only used to determine the steady-state time period used for further analysis of this test run (1900 hours to 2200 hours).

Comparison of client workload

The expected client workload for a LoadGen Default Outlook 2007 Online-Heavy profile is 20

sent/80 received.

Figure 8 shows the actual workload generated during the test standardized to an eight-hour day. The

following calculation is used to adjust for the three-hour, steady-state window.

Calculation:

(((Max-Min)/3)*8)/users on server = Messages sent or received per day per user

The average sent/received per user per day across all servers is shown in Figure 8.

20

Page 21: CCR Exchange 2007 Concept

Figure 8. LG Run 080212 - Message send and receive statistics

Effect of server memory on database IOPS

Figure 9, Figure 10, and Figure 11 depict the disk I/O on the first database LUN on each of the

three Exchange 2007 CCR clusters configured for the LG Run 080212.

Modification is made to reduce the quantity of memory on two servers to allow the simultaneous testing of the effect of memory. It is important to reiterate that LoadGen averages work evenly across the entire day, while actual production workload will reveal peaks and valleys.

The server memory configuration for LG Run 080212 is as follows:

• MB2N1 − 16 GB RAM

• MB3N1 − 12 GB RAM

• MB4N1 − 8 GB RAM

21

Page 22: CCR Exchange 2007 Concept

Figure 9. LG Run 080212 - MB2N1 - 16 GB RAM

22

Page 23: CCR Exchange 2007 Concept

Figure 10. LG Run 080212 - MB3N1 - 12 GB RAM

23

Page 24: CCR Exchange 2007 Concept

Figure 11. LG Run 080212 - MB4N1 - 8 GB RAM

In this test, additional memory reduces the I/O requirement for a mailbox server. The most dramatic

effect is achieved when comparing the 16 GB (0.074 IOPS per user) and 12 GB (0.155 IOPS per user) configurations, which reflects twice the database I/O with the reduction of memory.

Effect of server memory on processor use

Figure 12 depicts the processor use on each of the three Exchange 2007 CCR clusters configured

for the LG Run 080212. The server memory configuration ranges from 16 GB to 8 GB and is denoted on the charts.

24

Page 25: CCR Exchange 2007 Concept

Figure 12. LG Run 080212 - % processor time

Note

The % processor time value is well below the MS recommendation of less than 90 (at all times).

There is a small impact on CPU use with the change in the amount of RAM. There is sufficient processor headroom to support the use of third-party applications, such as anti-virus scanners.

Effect of server memory on RPC averaged latency

Figure 13 depicts the RPC averaged latency on each of the three Exchange 2007 CCR clusters configured for the LG Run 080212. The server memory configuration ranges from 16 GB to 8 GB

and is denoted on the charts.

25

Page 26: CCR Exchange 2007 Concept

Figure 13. LG Run 080212 - RPC averaged latency

Note

RPC averaged latency is well below the MS recommendation of less than 50 ms.

In this test, additional memory positively affects the RPC averaged latency on the mailbox server. At no time does the RPC averaged latency approach or exceed the Microsoft-recommended threshold of 50 ms. The effect of database cache is apparent when comparing the 8 GB and 16 GB data. Client requests are most efficiently served from cache and not from disk.

Effect of server memory on RPC requests

Figure 14 depicts the number of RPC requests outstanding on each of the three Exchange 2007 CCR

clusters configured for the LG Run 080212. The server memory configuration ranges from 16 GB to

8 GB and is denoted on the charts.

26

Page 27: CCR Exchange 2007 Concept

Figure 14. LG Run 080212 - RPC requests

Note

RPC requests is well below the MS recommendation of less than 20.

In this test, additional memory positively affects the mailbox server’s ability to handle RPC requests. At no time does RPC requests approach or exceed the Microsoft recommended threshold of 20 for any of the configured servers.

Database cache size

Figure 15 depicts the database cache size on each of the three Exchange 2007 CCR clusters configured for the LG Run 080212. The server memory configuration ranges from 16 GB to 8 GB

and is denoted on the chart.

27

Page 28: CCR Exchange 2007 Concept

Figure 15. LG Run 080212 – database cache size

In this test, Exchange server uses additional memory for the database cache. Exchange uses available memory for database cache if it is available and is needed.

The cache size used by Exchange for LG Run 080212 is as follows:

• MB2N1 — 16 GB RAM provides 3.25 MB cache per user

• MB3N1 — 12 GB RAM provides 2 MB cache per user

• MB4N1 — 8 GB RAM provides 1.25 MB cache per user

With 16 GB of RAM on MB2N1, Exchange is able to reduce cache over time as it no longer needs all of the cache it allocated. This indicates that sufficient memory is available for cache, given the

LoadGen heavy profile we are using.

Hub transport (HT) delivery queues

Figure 16 depicts the quantity of messages queued for delivery across the five hub transport (HT) servers configured for the LG Run 080212.

28

Page 29: CCR Exchange 2007 Concept

Figure 16. LG Run 080212 - hub transport messages queued for delivery

HT servers are working efficiently and are not queuing messages, resulting in a bottleneck. For the duration of the testing, there is an average of one message queued on each of the five hub

transport servers.

Test findings summary − LG Run 080212

LoadGen profile

• Outlook 2007 Online-Heavy per MS recommendation

Workload generated (average)

• 20 sent/48 received

• 73 KB average message size

IOPS generated

• 0.074 IOPS with 16 GB RAM

• 0.155 IOPS with 12 GB RAM

• 0.181 IOPS with 8 GB RAM

For LoadGen Run 080212, there are no significant bottlenecks, and the configuration performed

well. The effect of RAM is apparent in the IOPS generated during the LoadGen run. When using half of the amount of RAM that the Storage Planning Calculator recommends, the IOPS double.

LoadGen Run 080214

29

Page 30: CCR Exchange 2007 Concept

LoadGen in stress mode enables the generation of tasks as fast as the receiving Exchange server can accept them. This mode eliminates the wait time between tasks that occurs when running in

normal mode. LoadGen stress mode allows the identification of bottlenecks across multiple server and storage subsystems. The use of stress mode intentionally overloads the Exchange system; the

expected outcome is that the servers will not be able to handle the load generated.

LoadGen stress mode causes each LoadGen remote server to log on to each mailbox; this results in

each mailbox processing multiple, simultaneous client connections.

Effect of server memory on disk transfers per second

Figure 17 depicts the disk transfers per second on each of the three Exchange 2007 CCR clusters configured for the LG Run 080214.

The server memory configuration for the stress mode LG Run 080214 is as follows:

• MB2N1 − 8 GB RAM

• MB3N1 − 16 GB RAM

• MB4N1 − 12 GB RAM

Note

The server memory configuration is changed in earlier testing to ensure that the effect of memory on performance is consistent when the quantity of RAM is changed. For example, the performance on a server with 8 GB of RAM is consistent with the performance on another server when it is configured with 8 GB of RAM.

Figure 17. LG Run 080214 - disk transfers per second

30

Page 31: CCR Exchange 2007 Concept

Note

Client logons do not complete until approximately 1630 hours.

When LoadGen is configured to utilize stress mode, the following approximate per user IOPS are

reached:

• MB2N1 − 1.45 IOPS per user

• MB3N1 − 1.15 IOPS per user

• MB4N1 − 0.77 IOPS per user

These results indicate that LoadGen running in stress mode is able to generate a significant load on

the mailbox servers.

Effect of server memory on processor use

Figure 18 depicts the processor use on each of the three Exchange 2007 CCR clusters configured for the LG Run 080214.

Figure 18. LG Run 080214 - % processor time

Note

Client logons did not complete until approximately 1,630 hours.

31

Page 32: CCR Exchange 2007 Concept

Due to the significant load that LoadGen stress mode generates, % processor time is above the MS

recommendation of less than 90. This is a typical outcome of stress mode, where the tool will run

until all server resources are utilized.

Effect of server memory on RPC averaged latency

Figure 19 depicts the RPC averaged latency on each of the three Exchange 2007 CCR clusters configured for the LG Run 080214.

Figure 19. LG Run 080214 - RPC averaged latency

Note

Client logons do not complete until approximately 1,630 hours.

Due to the significant load that LoadGen stress mode generates, RPC averaged latency is well above

the MS recommendation of 50 ms. This is expected when using stress mode and indicates the

Outlook clients are experiencing delays when performing tasks against the Exchange server.

Effect of server memory on RPC requests

Figure 20 depicts the RPC requests outstanding on each of the three Exchange 2007 CCR clusters configured for the LG Run 080214.

32

Page 33: CCR Exchange 2007 Concept

Figure 20. LG Run 080214 - RPC requests

Note

Client logons do not complete until approximately 1630 hours.

Due to the significant load that LoadGen stress mode generates, RPC requests are well above the MS

recommendation of 20. This is expected when using stress mode and indicates the Outlook clients are experiencing delays when performing tasks against the Exchange server.

HT delivery queues

Figure 21 depicts the quantity of messages queued for delivery across the five HT servers configured

for the LG Run 080214.

33

Page 34: CCR Exchange 2007 Concept

Figure 21. LG Run 080214 - hub transport messages queued for delivery

Note

Client logons did not complete until approximately 1630 hours.

Due to the significant load that LoadGen stress mode generates, there are approximately 125,000

messages queued for delivery across the five HT servers at the completion of the test run. The

backlog of messages waiting on the HT server to be processed is a result of the bottlenecks identified

previously in areas such as processor use.

Test findings summary − LG Run 080214

LoadGen profile

• Outlook 2007 Online-Heavy

IOPS generated

• 0.772 IOPS with 16 GB RAM

• 1.158 IOPS with 12 GB RAM

• 1.448 IOPS with 8 GB RAM

For LoadGen Run 080214, there are bottlenecks across the Exchange configuration. Stress mode

is used to determine if this build of LoadGen is capable of generating a significant load on the

Exchange infrastructure.

34

Page 35: CCR Exchange 2007 Concept

Conclusion

The Exchange 2007 CCR POC configuration allows the validation of the server and storage

configuration for 28,000 mailboxes.

The proof of concept validated the following key points:

• 4,000 mailboxes can be hosted on each DL380 G5 mailbox server.

• 28,000 mailboxes can be hosted on a single EVA8100.

• Exchange 2007 SP1 CCR functionality works as expected for most common failure scenarios.

Functional testing identifies potential areas of concern listed below, along with areas where Exchange

2007 CCR could result in unexpected outages if monitoring is not configured and functional.

Performance testing with a workload generated by LoadGen shows that this configuration is sufficient to support 28,000 heavy users with 250-MB mailboxes with CCR enabled.

The use of Exchange 2007 CCR host-based replication can provide customers with a valuable

tool to enable the reduction of time needed for recovery of Exchange data. The use of Exchange

2007 CCR technology has the potential to favorably impact the recovery time objective (RTO) and

recovery point objective (RPO) by allowing up-to-date copies of Exchange data for recovery on

separate servers and storage.

The most significant finding from testing is the dismounting of databases upon loss of storage or connectivity on the active CCR node. While this behavior is expected, this is an issue since the

Exchange cluster resources, such as the System Attendant and Information Store, report they are up

and available while all of the databases are dismounted. This results in the loss of connectivity by

Outlook clients. This state requires the use of monitoring to ensure database availability, since the

cluster resources will not mount automatically in the event that one or all of the databases become

dismounted.

There are several additional areas of concern when using Exchange CCR that must be taken into

account before a change of this magnitude is implemented into a production environment:

• Additional training of support staff is required to ensure that operation of the new Exchange

CCR features is understood.

• Windows 2003/2008 majority node set clustering with FSW mechanism needs to be understood

by support staff, since it operates differently from a shared quorum cluster configuration.

• Database availability monitoring must be implemented to ensure that offline databases are

rapidly identified.

• Troubleshooting methodology changes due to new Windows clustering and Exchange CCR

features.

• Manual failover to the passive node may be required. There is no guarantee that databases will automatically failover and mount.

For more information on the expected behavior of CCR, see http://technet.microsoft.com/en-us/

library/aa995938(EXCHG.80).aspx.

• Backup and recovery methodology changes when using Exchange CCR, which results in

modification of the procedures detailing the backup and recovery of Exchange data.

35

Page 36: CCR Exchange 2007 Concept

• New recovery documentation development is required.

• Revision of the existing service level agreement may be required due to the different nature of Exchange 2007 CCR.

We value your feedback

In order to develop technical materials that address your information needs, we need your feedback. We appreciate your time and value your opinion. The following link will take you to a short survey

regarding the quality of this paper:

http://hpwebgen.com/Questions.aspx?id=12046&pass=41514

36

Page 37: CCR Exchange 2007 Concept

Appendix A Performance measurement

Performance counter objects The following list shows the general performance objects that are captured for LoadGen performance

runs by server type.

Domain controller/Global catalog

\LogicalDisk\*

\Memory\*

\Network Interface(*)\*

\NTDS\*

\Paging File(*)\*

\Process(*)\*

\Processor(*)\

\Server\*

Hub transport/Client access server

\MSExchange Transport Queues(*)\*

\MSExchange Transport Routing(*)\*

LoadGen master server

\Memory\*

\Network Interface(*)\*

\Paging File(*)\*

\Process(*)\*

\Processor(*)\

\Server\*

LoadGen remote servers

\Exchange Load Generator Engine(_total)\*

\Exchange Load Generator User Groups(_total)\*

\Memory\*

\Network Interface(*)\*

\Paging File(*)\*

\Process(*)\*

\Processor(*)\

\Server\*

Mailbox servers

37

Page 38: CCR Exchange 2007 Concept

\LogicalDisk(*)\*

\Memory\*

\MSExchange Database(*)\*

\MSExchangeIS(*)\*

\MSExchangeIS Client(*)\*

\MSExchangeIS Mailbox(*)\*

\Network Interface(*)\*

\Paging File(*)\*

\Process(*)\*

\Processor(*)\

\Server\*

EVA storage

\HP EVA Host Connection(*)\*

\HP EVA Host Port Statistics(*)\*

\HP EVA Physical Disk Group(*)\*

\HP EVA Storage Array(*)\*

\HP EVA Storage Controller(*)\*

\HP EVA Virtual Disk(*)\*

38

Page 39: CCR Exchange 2007 Concept

Appendix B Bill of materials

Servers Quantity Part number Description Comments

14 391835-B21 HP ProLiant DL380G5 Rack CTO Chassis Mailbox server

14 405160-B21 HP Smart Array P400/256 for DL380 G5

14 437940-L21 QC Intel Xeon X5345 (2.33 GHz, 80W, 1333 FSB)

28 397415-B21 8 GB FBD PC2-5300 2x4GB Kit

12 433559-B21 HP DL380G5 E5345 HPM FIO Perf Pack

56 431958-B21 HP 146 GB 3 G SAS 10K SFF HDD

28 431933-B21 HP 72 GB 3 G SAS 15 K SFF HDD

14 412648-B21 HP NC360T PCI Express Dual Port Gigabit Server Adapter

14 A8003A HP StorageWorks FC2242SR Dual Ch 4Gb PCI-e HBA

5 391835-B21 HP ProLiant DL380G5 Rack CTO Chassis HT/CAS server

5 405160-B21 HP Smart Array P400/256 for DL380 G 5

5 437940-L21 QC Intel Xeon X5345 (2.33 GHz, 80W, 1333 FSB)

5 397415-B21 8 GB FBD PC2-5300 2x4GB Kit

20 431958-B21 HP 146 GB 3G SAS 10 K SFF HDD

10 431933-B21 HP 72 GB 3 G SAS 15 K SFF HDD

5 331903-B21 Slimline CD-RW/DVD-ROM Combo Option Kit

3 364636-405 HP DL580G3 Red Mod-FX Rack Chassis Active Directory server

12 375369-L22 64-bit Intel Xeon 3.16-1M 580 G3 FIO

12 375004-B21 HP 4 GB PC2-3200 2 Rank DDR SDRAM Memory

3 286778-B22 HP 72 GB 15 K U320 15 K Pluggable Hard Drive

8 407424-001 HP DL385G2 2218 2 G LoadGen clients

8 407433-L21 AMD Opteron Processor 2218 (2.6 GHz, 95 Watts) FIO

8 408851-B21 2 GB PC2-5300 (2x1GB) Kit, single rank

16 431935-B21 HP 72 GB 3 G SAS 15K SFF SP HDD

39

Page 40: CCR Exchange 2007 Concept

EVA8100Quantity Part number Description Comments

4 AF004A HP Rack 10642 G2 w/Extn Shock (42U)

8 252663-D72 Modular PDU 24A HV

2 AG702A HP EVA8100 2C12D-A 60Hz 42U Cabinet

440 AG425B 300 GB 15K rpm dual-port 2/4 Gb/s FC-AL 1-inch (2.54

cm) drive

72 370790-B23 500 GB FATA disk dual-port 2 Gb FC Hybrid disk drive

factory integrated

16 221692-B22 5-meter LC-LC Multi-Mode Fibre Cable

16 A7446B 4 Gb/s SFP Fibre Channel Transceiver Kit

Infrastructure Quantity Part number Description Comments

4 J9050A ProCurve Switch 2900 48 G

2 J4858B ProCurve Gigabit-SX-LC Mini-GBIC

Miscellaneous Quantity Part number Description Comments

2 AF001A HP Universal Rack 10642 G2 Shock Rack

2 AG052A HP TFT7600 US Rckmnt Keybrd 17in Monitor

2 AF602A HP 4X 1X 16 IP Console USB/VM Switch

32 AF604A HP PS2 USB Vert Media Interface Adapter

40

Page 41: CCR Exchange 2007 Concept

Appendix C Exchange 2007 script samples

Script reference

The following sample scripts are broken into functional sections by the type of work being performed

and, where applicable, scripts are provided for the three types of LUN configuration used in this testing.

EVA configuration

EVA configuration scripts are generated using the HP Storage System Scripting Utility (SSSU) to

capture the active configuration on EVA01 after storage configuration is completed. The script is then modified to reference EVA02 and is processed to configure the second EVA identically to

the first and present the LUNs to the servers.

Mailbox server management

Once the disks are presented to the servers and verification that the correct configuration of drives is present, DiskPart.exe is used in conjunction with text files to select, align, and label partitions. After the partition creation process is completed, partitions are formatted and labeled, and folders are created for Exchange databases and log files.

DiskPart-MBX.txt sample script

This DiskPart input text file depends on the appropriate LUNs being presented in a consistent order. The alignment of disk partitions is an optional task, since the performance gain on an EVA 8100 is negligible.

REM HP CFT POC

REM Disk Partitioning

REM Version 1

REM

REM Invoke with: diskpart /s DiskPart-MBX.txt

REM

REM Set Focus then Perform Action

select disk 2

create partition primary align=64

assign letter=F

select disk 3

create partition primary align=64

assign letter=G

select disk 4

create partition primary align=64

assign letter=H

41

Page 42: CCR Exchange 2007 Concept

select disk 5

create partition primary align=64

assign letter=I

select disk 6

create partition primary align=64

assign letter=J

select disk 7

create partition primary align=64

assign letter=K

select disk 8

create partition primary align=64

assign letter=L

select disk 9

create partition primary align=64

assign letter=M

exit

Format-MBX-MB1N1 sample script

This Format script formats the aligned partitions using the NTFS file system, sets a volume name

(MB1N1_SG01-07_DB) and uses a 64 KB block allocation size. A block allocation size of 64 KB

is recommended for database partitions. A block allocation size of 8 KB (default) or 64 KB is suitable for log partitions.

REM Disk Formatting

REM Version 1

REM

format F: /fs:NTFS /v:MB1N1_SG01-07_DB /a:64K /q

format G: /fs:NTFS /v:MB1N1_SG01-07_Log /a:64K /q

format H: /fs:NTFS /v:MB1N1_SG08-14_DB /a:64K /q

format I: /fs:NTFS /v:MB1N1_SG08-14_Log /a:64K /q

format J: /fs:NTFS /v:MB1N1_SG15-21_DB /a:64K /q

format K: /fs:NTFS /v:MB1N1_SG15-21_Log /a:64K /q

format L: /fs:NTFS /v:MB1N1_SG22-27_DB /a:64K /q

format M: /fs:NTFS /v:MB1N1_SG22-27_Log /a:64K /q

MD-MBX.bat sample script

This folder creation script creates the folders used to organize the Exchange database and log file

structures.

42

Page 43: CCR Exchange 2007 Concept

REM HP CFT POC

REM Make Directory Script

REM Version 1

REM

MD F:\SG01_DB

MD F:\SG02_DB

MD F:\SG03_DB

MD F:\SG04_DB

MD F:\SG05_DB

MD F:\SG06_DB

MD F:\SG07_DB

MD G:\SG01_Log

MD G:\SG02_Log

MD G:\SG03_Log

MD G:\SG04_Log

MD G:\SG05_Log

MD G:\SG06_Log

MD G:\SG07_Log

MD H:\SG08_DB

MD H:\SG09_DB

MD H:\SG10_DB

MD H:\SG11_DB

MD H:\SG12_DB

MD H:\SG13_DB

MD H:\SG14_DB

MD I:\SG08_Log

MD I:\SG10_Log

MD I:\SG11_Log

MD I:\SG12_Log

MD I:\SG13_Log

MD I:\SG14_Log

MD J:\SG15_DB

MD J:\SG16_DB

43

Page 44: CCR Exchange 2007 Concept

MD J:\SG17_DB

MD J:\SG18_DB

MD J:\SG19_DB

MD J:\SG20_DB

MD J:\SG21_DB

MD K:\SG15_Log

MD K:\SG16_Log

MD K:\SG17_Log

MD K:\SG18_Log

MD K:\SG19_Log

MD K:\SG20_Log

MD I:\SG09_Log

MD K:\SG21_Log

MD L:\SG22_DB

MD L:\SG23_DB

MD L:\SG24_DB

MD L:\SG25_DB

MD L:\SG26_DB

MD L:\SG27_DB

MD M:\SG022_Log

MD M:\SG023_Log

MD M:\SG024_Log

MD M:\SG025_Log

MD M:\SG026_Log

MD M:\SG027_Log

Exchange provisioning for mailbox servers

Once the storage provisioning steps have been completed, the Exchange storage groups and

databases can be created. This section of scripts performs the tasks necessary for the creation, labeling, and configuration of Exchange objects for this testing.

SGProvMB1.ps1 sample script

This storage group provisioning script creates storage groups on an Exchange 2007 server after the

Exchange 2007 CCR nodes have been installed, licensed, and verified for health.

The first section creates the storage group, sets the log and system folder paths, and enables circular logging. Circular logging should only be used in non-production test environments and is set here to

44

Page 45: CCR Exchange 2007 Concept

allow the LoadGen initialization process to complete without filling log LUNs and dismounting the

Exchange databases.

The second section creates the Exchange database and sets the file path for each database.

The third section mounts the databases that are created. The identity used in the script to refer to

the database uses a unique reference, FYDIBOHF23SPDLT, which looks like a GUID but is actually

a transcription of EXCHANGE12ROCKS—this was chosen by the Exchange development team

when they needed to generate this unique value. This value is the same across all Exchange

implementations.

The script examples presented are the actual scripts used to perform Exchange manipulations. There

are many ways to create PowerShell functionality, and some of the functions in these scripts can be

performed in a single line. An example is presented below.

The Cmdlet used to mount each database individually that must be repeated 27 times with one

line per database is:

mount-database -Identity ’CN=MB1SG01DB01,CN=SG01,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

This entire series of 27 Cmdlets can be depicted in a single line as:

get-mailboxdatabase −server MB1CCR | mount-database

Note

Script lines have been wrapped for representation in this document.

#

=======================================================================

#

# Created with SAPIEN Technologies PrimalScript 2007

#

# NAME: MBX 01 SG/DB Provision Script

#

# COMMENT: MBX Server 01 - Storage Group and DB provisioning for theMailbox Server configuration utilizing drive letter configuration

# based on a weekly full and daily incremental backup rotation...Circular logging is enabled for each Storage Group.

#

#

=======================================================================

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG01’ -LogFolderPath ’G:\SG01_Log’ -SystemFolderPath ’G:\SG01_Log’

45

Page 46: CCR Exchange 2007 Concept

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG02’ -LogFolderPath ’G:\SG02_Log’ -SystemFolderPath ’G:\SG02_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG03’ -LogFolderPath ’G:\SG03_Log’ -SystemFolderPath ’G:\SG03_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG04’ -LogFolderPath ’G:\SG04_Log’ -SystemFolderPath ’G:\SG04_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG05’ -LogFolderPath ’G:\SG05_Log’ -SystemFolderPath ’G:\SG05_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG06’ -LogFolderPath ’G:\SG06_Log’ -SystemFolderPath ’G:\SG06_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG07’ -LogFolderPath ’G:\SG07_Log’ -SystemFolderPath ’G:\SG07_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG08’ -LogFolderPath ’I:\SG08_Log’ -SystemFolderPath ’I:\SG08_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG09’ -LogFolderPath ’I:\SG09_Log’ -SystemFolderPath ’I:\SG09_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG10’ -LogFolderPath ’I:\SG10_Log’ -SystemFolderPath ’I:\SG10_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG11’ -LogFolderPath ’I:\SG11_Log’ -SystemFolderPath ’I:\SG11_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG12’ -LogFolderPath ’I:\SG12_Log’ -SystemFolderPath ’I:\SG12_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG13’ -LogFolderPath ’I:\SG13_Log’ -SystemFolderPath ’I:\SG13_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG14’ -LogFolderPath ’I:\SG14_Log’ -SystemFolderPath ’I:\SG14_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG15’ -LogFolderPath ’K:\SG15_Log’ -SystemFolderPath ’K:\SG15_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG16’ -LogFolderPath ’K:\SG16_Log’ -SystemFolderPath ’K:\SG16_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG17’ -LogFolderPath ’K:\SG17_Log’ -SystemFolderPath ’K:\SG17_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG18’ -LogFolderPath ’K:\SG18_Log’ -SystemFolderPath ’K:\SG18_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG19’ -LogFolderPath ’K:\SG19_Log’ -SystemFolderPath ’K:\SG19_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG20’ -LogFolderPath ’K:\SG20_Log’ -SystemFolderPath ’K:\SG20_Log’

46

Page 47: CCR Exchange 2007 Concept

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG21’ -LogFolderPath ’K:\SG21_Log’ -SystemFolderPath ’K:\SG21_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG22’ -LogFolderPath ’M:\SG22_Log’ -SystemFolderPath ’M:\SG22_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG23’ -LogFolderPath ’M:\SG23_Log’ -SystemFolderPath ’M:\SG23_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG24’ -LogFolderPath ’M:\SG24_Log’ -SystemFolderPath ’M:\SG24_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG25’ -LogFolderPath ’M:\SG25_Log’ -SystemFolderPath ’M:\SG25_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG26’ -LogFolderPath ’M:\SG26_Log’ -SystemFolderPath ’M:\SG26_Log’

new-StorageGroup -Server ’MB1CCR’ -CircularLoggingEnabled:$true -Name’SG27’ -LogFolderPath ’M:\SG27_Log’ -SystemFolderPath ’M:\SG27_Log’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG01’ -Name ’MB1SG01DB01’-EdbFilePath ’F:\SG01_DB\MB1SG01DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG02’ -Name ’MB1SG02DB01’-EdbFilePath ’F:\SG02_DB\MB1SG02DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG03’ -Name ’MB1SG03DB01’-EdbFilePath ’F:\SG03_DB\MB1SG03DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG04’ -Name ’MB1SG04DB01’-EdbFilePath ’F:\SG04_DB\MB1SG04DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG05’ -Name ’MB1SG05DB01’-EdbFilePath ’F:\SG05_DB\MB1SG05DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG06’ -Name ’MB1SG06DB01’-EdbFilePath ’F:\SG06_DB\MB1SG06DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG07’ -Name ’MB1SG07DB01’-EdbFilePath ’F:\SG07_DB\MB1SG07DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG08’ -Name ’MB1SG08DB01’-EdbFilePath ’H:\SG08_DB\MB1SG08DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG09’ -Name ’MB1SG09DB01’-EdbFilePath ’H:\SG09_DB\MB1SG09DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG10’ -Name ’MB1SG10DB01’-EdbFilePath ’H:\SG10_DB\MB1SG10DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG11’ -Name ’MB1SG11DB01’-EdbFilePath ’H:\SG11_DB\MB1SG11DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG12’ -Name ’MB1SG12DB01’-EdbFilePath ’H:\SG12_DB\MB1SG12DB01.edb’

47

Page 48: CCR Exchange 2007 Concept

new-mailboxdatabase -StorageGroup ’MB1CCR\SG13’ -Name ’MB1SG13DB01’-EdbFilePath ’H:\SG13_DB\MB1SG13DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG14’ -Name ’MB1SG14DB01’-EdbFilePath ’H:\SG14_DB\MB1SG14DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG15’ -Name ’MB1SG15DB01’-EdbFilePath ’J:\SG15_DB\MB1SG15DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG16’ -Name ’MB1SG16DB01’-EdbFilePath ’J:\SG16_DB\MB1SG16DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG17’ -Name ’MB1SG17DB01’-EdbFilePath ’J:\SG17_DB\MB1SG17DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG18’ -Name ’MB1SG18DB01’-EdbFilePath ’J:\SG18_DB\MB1SG18DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG19’ -Name ’MB1SG19DB01’-EdbFilePath ’J:\SG19_DB\MB1SG19DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG20’ -Name ’MB1SG20DB01’-EdbFilePath ’J:\SG20_DB\MB1SG20DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG21’ -Name ’MB1SG21DB01’-EdbFilePath ’J:\SG21_DB\MB1SG21DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG22’ -Name ’MB1SG22DB01’-EdbFilePath ’L:\SG22_DB\MB1SG22DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG23’ -Name ’MB1SG23DB01’-EdbFilePath ’L:\SG23_DB\MB1SG23DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG24’ -Name ’MB1SG24DB01’-EdbFilePath ’L:\SG24_DB\MB1SG24DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG25’ -Name ’MB1SG25DB01’-EdbFilePath ’L:\SG25_DB\MB1SG25DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG26’ -Name ’MB1SG26DB01’-EdbFilePath ’L:\SG26_DB\MB1SG26DB01.edb’

new-mailboxdatabase -StorageGroup ’MB1CCR\SG27’ -Name ’MB1SG27DB01’-EdbFilePath ’L:\SG27_DB\MB1SG27DB01.edb’

mount-database -Identity ’CN=MB1SG01DB01,CN=SG01,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG02DB01,CN=SG02,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG03DB01,CN=SG03,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group

48

Page 49: CCR Exchange 2007 Concept

(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG04DB01,CN=SG04,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG05DB01,CN=SG05,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG06DB01,CN=SG06,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG07DB01,CN=SG07,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG08DB01,CN=SG08,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG09DB01,CN=SG09,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG10DB01,CN=SG10,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG11DB01,CN=SG11,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG12DB01,CN=SG12,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG13DB01,CN=SG13,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

49

Page 50: CCR Exchange 2007 Concept

mount-database -Identity ’CN=MB1SG14DB01,CN=SG14,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG15DB01,CN=SG15,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG16DB01,CN=SG16,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG17DB01,CN=SG17,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG18DB01,CN=SG18,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG19DB01,CN=SG19,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG20DB01,CN=SG20,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG21DB01,CN=SG21,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG22DB01,CN=SG22,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG23DB01,CN=SG23,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG24DB01,CN=SG24,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group

50

Page 51: CCR Exchange 2007 Concept

(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG25DB01,CN=SG25,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG26DB01,CN=SG26,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

mount-database -Identity ’CN=MB1SG27DB01,CN=SG27,CN=Informa-tionStore,CN=MB1CCR,CN=Servers,CN=Exchange Administrative Group(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=CFTOrg,CN=MicrosoftExchange,CN=Services,CN=Configuration,DC=cft,DC=lab’

MB1DisableCircularLogging.ps1 sample script

This script toggles the value to disable circular logging for all storage groups on a particular server and restarts the MSExcahngeIS service to enable the new setting.

#

=======================================================================

#

# Created with SAPIEN Technologies PrimalScript 2007

#

# NAME: MB1_DisableCircularLogging.ps1

#

# COMMENT: Script to disable circular logging

# COMMENT: Run from Active Node!

#

=======================================================================

$mbsg = get-storagegroup -server MB1CCR| select-object name

$val = 0

while ($val -ne $mbsg.count)

{

set-storagegroup $mbsg[$val].name -CircularLoggingEnabled:$False

$val++

}

Restart-Service MSExchangeIS

MB1EnableCircularLogging.ps1 sample script

51

Page 52: CCR Exchange 2007 Concept

This script toggles the value to enable circular logging for all storage groups on a particular server and restarts the MSExcahngeIS service to enable the new setting. This script must be run from

the ACTIVE CCR node.

#

=======================================================================

#

# Created with SAPIEN Technologies PrimalScript 2007

#

# NAME: MB1_EnableCircularLogging.ps1

#

# COMMENT: Script to enable circular logging

# COMMENT: Run from Active Node!

#

=======================================================================

$mbsg = get-storagegroup -server MB1CCR| select-object name

$val = 0

while ($val -ne $mbsg.count)

{

set-storagegroup $mbsg[$val].name -CircularLoggingEnabled:$True

$val++

}

Restart-Service MSExchangeIS

MB1_Dismount-Database_ALL.ps1 sample script

This script dismounts all databases on a particular server.

#

=======================================================================

#

# Created with SAPIEN Technologies PrimalScript 2007

#

# NAME: MB1_Dismount-Database_ALL.ps1

#

# COMMENT: Dismount all Databases 01-27

#

#

=======================================================================

52

Page 53: CCR Exchange 2007 Concept

Dismount-Database -Identity ’MB1CCR\MB1SG01DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG02DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG03DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG04DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG05DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG06DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG07DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG08DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG09DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG10DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG11DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG12DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG13DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG14DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG15DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG16DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG17DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG18DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG19DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG20DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG21DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG22DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG23DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG24DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG25DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG26DB01’ -confirm:$false

Dismount-Database -Identity ’MB1CCR\MB1SG27DB01’ -confirm:$false

MB1_Mount-Database_ALL.ps1 sample script

This script mounts all databases on a particular server.

#

=======================================================================

#

# Created with SAPIEN Technologies PrimalScript 2007

#

53

Page 54: CCR Exchange 2007 Concept

# NAME: MB1_Mount-Database_ALL.ps1

#

# COMMENT: Mount all Databases 01-27

#

#

=======================================================================

Mount-Database -Identity ’MB1CCR\MB1SG01DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG02DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG03DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG04DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG05DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG06DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG07DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG08DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG09DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG10DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG11DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG12DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG13DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG14DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG15DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG16DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG17DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG18DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG19DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG20DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG21DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG22DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG23DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG24DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG25DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG26DB01’ -confirm:$false

Mount-Database -Identity ’MB1CCR\MB1SG27DB01’ -confirm:$false

MB1_Suspend-StorageGroupCopy_All_SG.ps1 sample script

54

Page 55: CCR Exchange 2007 Concept

This script suspends CCR replication for each storage group in preparation for a manual reseed

procedure.

#

=======================================================================

#

# Created with SAPIEN Technologies PrimalScript 2007

#

# NAME: MB1_Suspend-StorageGroupCopy_ALL_SG.ps1

#

# COMMENT:

#

#

=======================================================================

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG01’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG02’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG03’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG04’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG05’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG06’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG07’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG08’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG09’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG10’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG11’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG12’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG13’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG14’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG15’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG16’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG17’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG18’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG19’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG20’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG21’ -Confirm:$false

55

Page 56: CCR Exchange 2007 Concept

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG22’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG23’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG24’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG25’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG26’ -Confirm:$false

Suspend-StorageGroupCopy -Identity ’MB1CCR\SG27’ -Confirm:$false

MB1_Update-StorageGroupCopy_All_SG.ps1 sample script

This script performs a manual reseed procedure after deleting any existing files and restarts the

storage group copy process. This script must be run from the PASSIVE CCR node.

#

=======================================================================

#

# Created with SAPIEN Technologies PrimalScript 2007

#

# NAME: MB1_Update-StorageGroupCopy_ALL_SG.ps1

#

# COMMENT: Run from PASSIVE node

#

#

=======================================================================

Update-StorageGroupCopy -Identity ’MB1CCR\SG01’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG02’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG03’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG04’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG05’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG06’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG07’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG08’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

56

Page 57: CCR Exchange 2007 Concept

Update-StorageGroupCopy -Identity ’MB1CCR\SG09’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG10’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG11’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG12’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG13’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG14’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG15’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG16’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG17’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG18’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG19’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG20’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG21’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG22’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG23’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG24’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG25’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG26’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

Update-StorageGroupCopy -Identity ’MB1CCR\SG27’ -Confirm:$false-DeleteExistingFiles:$True -Force:$True

MB1_Resume-StorageGroupCopy_All_SG.ps1 sample script

57

Page 58: CCR Exchange 2007 Concept

This script enables CCR replication for each storage group.

# =====================================================================

#

# Created with SAPIEN Technologies PrimalScript 2007

#

# NAME: MB1_Resume-StorageGroupCopy_ALL_SG.ps1

#

# COMMENT:

#

# =====================================================================

Resume-StorageGroupCopy -Identity ’MB1CCR\SG01’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG02’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG03’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG04’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG05’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG06’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG07’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG08’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG09’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG10’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG11’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG12’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG13’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG14’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG15’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG16’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG17’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG18’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG19’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG20’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG21’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG22’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG23’ -Confirm:$false

58

Page 59: CCR Exchange 2007 Concept

Resume-StorageGroupCopy -Identity ’MB1CCR\SG24’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG25’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG26’ -Confirm:$false

Resume-StorageGroupCopy -Identity ’MB1CCR\SG27’ -Confirm:$false

MB1_Resume-StorageGroupCopy_All_SG.ps1 sample script

This script is used to manually copy the active Exchange databases as an option to reseeding the

passive node databases. It requires that replication be suspended, the databases be dismounted, and that the target directories are empty.

REM @echo off

REM

=====================================================================

REM

REM Batch File -- Created with SAPIEN Technologies PrimalScript 2007

REM

REM NAME: mb1_DB_Copy.bat

REM

REM COMMENT: RUN this from NODE 2 (Passive) ONLY!

REM

REM Comment2: Suspend all SG Copy, Dismount all DB on Server, Clean all

REM target directories

REM

REM======================================================================

copy \\mb1n1\f$\SG01_DB\mb1SG01DB01.edb f:\SG01_DB\mb1SG01DB01.edb

copy \\mb1n1\f$\SG02_DB\mb1SG02DB01.edb f:\SG02_DB\mb1SG02DB01.edb

copy \\mb1n1\f$\SG03_DB\mb1SG03DB01.edb f:\SG03_DB\mb1SG03DB01.edb

copy \\mb1n1\f$\SG04_DB\mb1SG04DB01.edb f:\SG04_DB\mb1SG04DB01.edb

copy \\mb1n1\f$\SG05_DB\mb1SG05DB01.edb f:\SG05_DB\mb1SG05DB01.edb

copy \\mb1n1\f$\SG06_DB\mb1SG06DB01.edb f:\SG06_DB\mb1SG06DB01.edb

copy \\mb1n1\f$\SG07_DB\mb1SG07DB01.edb f:\SG07_DB\mb1SG07DB01.edb

copy \\mb1n1\h$\SG08_DB\mb1SG08DB01.edb h:\SG08_DB\mb1SG08DB01.edb

copy \\mb1n1\h$\SG09_DB\mb1SG09DB01.edb h:\SG09_DB\mb1SG09DB01.edb

copy \\mb1n1\h$\SG10_DB\mb1SG10DB01.edb h:\SG10_DB\mb1SG10DB01.edb

copy \\mb1n1\h$\SG11_DB\mb1SG11DB01.edb h:\SG11_DB\mb1SG11DB01.edb

copy \\mb1n1\h$\SG12_DB\mb1SG12DB01.edb h:\SG12_DB\mb1SG12DB01.edb

59

Page 60: CCR Exchange 2007 Concept

copy \\mb1n1\h$\SG13_DB\mb1SG13DB01.edb h:\SG13_DB\mb1SG13DB01.edb

copy \\mb1n1\h$\SG14_DB\mb1SG14DB01.edb h:\SG14_DB\mb1SG14DB01.edb

copy \\mb1n1\j$\SG15_DB\mb1SG15DB01.edb j:\SG15_DB\mb1SG15DB01.edb

copy \\mb1n1\j$\SG16_DB\mb1SG16DB01.edb j:\SG16_DB\mb1SG16DB01.edb

copy \\mb1n1\j$\SG17_DB\mb1SG17DB01.edb j:\SG17_DB\mb1SG17DB01.edb

copy \\mb1n1\j$\SG18_DB\mb1SG18DB01.edb j:\SG18_DB\mb1SG18DB01.edb

copy \\mb1n1\j$\SG19_DB\mb1SG19DB01.edb j:\SG19_DB\mb1SG19DB01.edb

copy \\mb1n1\j$\SG20_DB\mb1SG20DB01.edb j:\SG20_DB\mb1SG20DB01.edb

copy \\mb1n1\j$\SG21_DB\mb1SG21DB01.edb j:\SG21_DB\mb1SG21DB01.edb

copy \\mb1n1\l$\SG22_DB\mb1SG22DB01.edb l:\SG22_DB\mb1SG22DB01.edb

copy \\mb1n1\l$\SG23_DB\mb1SG23DB01.edb l:\SG23_DB\mb1SG23DB01.edb

copy \\mb1n1\l$\SG24_DB\mb1SG24DB01.edb l:\SG24_DB\mb1SG24DB01.edb

copy \\mb1n1\l$\SG25_DB\mb1SG25DB01.edb l:\SG25_DB\mb1SG25DB01.edb

copy \\mb1n1\l$\SG26_DB\mb1SG26DB01.edb l:\SG26_DB\mb1SG26DB01.edb

copy \\mb1n1\l$\SG27_DB\mb1SG27DB01.edb l:\SG27_DB\mb1SG27DB01.edb

MB1_SetMaintenanceSchedule.ps1 sample script

This script enumerates all databases on a particular server and sets the online maintenance schedule.

# ======================================================================

#

# Microsoft PowerShell Source File -- Created with SAPIEN Technologies

PrimalScript 2007

#

# NAME: MB1_SetMaintenanceSchedule.ps1

#

# COMMENT: Sets the Maintenance Schedule for all databases on a mailbox

server

#

# ======================================================================

$mbdb = get-mailboxdatabase -server MB1CCR| select-object name

$val = 0

while ($val -ne $mbdb.count)

{

set-mailboxdatabase $mbdb[$val].name -MaintenanceSchedule"1.23:30-2.03:30,2.23:30-3.03:30,3.23:30-4.03:30,4.23:30-5.03:30"

60

Page 61: CCR Exchange 2007 Concept

$val++

}

Exchange Advanced Counters PowerShell Cmdlet

To create the Show Advanced Counters Item using a PowerShell Cmdlet:

New-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Services\ESE\Per-formance -Name "Show Advanced Counters" -PropertyType DWord -Value ’1’

1. Open Exchange Management Shell.

2. Paste the above command.

3. Press Enter.

Confirm that the Show Advanced Counters Item has been created in the appropriate location by

using RegEdit to view the object using PowerShell:

Get-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Services\ESE\Per-formance -Name "Show Advanced Counters"

61

Page 62: CCR Exchange 2007 Concept

Appendix D Server build checklist

Server build consistency

The following items are completed on servers to ensure that all servers are consistently configured

and will be stable for the duration of the testing:

• Windows 2003 Enterprise Edition installed

• HP ProLiant Support Pack (PSP) installed

• Drivers updated if newer than PSP

• Data Execution Prevention - Set to Windows Programs only

• PowerShell installed

• IIS installed

• KB942027 - .NET 2.0 Memory Fix

• HBAnywhere installed

• Windows 2003 MPIO DSM for EVA 8x00 Series installed

• Fibre Channel cabling consistent

• iLo named

• iLo Password set

• iLo Advanced Pack License applied

• BGInfo and Customize Desktop installed

• Windows Explorer customized

• Internet Explorer Proxy configured

• Microsoft Update configured

• Screen resolution set to 1024 x 768

• CD-ROM drive letter set to Z:

• Internet Explorer Enhanced Security Configuration disabled

• Windows 2003 Service Pack 2 applied

• Post Windows 2003 SP2 updates applied

• Post Windows 2003 SP2 Update #2 applied

• Local administrator account configured

• Network configuration performed

• Remote desktop protocol enabled

• Exchange 2007 SP1 installed

• Exchange 2007 SP1 roles configured

• Exchange 2007 SP1 licensed

62

Page 63: CCR Exchange 2007 Concept

• Application event log set to 40 MB in size

• PowerShell event log set to allow overwrite

• Windows 2003 SP2 scalable networking pack TCP offload disabled

• Hub transport server — Move transport queues

63

Page 64: CCR Exchange 2007 Concept

Appendix E EVA disk position

Physical EVA configuration

The following physical disk configuration is used for the proof of concept on all EVA8100s.

64

Page 65: CCR Exchange 2007 Concept

For more information

• HP Customer Focused Testing

http://www.hp.com/go/hpcft

• High availability for Microsoft Exchange Server 2007 SP1 using CCR with HP StorageWorks EVA8100 (1-GB Mailbox)

http://h71028.www7.hp.com/ERC/downloads/4AA1-5675ENW.pdf

• Best practices for HP servers and HP Enterprise Virtual Array 8100 in a Microsoft Exchange

Server 2007 environment of 20,000 users

http://h71028.www7.hp.com/ERC/downloads/4AA1-5666ENW.pdf

• Exchange 2007 Mailbox Server Role Storage Requirements Calculator

http://msexchangeteam.com/archive/2007/01/15/432207.aspx

• Exchange Server 2007 Deployment Checklists

http://technet.microsoft.com/en-us/library/bb887628.aspx

• Tools for Exchange Server 2007: LoadGen, Profile Analyzer

http://technet.microsoft.com/en-us/exchange/bb330849.aspx

• How to Change the Location of the (Hub Transport) Queue Database

http://technet.microsoft.com/en-us/library/bb125177.aspx

• Exchange 2007 − Continuous Replication Architecture and Behavior

http://blogs.technet.com/scottschnoll/archive/2006/10/06/Exchange-2007-_2D00_­Continuous-Replication-Architecture-and-Behavior.aspx

© 2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. 4AA1-9891ENW, June 2008

65