EMC Solutions for Exchange 2003 NS Series iscsi. Reference Architecture Guide A01

Transcription

1 EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide A01 EMC Corporation Corporate Headquarters Hopkinton, MA

2 Copyright 2007 EMC Corporation. All rights reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 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. EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide A01 ii EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

3 Contents Preface... ix Chapter 1 The Business Challenge Business challenge Chapter 2 The Technology Solution Technology solution Chapter 3 The Physical Architecture Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Physical architecture Consolidation Network architecture VLANS Switches EMC Celerra NS Storage architecture RAID Layout File systems iscsi LUNs Application server architecture Microsoft Exchange 2003 cluster architecture Microsoft Cluster Services Microsoft iscsi Initiator Backup Backup architecture Archiving Archive architecture Protection Protect architecture Hardware Resources Hardware resources EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide iii

4 Contents Chapter 9 Software Resources Software resources iv EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

5 Figures Figure 3-1 Physical architecture of the Exchange 2003 NS Series iscsi solution including Store, Backup, Archiving, and Protection Figure 4-1 EMC NS40 Data Mover ports Figure 4-2 NS40 Storage layout Figure 4-3 File system layout for 500 Exchange users (eight disk spindles building block).4-5 EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide v

6 Figures vi EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

7 Tables Table 8-1 Exchange 2003 NS Series iscsi solution hardware resources Table 9-1 Exchange 2003 NS Series iscsi solution software resources Table 9-2 Microsoft Hotfixes EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide vii

8 Tables viii EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

9 Preface This document provides an overview of the architecture of an EMC Solution developed by EMC Global Solutions Operations. Information in this document can be used as the basis for a solution build, white paper, best practices document, or training. Information in this document 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. Audience This document is intended for internal EMC personnel, partners, and customers. It is not intended to be released, in its current form, as part of a technical services or sales kit. Scope This document describes the architecture of an EMC Solution built and tested cooperatively by the EMC Global Solutions lab in Hopkinton, Research Triangle Park Celerra Engineering, the EMC Software Group, and the EMC Technology Solutions Practice. Implementation instructions and best practices are beyond the scope of this document. For detailed information about the tests performed to validate this solution, EMC personnel and partners can refer to the documents listed below. EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide ix

10 Preface Related documents The following documents provide additional, relevant information. They can be found on Powerlink, EMC s password-protected extranet for customers and partners. Access may be restricted to EMC personnel and partners. EMC Solutions for Exchange 2003 NS40 iscsi Validation Test Report Best Practices for Celerra iscsi EMC Celerra iscsi Solutions Microsoft Exchange 2003 Best Practices Storage Configuration Guidelines RepliStor and Exchange 2003: A High Availability Solution Best Practices RepliStor and Exchange 2003: Disaster Recovery via Remote VSS Replication NAS Celerra Network Server Replication Manager / SE iscsi Clustered Disaster Recovery Solution Implementation Guide NAS Celerra Network Server Replication Manager / SE iscsi Nonclustered Disaster Recovery Solution Implementation Guide x EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

11 Chapter 1 The Business Challenge This chapter presents this topic: Business challenge EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide 1-1

12 The Business Challenge Business challenge Mid-sized enterprises and small- to medium-sized businesses (SMBs) need best-in-class solutions for storing, protecting, managing, and archiving their growing volumes of . As a critical business application, Microsoft Exchange must be available at all times. However, managing Exchange and the data it generates can be a challenge in distributed environments with inefficient storage and limited resources. Meeting the needs of internal corporate governance and external regulation adds even more urgency to the challenges of managing , which now must be readily available and easily retrieved. The EMC Solutions for provide a better way to store, protect, manage, and archive . They simplify life cycle management, speed up backup and restore, extend the mailbox size, and reduce costs. They provide the ability to manage an Exchange environment more efficiently, without requiring valuable time from end-users or overburdened IT resources. As an organization grows, availability becomes increasingly critical to success. Microsoft Exchange environments are expected to expand by 50 percent by IT responsibilities for managing this growth will include maintaining uptime and rapidly restoring databases, as well as responding to legal discovery, internal corporate governance, and regulatory compliance requirements for . Managing can be difficult in distributed environments where skills vary from site to site. For many businesses, incomplete backup and recovery, lost user productivity, and patchwork archiving are the norm. These organizations may face the additional challenge of having insufficient resources to research, test, and validate the best possible storage solution for their Microsoft Exchange environment. In distributed environments, backup and recovery is often incomplete, too frequent, and too time-consuming. Organizational productivity suffers because knowledge workers waste time managing.pst files and mailbox limits rather than attending to more strategic work. During this self-management and self-archiving process, many users copy.pst files to shared network drives, increasing IT workload and company / user risk, and adding hidden storage costs. The effects of inefficient management reach beyond IT all the way to the executive office. Meeting legal obligations can hinge on the rapid and accurate production of past traffic, and on ensuring that the necessary process and controls are in place to guarantee authenticity and retention. Legal discovery costs can quickly mount when it takes weeks to find s. Without consolidation and centralized storage policies, retrieval is difficult and time-consuming. 1-2 EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

13 Chapter 2 The Technology Solution This chapter presents this topic: Technology solution EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide 2-1

14 The Technology Solution Technology solution A consolidated Microsoft Exchange infrastructure is the first step toward meeting the challenges of managing . The Exchange 2003 NS Series iscsi solution is an integrated, low-cost, life cycle solution that maximizes the financial and operational benefits of Exchange while enabling rapid database recovery and restoration. The solution offers an enhanced level of archiving. Storing years of in a single storage array, the solution eliminates the need for. PST files and automates the movement of older s by archiving them to lower-cost devices. The solution offers guaranteed and verifiable authenticity of with optimized search, retrieval, and management of archives. 2-2 EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

15 Chapter 3 The Physical Architecture This chapter presents this topic: Physical architecture EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide 3-1

16 The Physical Architecture Physical architecture Figure 3-1 shows the overall physical architecture of the Exchange 2003 NS Series iscsi solution. The solution has four, stackable modules: Store (formerly known as Consolidation), Backup, Archiving, and Protection. The Store module is the core module; the Backup, Archiving, and Protection modules are optional modules. Figure 3-1 Physical architecture of the Exchange 2003 NS Series iscsi solution including Store, Backup, Archiving, and Protection 3-2 EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

17 Chapter 4 Consolidation This chapter presents these topics: Network architecture Storage architecture Application server architecture EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide 4-1

18 Consolidation Network architecture VLANS Switches EMC Celerra NS40 This section describes the network architecture of the validated solution. VLANs, or virtual local area networks logically group devices that are on different network segments, or subnetworks. The validated solution uses VLANs to segregate network traffic of different types. This improves throughput, manageability, application separation, high availability, and security. Figure 3-1 on page 3-2 shows two VLANs: A public VLAN network supports connectivity between the servers and the client workstations, DNS and Global Catalog lookups, and connectivity to the outside world. In this configuration, the public LAN supports connectivity to the management port of the Celerra NS40. The other VLAN is the iscsi Storage Area Network (SAN). This VLAN provides external storage to the servers using the iscsi protocol. Each server that requires external storage from the Celerra NS40 has at least one Network Interface Card (NIC) dedicated to the iscsi SAN. The iscsi SAN also provides connectivity to the four-node EMC Centera for archiving. The iscsi SAN VLAN and public VLAN are completely separate; traffic cannot be routed between them. The switch must be capable of supporting Gigabit Ethernet connections. It is recommended that the ports on the switches support copper-based media. EMC platforms, such as the Celerra NS40 and the four-node Centera, support copper Gigabit Ethernet connections. In addition, Dell servers, such as the 1850 or 2850, have two copper Gigabit Ethernet connections. The Celerra NS40 contains two Data Movers. The Data Movers can operate independently, or they can operate in active/passive mode, with the passive Data Mover serving as a fail-over device for the active Data Mover. In this solution, the Data Movers operate in active/passive mode. The NS40 Data Mover has four network ports. The Figure 4-1 on page 4-3 illustrates the ports on the rear of the EMC NS40 Data Mover. 4-2 EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

19 Consolidation Figure 4-1 EMC NS40 Data Mover ports Storage architecture Only two ports (cge0 and cge1) were connected to the iscsi SAN. These two ports were configured as an aggregated link (LACP) with ip set as the statistical load balancing method. Two virtual interfaces were then created on this device. These interfaces were presented to the Jetstress server. On the Jetstress server, the iscsi initiator was configured to use the Multiple Connections per Server (MC/S) feature to actively utilize both Celerra interfaces. The MC/S load balancing policy was set to weighted path. Note: At least two Celerra network interfaces are required for multipathing solutions such as MC/S. The additional two ports on the NS40 Data Mover (cge2 and cge3) were reserved for file sharing traffic. Setting up storage involves: Establishing the RAID levels Allocating hot spares Creating disk volumes Combining disk volumes into disk pools which can span disks Creating file systems, which can be used to create iscsi LUNs Creating iscsi LUNs, which can be exported to Microsoft Exchange Storage setup can be performed using Celerra Manager software. The software provides the ability to see every disk, create striped metavolumes, and design file systems to support specific database I/O demands. Storage architecture 4-3

20 Consolidation RAID Layout This testing was done using a building block approach. The building block was defined as the number of disk spindles required to support increments of 500 Exchange users assuming an Exchange IO profile of 1 IOPS per Exchange user. It was assumed that each set of 500 Exchange users belong to a different Exchange storage group. In this round of testing, two building block configurations were tested: Six disk spindle building block: Two log spindles and four database spindles Eight disk spindle building block: Two log spindles and six database spindles The six disk spindle building block is the economical configuration in terms of performance/cost. However, this configuration does not provide enough free disk capacity to adequately protect the Exchange logs and databases. To protect the Exchange logs and databases using Celerra iscsi Local or Remote Replicas, the eight disk spindle building block is required. Refer to the EMC Solutions for Exchange 2003 NS40 iscsi Validation Test Report for more details. The figure below shows the RAID layout for a 500 Exchange user configuration using the eight disk spindle building block: Figure 4-2 NS40 Storage layout 4-4 EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

21 Consolidation File systems In the eight disk spindle building block, two disk spindles are dedicated to Exchange log files while the other six disk spindles are dedicated to the Exchange database as shown in Figure 4-3. Figure 4-3 File system layout for 500 Exchange users (eight disk spindles building block) In the above figure, the two Celerra dvolumes in RG 8 are placed in a Celerra userdefined storage pool named Log. The Celerra file system used for storing the Exchange logs is created from the Log storage pool. If the desired file system size is larger than the capacity of a single dvolume, Celerra will automatically concatenate the two dvolumes. For the Exchange database, the two Celerra dvolumes in RG 9 are concatenated in to a Celerra metavolume. Similarly, the two Celerra dvolumes in RG 10 are concatenated in to a Celerra metavolume. The two Celerra dvolumes in RG 11 are also concatenated in to a Celerra metavolume. A Celerra stripe volume with a stripe size of 32Kb is then created across these three metavolumes. This stripe volume is placed in a Celerra userdefined storage pool named DB1. The Celerra file system used to store the Exchange database for the First Storage Group is created from the DB1 storage pool. For this particular building block, to grow from 500 to 1000 Exchange users requires that six additional disk spindles be added to the Celerra. The new set of 500 users will belong to a new Exchange storage group and the Exchange database for that storage group will be placed on the newly added disk spindles. The logs will be stored in a new file system created from the existing Log storage pool. For detailed instructions on creating Celerra file systems for use with Exchange 2003 please refer to the EMC Solutions for Exchange 2003 NS Series iscsi Best Practices Planning document. Storage architecture 4-5

22 Consolidation iscsi LUNs Finally, iscsi LUNs are created within the file systems and are made visible to the servers. The Microsoft Exchange Server will perceive these LUNs as local disks on which databases and logs can reside. For Exchange Clustering, the SMTP (services), and Quorum MUST be on a shared drive accessible to all nodes of the cluster. The SMTP Services Drive and Quorum drive can reside on Celerra iscsi storage. These Celerra iscsi LUNs are carved out of available space in the Log Storage pool. Before a Windows signature is written to any iscsi LUN, it is important to align the disk partition using DISKPART. When a Windows partition is created, it is created starting at the 64th sector. This misaligns the partition with the physical disk. The result is that I/O operations can straddle cylinder boundaries resulting in a significant reduction in performance. This can be fixed using Microsoft's DISKPART utility. Exchange writes data in 4KB blocks. The Celerra file system block size is 8KB. DISKPART can be used to set the partition offset to 64 sectors (32KB). This aligns the partition with the disk cylinder boundaries. An in-depth discussion of this topic can be found in the EMC Engineering white paper Using diskpart and diskpart to Align Partitions on Windows Basic and Dynamic Disks. The following Microsoft TechNet article also covers the topic: ge.mspx Note: For detailed information on the storage architecture validated for this solution, refer to the document entitled EMC Solutions for Exchange 2003 NS40 iscsi Validation Test Report. Application server architecture Microsoft Exchange 2003 cluster architecture This section describes the application server architecture. The active and passive servers shown in Figure 3-1 on page 3-2 represent a Microsoft Exchange cluster, which contains Exchange message stores. The servers in the cluster have Microsoft Windows Server 2003 Enterprise Edition SP1 and Microsoft Exchange 2003 SP2 installed. Note: For information on EMC-qualified Microsoft Cluster Services configurations, use the E- Lab Navigator on EMC Powerlink. Navigate to Server > Cluster Software, select Microsoft MSCS, and click Add to Cart and Get Results. In the Results pane, click iscsi Clusters under Host Connectivity. Each server in each cluster requires three network interfaces. One interface attaches to the public LAN, one interface attaches to the iscsi SAN, and one interface supports the heartbeat between the cluster nodes. Optionally, a fourth port can be used for a multipathing solution such as MC/S. 4-6 EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

23 Consolidation Microsoft Cluster Services Microsoft iscsi Initiator Each server has 4GB of RAM and needs to have its default boot.ini files modified. The operating system line must contain the /3GB switch so that 3GB of address space is available for user-mode applications. The /Userva switch should also be used. This switch provides the ability to allocate memory to each process. The switches should be used in combination as follows: /3GB /Userva=3030 This is the setting recommended by Microsoft to optimize memory usage on Microsoft Exchange 2003 servers. More information is available at the following URL: Exchange relies on the Global Catalog Server to provide Active Directory services; thus, a Global Catalog Server is located on the same network segment as the Exchange servers. The Exchange servers have Microsoft Cluster Services enabled. The cluster operates in an active/passive configuration providing local protection against a server failure. The quorum disk is an iscsi 1GB disk and is on a separate file system from the Exchange data and logs. All targets with storage associated with the cluster are configured as persistent targets. All volumes and devices are persistently bound using the iscsi initiator. Specific recommendations are provided in the document EMC Solutions for Exchange 2003 NS Series iscsi Best Practices Planning. Each server shares the external storage assigned to Exchange. The servers are connected to the external storage through iscsi connections. These connections are created using Microsoft iscsi Initiator 2.3. By default, the Microsoft iscsi Initiator time out is set to 60 seconds. The time out setting determines the period of time the initiator will hold a request before reporting an iscsi connection error. This value can be increased in order to accommodate longer outages, such as Data Mover cluster events. If an iscsi time out occurs on an Exchange server that hosts the Exchange database and transaction logs on iscsi LUNs, the database will be unmounted. To change the time out value, search the Windows Registry for the MaxRequestHoldTime entry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet and change the value to 600 seconds. The following is an example of the Windows Registry entry on an Exchange server: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\ {4D36E97B- E325-11CE-BFC BE10318}\0002\Parameters MaxRequestHoldTime = 600 (DWORD) Application server architecture 4-7

24 Consolidation When masking the production Celerra-iSCSI Exchange LUNs, specify multiple access using the CLI or the iscsi LUN Wizard and provide the name of the iscsi initiator for each node. By doing so, both MSCS nodes will have access to the same LUN in case of MSCS fail-over. After LUN creation, masking, and security steps are completed on the production Celerra system, the active Exchange node should be able to see the iscsi LUN as a raw volume once the initiator logs on to an iscsi session. Format the Celerra-iSCSI LUNs only on the active node, and then register these drives with MSCS as a physical disk under Resources. Do not format the corresponding drive in the standby node. 4-8 EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

25 Chapter 5 Backup This chapter presents these topics: Backup architecture EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide 5-1

26 Backup Backup architecture The combination of Microsoft Windows 2003 Server Enterprise Edition and Microsoft Exchange 2003 supports the backup of Exchange data using Volume Shadow Copy Services (VSS). VSS is a Microsoft service that quiesces the Exchange database and allows a restartable copy of the database to be made. EMC NetWorker and Replication Manager/SE (RM/SE) both support VSS. Backup can be performed directly using the NetWorker Module for Exchange Server, which performs a VSS backup using either tape or ATA disk drives as the target location. In this environment, NetWorker operates on a Windows platform. The server has a tape library directly attached to it. External storage on the NetWorker server is provided through the iscsi SAN. ATA disk drives are partitioned to provide backup-to-disk capabilities. NetWorker operates as a client/server application. Each server that has data to be backed up requires a client that is linked to the NetWorker server. The server can then schedule backups, manage the copies, and provide restore services to the client server. Replication Manager/SE provides snapshot capabilities for Exchange. The software is installed on the Exchange cluster and is VSS-compatible. The utility server is used to validate the Exchange snapshots. The snapshots are mounted to the utility server and Microsoft's ESEUTIL program is run to ensure application integrity. The snapshots can then be backed up to another medium, such as tape or ATA disk, using NetWorker. The snapshots can be backed up as flat files. This reduces the impact on the production Exchange server during backup. RM/SE can be loaded on the Exchange cluster to take advantage of snapshot technology to produce local replicas of the Exchange message stores. It is a best practice to take database snapshots during non-production hours and during times when the process of taking the snapshots does not conflict with other database maintenance procedures. RM/SE supports Microsoft clusters, but the message store replicas cannot be mounted back to the cluster to run ESEUTIL, the Microsoft Exchange consistency checker. The message store replicas need to be mounted to the utility server for the consistency check. A full Exchange license is not required on the utility server. Loading the Exchange administrative tools will load ESEUTIL and the necessary.dll files. After the message stores have been checked for consistency, NetWorker can be used to copy the replicas to tape or other media. RM/SE causes a decrease in user space. RM/SE stores backups on the same file system as the production iscsi LUN. Storage requirements for a given number of users depend on the number of backup snapshots the Exchange administrator keeps. This space reservation ensures that snapshots always have sufficient space to complete and that the worst-case restore scenarios can complete successfully. 5-2 EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

27 Backup Note: For detailed information on the backup architecture validated for this solution, refer to the document entitled EMC Solutions for Exchange 2003 NS40 iscsi Validation Test Report. Backup architecture 5-3

28 Backup 5-4 EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

29 Chapter 6 Archiving This chapter presents these topics: Archive architecture EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide 6-1

30 Archiving Archive architecture Exchange archiving can be performed using either Xtender or Xtender Archive Edition. Both Xtender and Xtender Archive Edition include an extraction feature, which uses Exchange administrative privileges to scan mailboxes for messages that meet a specified policy. The most common policy is to find messages and attachments that are older than a specified time period; for example, 30 days. The time period can be based on either the received date or the last read date. The messages are then archived and removed from the message store. A 2KB pointer stub is left in the mailbox to allow the user to retrieve the message and attachments from the archive. An MS Outlook plug-in that enables users to search their own archives is also available. Xtender (not Xtender Archive Edition) includes journaling capabilities in addition to extraction capabilities. Journaling captures all messages coming in to or going out from the Exchange server. Xtender then scans the journal mailbox and archives a copy of all messages. This configuration can be used in cases where regulatory compliance is needed. For example, in financial institutions, regulations require the archiving of all s to or from specific brokers. This solution was validated using Xtender Archive Edition. The solution is, however, fully compatible with Xtender for customers that require both extraction and journaling capabilities. DiskXtender can be added to the Xtender server or installed on a separate server. DiskXtender adds the capability to move archive databases to ATA disk drives or to the four-node Centera platform. DiskXtender has a set of user-defined policies that facilitate the automated movement of files from one class of storage to another. DiskXtender enables customers to implement an ILM strategy for . For example, as items age, DiskXtender can move the current archive database to ATA storage and then, after a specific period of time, move the archive database to Centera. Note: For detailed information on the backup architecture validated for this solution, refer to the document entitled EMC Solutions for Exchange 2003 NS40 iscsi Validation Test Report. 6-2 EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

31 Chapter 7 Protection This chapter presents these topics: Protect architecture EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide 7-1

32 Protection Protect architecture The Protection module of the solution uses EMC RepliStor 6.2 or Replication Manager/SE 3.1 to replicate Exchange data to a remote EMC Celerra system. You should choose one of these software packages based on your needs. The primary difference between the two packages is that in a RepliStor provides host-based replication, while Replication Manager / SE provides array based replication.. Validation has shown that both software packages can do the following: Replicate Exchange databases and log files from a source production Exchange server (or cluster of servers) to a target disaster recovery Exchange server or cluster. Facilitate application failover if the production Exchange host or production Celerra fails, so that MS Outlook users can access the disaster recovery site Exchange replicas as quickly and as smoothly as possible. Fail back replicated volumes when the production site has been restored. The difference between these solutions is that RepliStor implements host-based replication and requires that the Exchange server go offline during the initial replication job. Thereafter it maintains a nearly synchronous replica at the remote site. The Replication Manager / SE solution implements array-based replication and does not require application downtime. This solution creates new replicas at scheduled intervals. In both cases EMC recommends using Microsoft Cluster Services to provide local highavailability for mission critical applications. Both of the protection solutions presented in this section are compatible with MSCS. The validation tests for both solutions were performed with a two-node MSCS cluster in active/passive mode (1+1) at the primary site, and a single node (1+0) cluster at the disaster recovery site. Please refer to the following documents for more information. They can be found on Powerlink, EMC s password-protected extranet for customers and partners. Access may be restricted to EMC personnel and partners. EMC Solutions for Exchange 2003 NS40 iscsi Validation Test Report Best Practices for Celerra iscsi NAS Celerra Network Server Replication Manager / SE iscsi Clustered Disaster Recovery Solution Implementation Guide NAS Celerra Network Server Replication Manager / SE iscsi Nonclustered Disaster Recovery Solution Implementation Guide EMC RepliStor for Microsoft Windows Administrator s Guide RepliStor and Exchange 2003 A High Availability Solution Best Practices 7-2 EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

33 Chapter 8 Hardware Resources This chapter presents these topics: Hardware resources EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide 8-1

34 Hardware Resources Hardware resources The Exchange 2003 NS Series iscsi solution uses the hardware listed in Table 8-1. Table 8-1 Exchange 2003 NS Series iscsi solution hardware resources Hardware Quantity Configuration Consolidation EMC Celerra NS40 One DART release Two Data Movers GB, 15K FC drives 5 320GB ATA drives Dell PowerEdge 1850 or 2850 Three Two 3.0 GHz Intel Pentium4 processors server BIOS Level: A MB memory Two on board 10/100/1000 MB Ethernet NICs (Intel Pro 1000) One additional 10/100/1000 MB Ethernet NIC (DGE-560T Gigabit PCI Express) Gigabit Ethernet switch One Cisco Catalyst 6509 with Catalyst OS 6.4(11) or Cisco Catalyst 3560G with IOS 12.2(25)SEB4 Copper Gigabit Ethernet ports Backup Dell PowerEdge 1850 or 2850 Two Two 3.0 GHz Intel Pentium4 processors server BIOS Level: A MB memory Two on-board 10/100/1000 MB Ethernet NICs (Intel Pro 1000) One additional 10/100/1000 MB Ethernet NIC (DGE-560T Gigabit PCI Express) Dell PowerVault 132T tape One library Archiving EMC four-node Centera One Four-node cluster, two access nodes Dell PowerEdge 1850 or 2850 One Two 3.0 GHz Intel Pentium4 processors server BIOS Level: A MB memory Two on-board 10/100/1000 MB Ethernet NICs (Intel Pro 1000) One additional 10/100/1000 MB Ethernet NIC (DGE-560T Gigabit PCI Express) 8-2 EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

35 Hardware Resources Hardware Quantity Configuration Protection EMC Celerra NS40 One DART release Dell PowerEdge 1850 or 2850 server Two Data Movers GB, 15K FC drives 5 320GB ATA drives Two Two 3.0 GHz Intel Pentium4 processors BIOS Level: A MB memory Two on-board 10/100/1000 MB Ethernet NICs (Intel Pro 1000) One additional 10/100/1000 MB Ethernet NIC (DGE-560T Gigabit PCI Express) Gigabit Ethernet switch One Cisco Catalyst 6509 with Catalyst OS 6.4(11) or Cisco Catalyst 3560G with IOS 12.2(25)SEB4 Copper Gigabit Ethernet ports Optional Replication Manager/SE mount host Note: Replication Manager/SE environments only Two Configuration - Optional for Non- Clustered environments Serves as a management host for Replication Manager Environment - see Replication Manager / SE User Guide for details Hardware resources 8-3

36 Hardware Resources 8-4 EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

37 Chapter 9 Software Resources This chapter presents these topics: Software resources EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide 9-1

38 Software Resources Software resources The Exchange 2003 NS Series iscsi solution uses the software listed in Table 9-1. Table 9-1 Exchange 2003 NS Series iscsi solution software resources Software Quantity Configuration Consolidation Microsoft Windows 2003 Server Enterprise Edition SP1 or later. See Table 9-2 for hotfixes. Three licenses Installed on Exchange servers and Global Catalog server Microsoft Exchange 2003 SP2 Two licenses Installed on Exchange servers Microsoft iscsi Initiator Two licenses Installed on Exchange servers Backup Microsoft Windows 2003 Server Enterprise Edition SP1 Two licenses Installed on Utility server and NetWorker server or later. See Table 9-2 for hotfixes. Microsoft Exchange 2003 SP2 or higher One license Installed on Utility server Microsoft Exchange 2003 Administrative Tools Included with Microsoft Exchange 2003 Installed on Utility server Microsoft iscsi Initiator Two licenses Installed on Utility server and NetWorker server EMC NetWorker 7.3 One license Installed on NetWorker server EMC NetWorker Module for Two licenses Installed on Exchange servers Exchange Server EMC NetWorker Windows Two licenses Installed on Exchange servers Client EMC Solutions Enabler One license Installed on Utility server Sun Java Freely available from Sun Installed on Utility server EMC Replication Manager/SE One license Installed on Utility server Archiving Microsoft Windows 2003 Server Enterprise Edition SP1 or later. See Table 9-2 for hotfixes. One license Installed on Xtender/DiskXtender server Microsoft Outlook 2003 One license Installed on Xtender/DiskXtender server Microsoft iscsi Initiator One license Installed on Xtender/DiskXtender server Microsoft SQL 2000 Standard Edition One license Installed on Xtender/DiskXtender server Xtender 4.8 One license Installed on Xtender/DiskXtender server 9-2 EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide

39 Software Resources Software Quantity Configuration DiskXtender 6.0 One license Installed on Xtender/DiskXtender server Protection Microsoft Windows 2003 Server Enterprise Edition SP1 or later. See Table 9-2 for hotfixes. Microsoft Exchange 2003 SP2 or higher Note: RepliStor Environments only EMC Replication Manager/SE 3.1 Note: Replication Manager/SE Environments only Two licenses One licenses Installed on Exchange server and Global Catalog server Installed on Exchange server Microsoft iscsi Initiator One licenses Installed on Exchange server EMC RepliStor 6.2 Three licenses Installed on source cluster (two servers) and target cluster (one server) Five licenses Installed on source cluster (two servers) target cluster (one server) and mount hosts (two servers) Note: The environment must have either RepliStor or RMSE, not both. Table 9-2 Microsoft Hotfixes Hotfixes KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB Software resources 9-3

40 Software Resources Hotfixes KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB KB EMC Solutions for Exchange 2003 NS Series iscsi Reference Architecture Guide