EMC Backup and Recovery for Microsoft Exchange … 5: Testing and Validation ... Manager, and...

EMC Backup and Recovery for Microsoft Exchange 2007

Enabled by EMC CLARiiON CX4-120,

Replication Manager, and Hyper-V on Windows Server 2008 using iSCSI

Proven Solution Guide

Copyright © 2009 EMC Corporation. All rights reserved. Published September, 2009 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. Benchmark results are highly dependent upon workload, specific application requirements, and system design and implementation. Relative system performance will vary as a result of these and other factors. Therefore, this workload should not be used as a substitute for a specific customer application benchmark when critical capacity planning and/or product evaluation decisions are contemplated. All performance data contained in this report was obtained in a rigorously controlled environment. Results obtained in other operating environments may vary significantly. EMC Corporation does not warrant or represent that a user can or will achieve similar performance expressed in transactions per minute. No warranty of system performance or price/performance is expressed or implied in this document. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners. Microsoft may have substituted components of the original environment in this document with hardware of a similar (or higher) specification to the original equipment used in the EMC Proven Solution. The content contained in this document originated from a validated EMC Proven Solution. The modification introduced by Microsoft may have caused changes in performance, functionality, or scalability of the original solution. Please refer to Hhttp://www.EMC.com/solutionsH for further information on validated EMC Proven Solutions. Part number: H6351

Table of Contents

Table of Contents

Chapter 1: About This Document .............................................................................................................. 4

Overview ........................................................................................................................................... 4 Audience and purpose ...................................................................................................................... 5 Scope ................................................................................................................................................ 5 Business challenge ........................................................................................................................... 6 Technology solution .......................................................................................................................... 6 Objectives .......................................................................................................................................... 6 Reference Architecture ..................................................................................................................... 7 Validated environment profile ............................................................................................................ 8 Hardware and software resources .................................................................................................. 10 Prerequisites and supporting documentation .................................................................................. 12

Chapter 2: Storage Design Layout .......................................................................................................... 13 Overview ......................................................................................................................................... 13 Storage design layout ..................................................................................................................... 14 RAID group layout ........................................................................................................................... 14 Best practices and recommendations ............................................................................................. 15

Chapter 3: Server and Network Design .................................................................................................. 16 Overview ......................................................................................................................................... 16 Server design .................................................................................................................................. 17 Network design................................................................................................................................ 19 Best practices for virtual machines ................................................................................................. 19 Best practices for iSCSI .................................................................................................................. 20

Chapter 4: Installation and Configuration ................................................................................................ 21 Overview ......................................................................................................................................... 21 Navisphere CLI scripts configuration .............................................................................................. 22 Disk management scripts ................................................................................................................ 23

Chapter 5: Testing and Validation ........................................................................................................... 25 Overview ......................................................................................................................................... 25 Microsoft Exchange performance ................................................................................................... 26 Tested components ......................................................................................................................... 42 Test results summary ...................................................................................................................... 43

Chapter 6: Conclusion ............................................................................................................................. 49 Overview ......................................................................................................................................... 49

Supporting Information ............................................................................................................................ 51 Overview ......................................................................................................................................... 51 Navisphere CLI scripts configuration .............................................................................................. 51

EMC Backup and Recovery for Microsoft Exchange 2007 Enabled by EMC CLARiiON CX4-120, Replication Manager, and Hyper-V on Windows Server 2008 using iSCSI Proven Solution Guide

3

Chapter 1: About This Document


Overview

Introduction This Proven Solution Guide summarizes observations of best practices that were discovered, validated, or otherwise encountered while validating the functionality of Microsoft Exchange 2007 enabled by EMC® CLARiiON® CX4-120, EMC Replication Manager, and Hyper-V on Microsoft Windows Server 2008 using the Microsoft iSCSI Software Initiator. EMC Replication Manager uses Microsoft Volume Shadow Copy Service (VSS) to perform online replication of Exchange Server 2007 storage groups. EMC's commitment to consistently maintain and improve quality is led by the Total Customer Experience (TCE) program, which is driven by Six Sigma methodologies. As a result, EMC has built Customer Integration Labs in its Global Solutions Centers to reflect real-world deployments in which TCE use cases are developed and executed. These use cases provide EMC with an insight into the challenges currently facing its customers. This document provides the specifications for the customer environment (that is, the storage configurations, design, sizing, and backup considerations) that constitute the requirements for this use case. This document outlines the detailed components that make up the environment and their relationship to each other. The use case test scenarios are listed, together with the objectives for completing them and the expected results.

Use Case definition

A use case reflects a defined set of tests that validates the reference architecture for a customer environment. This validated architecture can then be used as a reference point for a Proven Solution.

Contents The content of this chapter includes the following topics.

Topic See Page

Audience and purpose 5

Scope 5

Business challenge 6

Technology solution 6

Objectives 6

Reference Architecture 7

Validated environment profile 8

Hardware and software resources 10

Prerequisites and supporting documentation 12


4


Audience and purpose

Audience The intended audience for this Proven Solution Guide is:

• Internal EMC personnel • EMC partners • Customers

Purpose The purpose of this use case is to provide a consolidated virtualized out-of-the-box

solution for Microsoft Exchange Server 2007. The solution includes all the hardware and software components required to run this environment, including Active Directory and the required Exchange Server roles. Backup and Recovery replication and disaster recovery are applicable use cases for this solution using EMC's Replication Manager. Information in this document can be used as the basis for a solution build, white paper, best practices document, or training. It can also be used by other EMC organizations (for example, the technical services or sales organization) as the basis for producing documentation for a technical services or sales kit.

Scope

Scope of this document

This document describes the architecture of an EMC solution built at EMC’s Global Solutions labs. The scope of this solution includes the following: • Design of the CX4-120 storage array to support the tested building blocks • Design of the CX4-120 storage array to support Replication Manager clones for

Exchange databases and logs on a 2-day rotation cycle. • Storage loading simulated using Microsoft Load Generator (LoadGen) • EMC Replication Manager performance testing and analysis

Not in scope Implementation instructions and sizing guidelines are beyond the scope of this

document. Information on how to install and configure Microsoft Exchange Server 2007 and the required EMC products is out of scope for this document. However, links are provided on where to find all required software for this solution.


5


Business challenge

Overview The business challenge is to provide customers with the ability to use Microsoft

Exchange Server 2007 SP1, with local data replication, to allow for fast data recovery in the event of database loss or corruption. The storage architecture for this solution is based on a design that utilizes a “building block” approach, which repeatedly builds upon itself as customers’ requirements grow and additional space and fault tolerance are required. This solution uses a building block designed for 600 users. The challenge was to ensure that, at the smallest building block level, all components worked as expected and within Microsoft Exchange database latencies at all times, while running local data replication.

Technology solution

Overview A consolidated Microsoft Exchange infrastructure can be the first step towards

meeting the challenges of managing e-mail. This solution demonstrates the testing completed in a Microsoft Exchange environment. The solution described in this reference architecture utilizes EMC’s CLARiiON CX4-120 using the Microsoft iSCSI Software Initiator, which is a simple, easy-to-manage storage system.

Objectives

Overview The following are the objectives of this solution.

Objective Details

LoadGen validation Testing and validating 2,000 users at .48 IOPS

Replication Manager validation Validating the creation of Replication Manager replicas


6


Reference Architecture

Corresponding Reference Architecture

This use case has a corresponding Reference Architecture document that is available on Powerlink® and EMC.com. Refer to EMC Backup and Recovery for Microsoft Exchange 2007 enabled by EMC CLARiiON CX4-120, Replication Manager, and Hyper-V on Windows Server 2008 using iSCSI Reference Architecture for details. If you do not have access to this content, contact your EMC representative.

Reference Architecture diagram

The following diagram depicts the overall physical architecture of the use case. Note: A physical domain controller is recommended for site resilience. This is to ensure that the Active Directory remains intact in the unlikely event of the virtual Active Directory servers losing connectivity with the array.

Production Ethernet

iSCSI Channel Path 0

iSCSI Channel Path 1

Storage Processor Management

Replication ManagerServer/Mount Host

Virtual AD Server

Virtual Exchange Server(s)

EMC CLARiiON CX4-120

CL4332

MBX1

Hyper-V server Hyper-V server

Hub/CAS

Virtual AD Server

System CenterVirtual Machine Manager

EMC Replication Manager

Physical AD Server

Production

EMC Replication Manager

Physical Active Directory (AD)Server


7


Validated environment profile

Profile characteristics

This configuration is based on previous testing that was run on Exchange 2007 SP1 and 300 GB 15k FC drives. This configuration was tested with virtualization with no errors encountered. More information on this testing can be found on EMC.com and the Microsoft website under the Exchange Solutions Review Program (ESRP). For more information, see ESRP Storage Program - EMC CLARiiON CX3-20c (600 User) iSCSI Storage Solution for Microsoft Exchange Server 2007. The solution was validated with the following environment profile.

Profile characteristic Value

Number of Exchange 2007 users 600

Exchange 2007 SP1 servers 1

Number of Exchange 2007 users per server 600

Number of Exchange 2007 storage groups per server 4

Number of Exchange 2007 mail databases per storage group 1

Number of Exchange 2007 users per mail database 150

Size of Exchange 2007 user mailbox 300

Exchange 2007 production data

Type Value RAID type 1_0 Drive size 300 GB Speed 15k Connection FC


8


Hardware layout diagram

The following diagram describes the hardware layout used in this solution.

iSCSI SubNet 1 SPa

iSCSI SubNet 2 SPaiSCSI SubNet 2 SPb

Array ManagementProduction Network

EMC CLARiiON CX4-120 UltraScale

Windows 2008 Hyper-V

D O N OT

R E M OV E

D O N O T

R E M O V E

D O N O T

R E M O V E

D O N O T

R E M O V E

046-002-000

E X P P R I

EXP PRI

0 1 2 3

4 5 6 7

0 1 2 3

4 5 6 7

2 MI

N

No

Serv

iceab

le Pa

rts W

ithin

Ne

conti

ent p

as de

piec

es re

para

bles

No

cont

iene p

ieza

s rep

arabl

es

Ent

halt k

eine

repa

rierb

aren

Teile

Non

con

tlene

part

i ripa

rabili

046-002-597_A 02

EXPPRI

E X PP R I

0123

4567

0123

4567

2 MIN

No S

ervic

eabl

e Par

ts W

ithin

Ne c

ontie

nt pa

s de

piec

es rep

arab

les

No c

ontie

ne p

iezas

repa

rable

sE

nthal

t kein

e rep

arier

bare

n Teil

eN

on co

ntlen

e pa

rti rip

arab

ili

046-002-597_A02

B

A

1 Gigabit Ethernet Switch

1 Gigabit Ethernet Switch

System Center Virtual Machine Manager

Physical Active Directory Server

Physical Mount Host Server

300GB300GB 300GB300GB 300GB300GB 300GB300GB 300GB300GB 300GB300GB

300GB

300GB

300GB

300GB

RM RAID Group

1TB1TB

300GB300GB 300GB300GB

Log File RAID Group

DB File RAID Group

Hotspare

Unused

DAE 0_0

iSCSI SubNet 1 SPb


9


Hardware and software resources

Hardware The hardware used to validate the solution is listed below. Equipment Quantity Configuration

Rack 1 Dell 42 U rack

EMC CLARiiON CX4-120 1 2 service processors 2.879 GB mirrored cache DAE0: 15 15k 300 GB FC HDD FLARE® 6.28.0 (4.30)

Windows 2008 Hyper-V Server

2 1: 1 Gb/s NIC production 4: 1 Gb/s NIC iSCSI 1: Microsoft virtual network switch adapter 64 GB RAM 4: Intel64 Family 15 Model 6 Stepping 8 GenuineIntel ~2992 MHz processors Microsoft Windows Server 2008 Enterprise Edition Microsoft iSCSI Software Initiator OS Version: 6.0.6001 Service Pack 1 Build 6001

Windows 2008 System Center Virtual Machine Manager Server

1 1: 1 Gb/s NIC production 64 GB RAM 4: Intel64 Family 15 Model 6 Stepping 8 GenuineIntel ~2992 MHz processors Microsoft Windows Server 2008 Enterprise Edition OS Version: 6.0.6001 Service Pack 1 Build 6001

PowerEdge 1950 1 1: 1 Gb/s NIC production 8 GB RAM 2: Intel64 Family 15 Model 4 Stepping 8 GenuineIntel ~2793 MHz processors Microsoft Windows Server 2008 Enterprise Edition OS Version: 6.0.6001 Service Pack 1 Build 6001

PowerEdge 2950 1 1: 1 Gb/s NIC production 8 GB RAM 2: Intel64 Family 15 Model 4 Stepping 8 GenuineIntel ~2793 MHz processors Microsoft Windows Server 2008 Enterprise Edition OS Version: 6.0.6001 Service Pack 1 Build 6001

Dell PowerConnect 5324 2 24 Port 1 Gigabit Ethernet Layer 3 switch with 4 combo ports


10


Software The software used to validate the solution is listed below. Software Version

Microsoft Windows Server 2008 Enterprise x64 8

Microsoft Windows Server 2003 Enterprise x32 (to support Replication Manager)

1

Windows Server 2008 Hyper-V 2

Microsoft Exchange Server 2007 2

EMC PowerPath® 3

Microsoft iSCSI Software Initiator 3

EMC Replication Manager 2

EMC Solutions Enabler 2

Navisphere® admsnap 2

Navisphere CLI 2

Microsoft System Center Virtual Machine Manager 1

Microsoft LoadGen 2


11


Prerequisites and supporting documentation

Technology It is assumed the reader has a general knowledge of the following products:

• EMC CLARiiON storage arrays • EMC Replication Manager • EMC Navisphere Manager • Microsoft Exchange Server 2007 • Microsoft LoadGen • Hyper-V on Windows Server 2008

Supporting documents

The documents listed below are EMC documents published on Powerlink. Access to these documents is based on your login credentials. If you do not have access to the content listed below, contact your EMC representative. • Replication Manager Product Guide Version 5.2.1 • EMC Solutions for Microsoft Exchange Server 2007 CLARiiON CX3 Series iSCSI -

Best Practices Planning • ESRP Storage Program - EMC CLARiiON CX3-20c (600 User) iSCSI Storage

Solution for Microsoft Exchange Server 2007 • EMC Solutions for Microsoft Exchange 2007 Virtual Exchange 2007 Using

Replication Manager Clones - Reference Architecture • EMC Solutions for Microsoft Exchange 2007 Virtual Exchange 2007 Using RM

Clones with Ontrack PowerControls for Email Recovery - Reference Architecture • EMC Backup and Recovery for Microsoft Exchange 2007 SP1 enabled by EMC

CLARiiON CX4-120, Replication Manager, and Hyper-V on Windows Server 2008 using ISCSI - Reference Architecture

• EMC Solutions for Microsoft Exchange 2007 Replication Manager Setup - Build Document

• EMC Solutions for Microsoft Exchange 2007 Standard Setup of an Exchange 2007 Mailbox Role - Build Document

• EMC Solutions for Microsoft Exchange 2007 Standard Setup of an Exchange 2007 HUB/CAS Role - Build Document

Third-party documents

The following documents published on the Microsoft website provide additional, relevant information on the tools used to validate and simulate Microsoft Exchange Server loads. • Exchange Server 2007 Load Generator • Installing Microsoft Exchange Server 2007


12

http://www.microsoft.com/downloads/details.aspx?FamilyId=0FDB6F14-1E42-4165-BB17-96C83916C3EC&displaylang=en

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

Chapter 2: Storage Design Layout


Overview

Introduction The purpose of this use case is to build a Microsoft Exchange 2007 SP1 with Hyper-

V on Windows Server 2008 environment on the CLARiiON CX4-120 platform and integrate it with Replication Manager 5.2.1. This use case is not intended to be a comprehensive guide to every aspect of an Exchange 2007 SP1 with Hyper-V on Windows Server 2008 solution. The storage design layout presented in this chapter applies to the specific components used during the development of this solution. The scope is roughly bound by the following parameters and assumptions. This is a representative of Replication Manager 5.2.1 integration with Microsoft Exchange 2007 SP1 and Hyper-V on Windows Server 2008 implementation using the Microsoft iSCSI Software Initiator. Note, however, that actual implementations will vary from the parameters shown, based on testing results.

Contents This chapter contains the following topics:

Topic See Page

Storage design layout 14

RAID group layout 14

Best practices and recommendations 15


13


Storage design layout

Introduction The following sections detail the layout principles associated with this solution.

Goals The following describes some of the key objectives when designing a configuration

for the CLARiiON CX4-120 storage layout: • The performance requirements must accommodate the required I/O based on the

user profile. • The design should be easy to understand and build upon (using a building block

approach). • The design should help to minimize the time and complexity of designing the

storage layout.

Determining building block requirements

A building block approach was used to determine the number of physical spindles required for this solution. This was a commercial-level building block approach, based on the Microsoft Exchange Solution Reviewed Program (ESRP) testing and submissions, which are a proven solution for the desired IOPS per building block. For more information, see ESRP Storage Program - EMC CLARiiON CX3-20c (600 User) iSCSI Storage Solution for Microsoft Exchange Server 2007. For more information on Microsoft’s ESRP program, visit: http://technet.microsoft.com/en-us/exchange/bb412164.aspx For more information about EMC solutions using the ESRP framework, visit: http://www.emc.com/esrp

RAID group layout

RAID group layout design

This design was tested based on previous, known performances of the building block configurations using metaLUNs. This storage solution was based with a single DAE solution in mind, having the ability, once this configuration was proven, to show that linear results would be possible as building blocks are added.


14

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

http://www.emc.com/esrp


RAID group diagram

The RAID group layout is illustrated in the following diagram.

Best practices and recommendations

CLARiiON RAID group configuration

For CLARiiON RAID group configuration, it is recommended to: • Keep the Exchange database and log LUNs in separate RAID groups. • Keep the Replication Manager clone LUNs in a separate RAID group from the

Exchange production LUNs. • Balance the RAID group across the storage processors. • Ensure that a hot spare disk is assigned.

Exchange online maintenance

For Exchange online maintenance, ensure that Replication Manager jobs are running outside the Exchange online maintenance window. Do not run Exchange online maintenance against an Exchange storage group while its Replication Manager job is running. Note: Failure to follow this recommendation will cause a large decrease in the clone resync speed and slow online maintenance. A best practice for running Replication Manager jobs is to run them during off-peak hours.

Clone RAID group configuration

For clone RAID group configuration, ensure that a separate RAID group is used for clone LUNs. Note: Failure to do so will result in degraded performance in the production Exchange server and in the time to complete the Replication Manager jobs. Since the clone is used as a protect methodology, using the same drives for the source and destination defeats the purpose.


15

Chapter 3: Server and Network Design


Overview

Introduction This section focuses on the server and network design and layout.

The server design provides details on the physical and logical or virtual servers that were used in this solution. Details on server configuration include the number of processors, network cards, and amount of RAM used. For more information about the hardware specification of the servers, refer to the corresponding Reference Architecture document EMC Backup and Recovery for Microsoft Exchange 2007 enabled by EMC CLARiiON CX4-120, Replication Manager, and Hyper-V on Windows Server 2008 using iSCSI Reference Architecture. The network design section provides an overview and details the best practices for using an iSCSI storage array.

Contents Topic See Page

Server design 17

Network design 19

Best practices for virtual machines 19

Best practices for iSCSI 20


16


Server design

Overview of server design

This solution was created with two Active Directory servers, one physical server and one virtual server. A physical server was also used for the System Center Virtual Machine Manager (SCVMM) server. The rationale for using this is that SCVMM will not install in a Hyper-V child OS. The following describes the configuration of each component used.

Configuration of components

Each Hyper-V Server was configured with 64 GB RAM. Guests were separated onto each Hyper-V Server to maximize the usage of these servers.

Hyper-V Server 1 • Microsoft Active Directory server • Exchange 2007 Mailbox role • Exchange Hub/CAS roles

Hyper-V Server 2 • Replication Manager mount host • Replication Manager Server • LoadGen Server 1 • LoadGen Server 2 The Hyper-V child partitions were configured as follows:

Microsoft Exchange Mailbox Server • 4 processors • 16 GB RAM • 3 network cards

Microsoft Active Directory Server • 2 processors • 2 GB RAM • 1 network card

Microsoft Exchange Hub/CAS Server • 2 processors • 8 GB RAM • 1 network card

EMC Replication Manager mount host server • 2 processors • 8 GB RAM • 3 network cards

Microsoft LoadGen Server • 2 processors • 2 GB RAM • 1 network card


17


EMC Replication Manager Server • 4 processors • 2 GB RAM • 1 network card Note: Microsoft Windows Server 2003 is required for EMC’s Replication Manager Server, which is not currently supported to run on Microsoft Windows Server 2008. Once Replication Manager is supported, it will be possible to have the Replication Manager Server and the mount host as part of the same virtual server. For this solution, the mount host had to be separate, as the mount host must run the same operating system as the production Exchange server. The solution in total requires four licenses for Microsoft Windows Server.

Quantity Description

1 Windows Server 2008 Enterprise* (Hyper-V on Windows Server 2008 allows for up to four guests licenses)

2 Microsoft Windows 2008 Standard Edition Physical Domain Controller Microsoft System Center Virtual Machine Manager

1 Microsoft Windows Server 2003 standard edition for the virtual Replication Manager Server.

* Microsoft’s Microsoft Windows Server 2008 Enterprise License allows the use of up to four instances of the server software in virtual environments (for details, visit http://www.microsoft.com/windowsserver2008/en/us/licensing-faq.aspx). When possible, it is recommended to spread the Virtual Hard Disk (VHDs) files across the CLARiiON service processors to prevent performance issues if there is a very active VM. A recommended configuration with the service processors on a CLARiiON array is:

Service Processor A • Microsoft Active Directory Server • Exchange 2007 Mailbox role • Exchange Hub/CAS roles

Service Processor B • EMC Replication Manager mount host • EMC Replication Manager Server • Microsoft LoadGen Server 1 • Microsoft LoadGen Server 2


18

http://www.microsoft.com/windowsserver2008/en/us/licensing-faq.aspx


Network design

Overview of network design

Two physical 1 Gb/s Ethernet network switches were used for this solution: one for production network traffic and the other for iSCSI (through VLAN) traffic to the array. Dedicated virtual networks were created to match the physical network and iSCSI networks. Guests requiring access to iSCSI were given additional network connections for array connectivity.

Best practices for virtual machines

Overview These changes not only free up space but also free up a lot of memory.

Disable hibernation on Windows Server 2008

Hibernation is on by default in Windows Server 2008. This feature consumes additional processor power and storage space and is not needed for Exchange and Active Directory servers, which have built-in features to handle power loss. To disable hibernation on Windows Server 2008:

1. Run the following command from the command line on all virtual machine servers. powercfg -Hibernate OFF

2. Run the following command to confirm that hibernation is off. Dir /ah

3. Reboot the server.

Registry change

Changing the registry specifies whether the user-mode or kernel-mode drivers and kernel–mode system code can be paged to disk when not in use. Disabling this in a guest OS prevents unnecessary caching in the guest and host. A reboot of the system is needed for this change to take effect. To change the registry, add the following registry key to all virtual machines. Note: Do not do this on a physical server. [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management] • DisablePagingExecutive=dword:00000001


19


Best practices for iSCSI

Best practices The following are some iSCSI best practices for connectivity to EMC CLARiiON

storage arrays using iSCSI connectivity. These recommendations are intended to provide a high performance and stable solution. This section does not include all possible iSCSI best practices. • Always use at least two NIC ports for iSCSI traffic to ensure high availability and

maximum throughput for storage connections. • Use dedicated switches for production and iSCSI networks. If this is not possible,

ensure that VLANs can be created on the switch being used to guarantee that the iSCSI traffic from the server to the array is separated from all other network traffic.

• Ensure that all ports on the switch are set to auto-negotiate 1000. Note: It is not possible to disable auto-negotiation on ports on the Dell Powerconnect 6224 switches. While the GUI/CMD line allows the change, the port will become disabled and non-functional.

• Disable the spanning tree on network switches. • Disable power management on the NICs on the server. • Disable each of the following in advanced settings on the NICs Jumbo packet:

− IPv4 Checksum offload − TCP Checksum Offload (IPv4) − TCP Large send Offload (IPv4) − UDP Checksum Offload (IPv4)

• On the iSCSI NICs on the Exchange servers, clear the checkboxes for Client for Microsoft Networks and File and Printer Sharing for Microsoft Networks.

• Modify the registry with the following changes on the Exchange servers to optimize iSCSI performance: − HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP\Parame

ters KeepAliveTime=Dword:300000 (Decimal)

For more details, visit http://support.microsoft.com/kb/324270. − HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP\Parame

ters\Interfaces{1CDF670F-6155-4652-A317-118489577A22} TcpAckFrequency=Dword:1 (Decimal)

For more details, visit http://support.microsoft.com/kb/328890. For more details on these best practices, please see EMC Solutions for Microsoft Exchange Server 2007 CLARiiON CX3 Series iSCSI - Best Practices Planning. This document is available on EMC’s Powerlink website.


20

http://support.microsoft.com/kb/324270

http://support.microsoft.com/kb/328890

Chapter 4: Installation and Configuration


Overview

Introduction This chapter provides the procedures and guidelines for configuring the components

that make up the validated solution scenario. For more information about the background to this solution, see ESRP Storage Program - EMC CLARiiON CX3-20c (600 User) iSCSI Storage Solution for Microsoft Exchange Server 2007. The configuration presented in this chapter applies to the specific revision levels of components used during the development of this solution. Before attempting to implement any real-world solution based on this validated scenario, gather the appropriate installation and configuration documentation for the revision levels of the hardware and software components in the solution. Version-specific release notes are especially important. EMC Replication Manager software is used for the creation of VSS cloned images and snapshots of the Exchange database and log file LUNs. While the software is capable of backup and restore using this technology, this paper focuses on the backup technology and comparative times when running sequential or parallel jobs. With Replication Manager, it is possible to configure clone jobs to run in order, sequentially, where database and log file LUNs are cloned or snapped one at a time or in parallel, where two jobs can run simultaneously. Backing up and check-summing the databases using the eseutil /K command would complete faster.

Contents This chapter contains the following topics:

Topic See Page

Navisphere CLI scripts configuration 22

Disk management scripts 23


21


Navisphere CLI scripts configuration

Background Several options are available when configuring a CLARiiON CX4-120 storage array.

One option is to use the Navisphere user interface; another is to use the CLARiiON Navisphere Secure Command Line Interface (naviseccli). This solution provides details on using the command line interface. This method is recommended as a best practice because it is faster and gives the ability to document the array configuration while creating the array storage. This information can then be used in a disaster recovery document to quickly re-create the exact configuration.

Overview The CLI commands used to create this solution are provided in the Supporting

Information section. The following steps assume that planning has already taken place on how the entire array is configured, including decisions on the RAID group configuration, RAID type, number of LUNs, size of LUNs, and so on. Note: All lines for each section can be copied and pasted into a Windows command window. Copying and pasting lines of scripts automates the use of the commands without requiring additional user input. All CLI commands provided in this document are specific to this configuration. Details such as RAID types, LUN numbers, names, sizes, and volume labels can be modified to suit the implementation. They are provided here as an example of exactly what was completed to configure this specific solution.

Prerequisites The following are the prerequisites for a successful configuration:

• Prior to configuration Navisphere Agent and Navisphere CLI must be installed. • Connectivity and registration must be set up prior to running the following scripts.

The scripts can be run from any server with Navisphere CLI installed. • Hosts should be set up and configured but they are not required for LUN creation.

Hosts are required for host addition to the storage groups but not for the storage groups themselves.

Steps for naviseccli configuration

The following are the steps for naviseccli configuration: • Create storage groups • Create RAID groups • Bind LUNs • Create reserved LUN pool LUNs • Add LUNs to reserved LUN pool • Add hosts to CLARiiON storage groups • Add LUNs to clone private LUNs


22


Disk management scripts

Overview

Once the LUNs and hosts have been assigned to the storage group, they are available on the server. Rescan the disk drives in the Device Manager and all of the LUNs will appear. Microsoft Windows Server 2008 places new volumes in an offline state by default. Disks must be brought online before partitions can be created. Diskpart can be used to configure each disk completely. Using scripts here simplifies and speeds up the process for configuring the volumes. Planning is required to ensure the scripts are correct.

Make volumes accessible to the host for data

Before the database and log volumes can be configured, the mount points must first be configured. To do this, follow the steps below:

• Type diskpart at the command prompt. The following commands can be selected together and copied and pasted into Diskpart to run automatically without any prompting. Note: This is the configuration for this solution. Disk numbers may differ during implementation. The following is an example of the two script files used with Diskpart to create the S: drive (drive 10 mount point root), and then assign a drive to the mount point directories. The following assumes that drives 10 and 11 are the mount point drives for S: and T: Note: With Windows Server 2008, Diskpart does not require the alignment of a partition to 64. Note: This is only required when using Diskpart. GUI configuration does this automatically. assigning letters for mp root drives -------mountpoint.txt select disk 10 online disk attributes disk clear readonly create partition primary select partition 1 assign letter s: select disk 11 online disk attributes disk clear readonly create partition primary select partition 1 assign letter t: ------- -------mounts.bat


23


format S:\ /fs:NTFS /v:MOUNT_S /a:64K /q /y format T:\ /fs:NTFS /v:MOUNT_T /a:64K /q /y Md s:\sg1db Md t:\sg2db Md t:\sg1lg Md s:\sg2db ------- -------mountdrives.txt select disk 21 online disk attributes disk clear readonly create partition primary select partition 1 assign mount s:\sg1db ----- -------fmtdrives.bat format S:\sg1db /fs:NTFS /v:sg1db /a:64K /q /y format t:\sg2db /fs:NTFS /v:sg2db /a:64K /q /y format t:\sg1lg /fs:NTFS /v:sg1lg /a:64K /q /y format S:\sg2lg /fs:NTFS /v:sg2lg /a:64K /q /y To use these types of files, confirm the drives for the mount points, and then copy the disk 21 commands for each of the drives required for all storage groups. Run the following commands to quickly create the partitions and mount the partitions to the mount points. From the Windows command prompt, enter: C:\Diskpart /s mountpoint.txt C:\mounts.bat C:\diskpart /s mountdrives.txt C:\fmtdrives.bat Using these scripts as an example, it is possible to quickly mount, partition, and format all the presented drives. It is recommended to use a file for recording all the actions.


24

Chapter 5: Testing and Validation


Overview

Introduction Storage design is an important element to ensure the successful development of

EMC’s backup and recovery solution for Microsoft Exchange 2007 enabled by CLARiiON CX4-120, Replication Manager, and Hyper-V on Windows Server 2008 using the Microsoft iSCSI Software Initiator. This chapter provides details on Microsoft Exchange performance, the components tested in this solution, and a summary of the test results.

Contents This section contains the following topics:

Topic See Page

Microsoft Exchange performance 26

Tested components 42

Test results summary 43


25


Microsoft Exchange performance

EMC Backup and Recovery for Microsoft Exchange 2007 Enabled by EMC CLARiiON CX4-120,

Measuring good Exchange performance

Good Microsoft Exchange performance can be measured by multiple factors such as overall server utilization, disk latencies, and good response times from Outlook clients (RPC latencies). Some of the performance parameters analyzed during LoadGen testing included: • RPC Averaged Latency

The RPC Averaged Latency performance counter records the average time, in milliseconds (ms), that it takes to process the last 1,024 packets. If the RPC Averaged Latency performance counter data is lower than 50 ms, the server can process the requests in a reasonable amount of time. If the counter is higher than 50 ms for more than several seconds, this indicates that the server is having difficulty keeping up with the load. As a result, users may experience delays when accessing their e-mail messages.

• RPC Operations/Sec

The RPC Operations/Sec performance counter shows the rate at which remote procedure call (RPC) operations occur. The RPC Operations/sec performance counter is a good rate counter to measure the Exchange Server workload because all MAPI-based actions use the RPC protocol.

• RPC Requests

The RPC Requests performance counter records the number of client computer requests that are currently being processed by Microsoft Exchange. This counter has a maximum value of 100. When the Exchange store has 100 RPC operations being processed, it denies any new connections. On a healthy server, the number of outstanding requests should be lower than 50. If the number is more than 50 for a sustained time, this indicates that the RPCs are backed up and waiting to be processed and that the client computers are probably experiencing delays.

• RPC Num. of Slow Packets

The RPC Num. of Slow Packets performance counter should always be less than two. Some normal operations may take longer than two seconds but the average should always be less than two.

• Process/% Processor Time

Process/% Processor Time is the percentage of elapsed time for which all of the process threads used the processor to execution instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count.

• Processor/% Processor Time

Processor/% Processor Time is the percentage of elapsed time that the processor uses to execute a non-Idle thread. It is calculated by measuring the percentage of time that the processor spends executing the idle thread and then subtracting that value from 100%. (Each processor has an idle thread that consumes cycles when no other threads are ready to run.) This counter is the primary indicator of processor activity and displays the average percentage of busy time observed during the sample interval.

Replication Manager, and Hyper-V on Windows Server 2008 using iSCSI Proven Solution Guide

26


Note that the accounting calculation of when the processor is idle is performed at an internal sampling interval of the system clock (10 ms). On today’s fast processors, % Processor Time can therefore underestimate the processor utilization as the processor may be spending a lot of time servicing threads between the system clock sampling interval. Workload-based timer applications are one example of applications that are more likely to be measured inaccurately, since the timers are signaled just after the sample is taken.

Performance counters for RPC processing

The performance counters used for RPC processing are listed in the following table.

Counter Expected values

MSExchangeIS\RPC Requests Indicates the number of MAPI RPC requests currently being serviced by the Microsoft Exchange Information Store service. The Microsoft Exchange Information Store service can support up to 500 RPC requests simultaneously before rejecting new client requests.

Should always be lower than 70.

MSExchangeIS\RPC Averaged Latency Indicates the latency in milliseconds, averaged across all RPC operations in the past 1,024 RPC packets.

Should always be less than 25 milliseconds.

MSExchangeIS\RPC Operations/sec Indicates the current number of RPC operations that are submitted to the Information Store each second

This is a good indicator of client activity and is used for information only.

MSExchangeIS\RPC Num. of Slow Packets Indicates the number of RPC packets in the past 1,024 that have latencies that are longer than two seconds.

Should always be less than two. Certain normal operations may take longer than two seconds, but the average should always be less than two.

Performance Monitor data

Clone operations included: • Sequential clone operations • Parallel clone operations

Sequential clone operations In the sequential clone operation, each of the four storage groups that contains a single database is cloned separately, running each job one after the other.

Parallel clone operations In the parallel clone operation, each of the four storage groups that contains a single database is cloned, running two jobs simultaneously. The following chart shows the amount of time to complete each job, along with total times for each of these two types of jobs. As can be seen in this comparison, for the commercial-sized mailboxes completion times are almost identical, coming in at approximately 11 minutes per database individually, or 22 minutes when running two


27


storage groups, thus 11 minutes per storage group. Completion times are within two minutes of each other, which is an insignificant amount of time over the job run. The start and stop times listed in the chart are based on the 5022 ECCRM Server event logged in the application event log on the RM server.

RM job Start Complete Serial

Sequential

Job 1 5:07:14 5:18:32 0:11:18

Job 2 5:54:48 6:06:30 0:11:42

Job 3 6:42:04 6:55:39 0:11:35

Job 4 7:28:11 7:39:56 0:11:45

Total Time 0:46:20

Parallel

Job 1-p 3:16:38 3:38:04 0:21:26

Job 2-p 4:29:07 4:51:40 0:22:33

Total Time 0:43:59

Comparing PerfMon counters on the Exchange Server

A side-by-side comparison of PerfMon counters on the Exchange Server was done to give a good visual of the different types of job runs and to see more than the reports only. As can be seen in the following diagram, the Process/% Processor Time runs at the same levels and drops almost identically for the different types of scenario, the only difference being in the duration. This depends on how long the customer will endure the processor hit: 11 minutes * 4, or 22 minutes * 2. If the customer wants shorter periods of higher processor and latencies, running sequential jobs may be preferred. If the customer wishes to have smaller periods of time when the processor and latencies are high, the parallel job method may be preferred. Process/% Processor Time at its lowest was almost identical at 245.


28


Baseline data This run is to show the Exchange baseline while running LoadGen with identical

loads for the two clone method tests. The following diagram shows that the Process/% Processor Time is at the same level as the two cloning tests, without the apparent drops during the cloning of the storage groups.

RPC Averaged Latency

RPC Averaged Latency, when compared in the following charts, shows latencies for the sequential job being slightly higher at 317, except for a brief period at the final portion of the jobs. In the parallel jobs, this same slight spike was lower at 256. Both jobs show a small increase for the first two databases and a slightly higher increase on the second two.


29


Baseline data for RPC Averaged Latency

Baseline data shows the RPC Averaged Latency running extremely well at a maximum of 27.

Effects of cloning on Hyper-V Servers

During the clone job, there was a slight processor increase on the second Hyper-V Server running the clone jobs, which did not exceed more than 20%.

Baseline data for cloning on Hyper-V Servers

In comparison, in the baseline runs the second Hyper-V Server did not exceed 10%, showing that during the brief clone cycles the Hyper-V Server was negligibly affected by the clone jobs. This translates to the other guests/child partitions not being affected by the virtualized RM Mount host guest.


30


Report data The following report data shows RPC and processor minimum, average, and

maximum report data for comparing the two clone methods. From the following charts, the differences between the baseline LoadGen, sequential clone method, and parallel clone method tests can be evaluated. The following table provides the minimum recorded report data.


31


The following table provides the average recorded report data.

The following table provides the maximum recorded report data.


32


Navisphere data during the sequential job runs

The following graph illustrates the Navisphere data during the sequential job runs. SP utilization is 3%-5% during the entire run.


33


Database storage group LUN response times

The following graph illustrates the Exchange database storage group LUN response times below a 4% average, with occasional increases below 20 ms.


34


Log file storage group LUN response times

The following graph illustrates the Exchange log file storage group LUN response times below a 2% average, with occasional increases below 20 ms.


35


Navisphere data during parallel job runs

The following graph illustrates the Navisphere data during parallel job runs. SP utilization is 3%-5% after the clones. During the clone sync, the processors increased to 48% during the run.


36



The following graph illustrates how Exchange database storage group LUNs are shown to have an average identical to the baseline after the clone syncs. During the clone job, response times increased up to 50% max for one storage group, while the others remained at approximately 30%.


37



The following graph illustrates how log file LUN performance also mimics the baseline test except for a brief spike during log file truncation.


38


Service processor performance

The following graph illustrates how SP performance during the sequential job run was similar to the parallel jobs, although appearing to the array as one continual job.


39


Job completions

The following graph illustrates Exchange database storage group LUN performance showing the job completions appearing as one hit on the array. Response times did increase significantly, indicating that it would be better to spread the jobs between runs to minimize this effect.


40


Log file truncation

The following graph illustrates log file truncation appearing much like the parallel job, with a brief response spike during log file truncation.

Conclusion

In conclusion, it was seen that when comparing the baseline for the two jobs, there is an impact to client and server performance, although only for short durations and for very small amounts of time. Due to this impact, it is recommended to run the clone jobs, either sequentially or in parallel, in the course of maintenance cycles during lower client usage. If a customer needs to run multiple clone jobs throughout the day, then the commercial configuration outlined in this document would be able to successfully complete these jobs with only a slight effect on the user base. Based on the amount of time outlined in this document, the customer could run jobs that would, at most, take approximately one hour to complete. This timeframe would fit into clone cycles during normal meal breaks. Since both methods discussed in this document are completed in the same amount of time, and have almost identical impacts, either method is recommended and can be used without cause for concern.


41


Tested components

Introduction The following section details the components that were tested for this solution.

Replication Manager

For Replication Manager, the tests that were completed were as follows: • Validate the functionality of Replication Manager with Hyper-V on a Windows

Server 2008 environment • Validate the performance of Replication Manager without LoadGen running • Validate the performance of Replication Manager with clone jobs running in

sequential operation • Validate the performance of Replication Manager with clone jobs running in parallel

operation


42


Test results summary

Summary of results for Hyper-V on Windows 2008 Server testing

Functionality testing was carried out to determine the ability of Replication Manager to run in different modes in comparison to baseline testing. Baseline LoadGen testing was done prior to the cloning process for comparison of data on the impact of cloning on the Exchange Server and CLARiiON CX4 array. Performance testing was completed in this solution using Microsoft’s LoadGen tool to simulate Exchange I/O. Running Replication Manager jobs with LoadGen also running is intended to simulate running clone job during the peak hours of the production day. These tests indicate the worst-case scenario. Baseline testing and testing with Replication Manager running were both completed. As expected, running Replication Manager clone jobs during the production day has an impact both on the array and on Exchange 2007.

Comparison of baseline LoadGen 95th percentile results

The LoadGen comparisons in the following table show that there is a slight increase in latencies during a few tasks but in major tasks like login and logout, these latencies were negligible.

Baseline Parallel % Difference Sequential % Difference

Task Name 95th Percentile Latency 95th Percentile Latency baseline to parallel 95th Percentile Latency baseline to sequentialBrowseCalendar 124 183 47.58064516 175 41.12903226BrowseContacts 194 411 111.8556701 413 112.8865979BrowsePublicFolder 0 0 0 0 0BrowseTasks 0 0 0 0 0CreateContact 223 766 243.4977578 646 189.6860987CreateFolder 0 0 0 0 0CreateTask 202 717 254.950495 638 215.8415842DeleteMail 0 0 0 0 0DownloadOab 0 0 0 0 0EditRules 0 0 0 0 0EditSmartFolders 0 0 0 0 0ExportMail 0 0 0 0 0InitializeMailbox 0 0 0 0 0Logoff 13 12 -7.692307692 13 0Logon 307118 307089 -0.009442625 306319 -0.26016059MakeAppointment 995 1935 94.47236181 1811 82.01005025ModuleInit 2704 2877 6.397928994 2857 5.658284024ModuleTerm 0 0 0 0 0MoveMail 0 0 0 0 0PostFreeBusy 0 0 0 0 0PublicFolderPost 0 0 0 0 0ReadAndProcessMessages 333 634 90.39039039 594 78.37837838RequestMeeting 1673 8045 380.8726838 4534 171.0101614Search 0 0 0 0 0SendMail 374 1135 203.4759358 1173 213.6363636SynchronizeFolders 0 0 0 0 0UserInit 0 0 0 0 0UserTerm 0 0 0 0 0


43


Baseline LoadGen results

The following diagram illustrates the Navisphere results with no clone jobs running. SP utilization on average is no greater than 5% while supporting 600 users.

LoadGen results

The following table provides details of the LoadGen results.

Task Name Count Actual

Distribution (%)Configured Distribution (%)

Average Latency

95th Percentile Latency

BrowseCalendar 7237 14 14 31 124

BrowseContacts 6026 11 12 65 194

BrowsePublicFolder 0 0 0 0 0

BrowseTasks 0 0 0 0 0

CreateContact 1182 2 1 64 223

CreateFolder 0 0 0 0 0

CreateTask 609 1 1 55 202

DeleteMail 0 0 0 0 0

DownloadOab 609 1 1 0 0

EditRules 0 0 0 0 0

EditSmartFolders 0 0 0 0 0

ExportMail 0 0 0 0 0


44



Task Name Count Actual Distribution (%)

Configured Distribution (%)

Average Latency


InitializeMailbox 0 0 0 0 0

Logoff 1795 3 3 3 13

Logon 600 1 0 20590 307118

MakeAppointment 569 1 2 326 995

ModuleInit 2 0 0 2307 2704

ModuleTerm 0 0 0 0 0

MoveMail 0 0 0 0 0

PostFreeBusy 2506 4 4 9 0

PublicFolderPost 0 0 0 0 0

ReadAndProcessMessages

23858 47 48 97 333

RequestMeeting 589 1 1 775 1673

Search 0 0 0 0 0

SendMail 4795 9 9 120 374

SynchronizeFolders 0 0 0 0 0

UserInit 0 0 0 0 0

UserTerm 0 0 0 0 0

Sequential jobs The following diagram illustrates the Navisphere results with clone jobs running in

sequential operation. As can be seen, each job was run in order, with both jobs completing in 30 minutes and the total job taking approximately one hour to complete.


45





Average Latency








CreateTask 563 1 1 147 717



EditRules 0 0 0 0 0




Logoff 1784 3 3 5 12

Logon 500 0 0 29195 307089


ModuleInit 2 0 0 2203 2877



46



Task Name Count Actual Distribution (%)

Configured Distribution (%)

Average Latency


MoveMail 0 0 0 0 0




24196 48 48 225 634


Search 0 0 0 0 0

SendMail 4784 9 9 303 1135


UserInit 0 0 0 0 0

UserTerm 0 0 0 0 0

Parallel jobs The following diagram illustrates the Navisphere results with clone jobs running in

parallel operation. As can be seen, each job ran at the same time and was completed in 30 minutes.



47




Average Latency








CreateTask 586 1 1 188 638



EditRules 0 0 0 0 0




Logoff 1874 3 3 5 13

Logon 500 0 0 20760 306319


ModuleInit 2 0 0 2199 2857


MoveMail 0 0 0 0 0




23887 47 48 202 594


Search 0 0 0 0 0

SendMail 4784 9 9 293 1173


UserInit 0 0 0 0 0

UserTerm 0 0 0 0 0


48

Chapter 6: Conclusion


Overview

Summary This solution contains all components required to run a messaging infrastructure,

which includes protection, at a relatively low cost. The solution benefits customers in terms of: • Protection • Simplified mailbox design

Protection Replication Manager is ideal for backup automation and acceleration in creating a

“Gold Copy” of the production data for an instant restore in the event of corruption. Replication Manager is an easy to use point-and-click application to manage and automate data protection at the array level.

Simplified mailbox design

By using the building block method, Exchange deployments result in predictable performance for all mailbox servers. The building block method removes any assumptions or guesswork when sizing the servers and storage.

Objectives and results

The following table summarizes the objectives and results.

Objective Result

Confirm the functionality of Replication Manager in a virtualized environment using two different methods for running the jobs

Replication Manager jobs were run both sequentially and in parallel. Two “gold” clones were created and the sequential and parallel jobs worked without issue as expected.

Determine if running Replication Manager jobs would have an impact if run during the production day

Results from LoadGen and Navisphere Analyzer confirmed that running Replication Manager jobs during the production day does have an impact on Exchange 2007 performance. Therefore, it is recommended to run the clone jobs during non-production or off-peak hours Differences were also noticed between the two methods used when taking Replication Manager clones. While both jobs completed within the same timeframe, there was an impact on the number of Exchange tasks that were completed during this time.


49


Conclusion IT infrastructure management is becoming increasingly complex and so are the

needs for constant information availability and detailed management and reporting capabilities. The growth of data is driving longer backup and recovery windows, and core business processes, such as generating copies of data and establishing recovery processes to meet a business’s service level agreements, are taking longer. With the decreasing cost of disk storage, replication technologies are now more cost-effective for enabling realtime backup and recovery in parallel or sequential environments. With this EMC solution and the advanced features of EMC Replication Manager, the discovery of the environment is automated, allowing customers to easily schedule replications in their backup environment. It places their Microsoft application in the proper state for application-consistent replicas, which accelerates backups and provides instant restore capabilities for their test/development environment or production tiered storage environment. Application images can instantly be transferred between servers or between sites to meet the customer’s business needs. This EMC solution, deployed in a virtual environment based on Microsoft Hyper-V, contributes to improving your operational efficiency, so you can deploy fewer resources for completing the operational tasks of detailed management reporting and deploying replication-based backup processes. Testing verified that using Microsoft Exchange Server 2007 SP1, with local data replication, allows for fast data replication in the event of database loss or corruption. The storage layout for this solution is based on a design that utilizes a building block approach, which repeatedly builds upon itself as the customer’s requirements grow and additional space and fault tolerance are required. Testing confirmed that at the smallest building block level all components worked in a single system, as expected, and within Microsoft Exchange database latencies, while running local data replication.


50

Supporting Information


Overview

Introduction to supporting information

This chapter contains supporting information on configuring Navisphere CLI scripts.

Navisphere CLI scripts configuration

Scripts for naviseccli configuration

The following are the scripts for naviseccli configuration. -h 200.0.80.100 as seen in the following CLI examples should be replaced with either the SPa or SPb management IP addresses.

Creating storage groups

naviseccli –h 200.0.80.100 storagegroup –create –gname EXCH

naviseccli –h 200.0.80.100 storagegroup –create –gname F80HYPERV01


naviseccli –h 200.0.80.100 storagegroup –create –gname F80RMH01

naviseccli –h 200.0.80.100 storagegroup –create –gname “EMC Replication Storage”

Creating RAID groups

Creating RAIDGroup 10 for Logs and ESX (Disk 0,1,2,3) ..

NaviSecCLI -h 200.0.80.100 CreateRG 10 0_1_0 0_1_1 0_1_2 0_1_3 -rm yes -pri High

Creating RAIDGroup 11 for Databases (Disk 10,11,12,13) ..

NaviSecCLI -h 200.0.80.100 CreateRG 11 0_1_10 0_1_11 0_1_12 0_1_13 -rm yes -pri High

Creating RAIDGroup 12 for Hotspare (Disk14)..

NaviSecCLI -h 200.0.80.100 CreateRG 12 0_1_14 -rm yes -pri High

Creating RAIDGroup 13 for RMLUNS and RLP (Disk 5,6,7,8,9)..

NaviSecCLI -h 200.0.80.100 CreateRG 13 0_1_5 0_1_6 0_1_7 0_1_8 0_1_9 -rm yes -pri High


51


Binding LUNs

Binding 12GB LUN for Q2RM_SG1LG ..

NaviSecCLI -h 200.0.80.100 bind r1_0 104 -rg 10 -sq bc -cap 25165824 -sp b

naviseccli -h 200.0.80.100 chglun -l 104 -name Q2RM_SG1LG





NaviSecCLI -h 200.0.80.100 bind r1_0 106 -rg 10 -sq bc -cap 25165824 -sp a





Binding 1GB LUN for S ..


naviseccli -h 200.0.80.100 chglun -l 115 -name Q2RM_S

Binding 1GB LUN for T ..


naviseccli -h 200.0.80.100 chglun -l 116 -name Q2RM_T

Binding 175GB LUN for shared hyper-v child partition location


naviseccli -h 200.0.80.100 chglun -l 120 -name hyper-v01

Binding 175GB LUN for shared hyper-v child partition location


naviseccli -h 200.0.80.100 chglun -l 121 -name hyper-v02

Binding 120GB LUN for Q2RM_SG1DB ..


naviseccli -h 200.0.80.100 chglun -l 108 -name Q2RM_SG1DB







52






Adding Disk 14 as hotspare ..

NaviSecCLI -h 200.0.80.100 bind hs 112 -rg 12

Binding 8X120GB LUN for RMDB

NaviSecCLI -h 200.0.80.100 bind r5 130 -rg 13 -sq bc -cap 251658240 -sp a




NaviSecCLI -h 200.0.80.100 bind r5 134 -rg 13 -sq bc -cap 251658240 -sp b




Binding 8X12GB LUN for RMLG









Binding 1GB LUN for S on RMMountHost ..


naviseccli -h 200.0.80.100 chglun -l 146 -name Q2RM_S_RMMH01

Binding 1GB LUN for T on RMMountHost ..


53



naviseccli -h 200.0.80.100 chglun -l 147 -name Q2RM_T_RMMH01

Creating reserved LUN pool LUNs

Binding LUN for Reserved Lun 150

NavisecCLI -h 200.0.80.100 bind r5 150 -rg 13 -sq bc -cap 2097152 -sp a


NavisecCLI -h 200.0.80.100 bind r5 151 -rg 13 -sq bc -cap 2097152 -sp b

























54







Adding LUNs to the reserved LUN pool

NaviSecCLI -h 200.0.80.100 reserved -lunpool -addlun 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165

naviseccli –h 200.0.80.100 storagegroup –create –gname EXCH



naviseccli –h 200.0.80.100 storagegroup –create –gname F80RMH01

naviseccli –h 200.0.80.100 storagegroup –create –gname “EMC Replication Storage”

Adding hosts to CLARiiON storage groups

naviseccli -h 200.0.80.100 storagegroup -connecthost –host F80VEX01 -gname EXCH

naviseccli -h 200.0.80.100 storagegroup -connecthost –host F80HYPERV01 -gname F80HYPERV01

naviseccli -h 200.0.80.100 storagegroup -connecthost –host F80HYPERV02 -gname F80HYPERV01

naviseccli -h 200.0.80.100 storagegroup -connecthost –host F80VRMMH01 -gname F80RMH01

Adding LUNs to clone private LUNs

To enable EMC’s Replication Manager to create clones, two LUNs must be assigned as clone private LUNs on the array. These can be two 1 GB LUNs. To assign these LUNS: • Right-click on the array, navigate to SnapView™ and select Clone Feature

Properties as illustrated. Result: The Clone Features Properties window is displayed.


55



56

• Select the two 1 GB LUNs to be added and select Allow Protected Restore. • Click OK.

EMC Backup and Recovery for Microsoft Exchange … 5: Testing and Validation ... Manager, and...

Documents

Transcript of EMC Backup and Recovery for Microsoft Exchange … 5: Testing and Validation ... Manager, and...