Deployment Guide Microsoft® Windows® Storage Server 2003 Feature Pack for DellTM PowerVaultTM NAS Systems Guidelines for Deployment of the Feature Pack
Information in this document is subject to change without notice. ©2004 Dell Inc. All rights reserved. Reproduction in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden. Trademarks used in this text: Dell, the DELL logo, and PowerVault, are trademarks of Dell Inc; Microsoft and Windows are registered trademarks of Microsoft Corporation.
Contents Introduction ...................................................................................................................7 Overview of the Feature Pack ...........................................................................................8 Audience.......................................................................................................................8 Scope ....................................................................................................................
Contents Installing Patches ..........................................................................................................33 Uninstalling the Feature Pack..........................................................................................33 Chapter 3: Moving Exchange Files to a NAS System...................................................37 Overview of the Remote Storage Tools for Exchange........................................................
Contents The DFS root or DFS links are missing on the Exchange server. ..................................59 The mapped drive that Exchange uses was deleted or is not being created. .................60 Appendix A: Detailed Report Log File..........................................................................63 Viewing a Detailed Report Log File ..................................................................................64 Contents of the Detailed Report .............................................
Contents Feature Pack Deployment Guide 6
Introduction This guide assists in the deployment of the Microsoft® Windows® Storage Server 2003 Feature Pack on DellTM PowerVaultTM NAS systems. It includes topics such as installing the Feature Pack, moving Exchange databases and transaction logs to the Windows Storage Server computer, using Exchange database tools and applications with the Feature Pack, and troubleshooting common problems that might occur when using Feature Pack.
Introduction Overview of the Feature Pack The Microsoft Windows Storage Server 2003 Feature Pack (Feature Pack) allows Microsoft Exchange Server 2003 databases and transaction logs to be stored on Dell PowerVault network attached storage (NAS) systems running Microsoft Windows Storage Server 2003. A single Windows Storage Server computer running the Feature Pack can host the databases and transaction logs of up to two Exchange servers and up to fifteen hundred Exchange mailboxes.
Introduction Feature Pack Documentation In addition to this Deployment Guide, other documentation for the Feature Pack is available in several formats. Table 1: Additional Documentation for the Feature Pack Type of Documentation Description Context-Sensitive Help for the Remote Storage Wizard The Remote Storage Wizard on the Exchange Server is a Feature Pack tool that includes context-sensitive help topics accessible by using a Help button on each wizard page.
Introduction Feature Pack Deployment Guide 10
CHAPTER 1 Planning a Deployment The Microsoft Windows Storage Server 2003 Feature Pack enables organizations to consolidate Microsoft Exchange Server 2003 database and transaction logs on a single Windows Storage Server computer. This chapter describes how to plan the deployment of the Feature Pack. A thorough deployment plan is essential to minimize downtime during Feature Pack installation.
Planning a Deployment Planning Deployment of the Windows Storage Server Computer The Feature Pack supports a total of 1,500 Exchange mailboxes on one or two active Exchange servers that are connected to one Windows Storage Server computer.
Planning a Deployment Low-Capacity Scenario The low-capacity scenario supports up to 250 mailboxes on one Exchange 2003 server. Table 1.
Planning a Deployment Notice It is not recommended to store Exchange databases and transaction logs on the same disk drive on the Windows Storage Server computer. This configuration degrades disk performance and leaves the server vulnerable to data loss in the event of physical disk corruption. Because corruption of the disk damages both the Exchange databases and the transaction logs, a recovery operation can restore only data from the last successful backup. All data stored after the last backup is lost.
Planning a Deployment Figure 1.2 Recommended Configuration for the Medium-Capacity Scenario Medium-Capacity Disk Drive Configuration The medium-capacity disk drive configuration stores the Exchange databases on a RAID-5 volume that spans four disk drives on the Windows Storage Server computer. -OrThe medium-capacity disk drive configuration stores the Exchange databases and transaction logs on separate RAID volumes that span separate disk arrays (if available) on the Windows Storage Server computer.
Planning a Deployment High-Capacity Scenario The high-capacity scenario supports up to a total of 1,500 mailboxes on one or two Exchange 2003 servers. Table 1.
Planning a Deployment High-Capacity Disk Drive Configuration The disks are configured according to Exchange best practices, in which the Exchange databases and transaction logs for each storage group are stored on separate RAID volumes that span separate disk arrays on the Windows Storage Server computer. High-Capacity Network Configuration In the high-capacity scenario shown in Figure 1.
Planning a Deployment Figure 1.4 Sample Network Topology for One Windows Storage Server Computer Hosting Storage Groups for Two Stand-Alone Exchange Servers Planning the Move to the Windows Storage Server Computer Deploying the Feature Pack on Exchange Server 2003 involves deploying the Exchange Server 2003 computer and then moving the Exchange databases and transaction logs to the Windows Storage Server computer.
Planning a Deployment Deploying the Feature Pack with Exchange Server 2003 requires the following steps: 1. Deploy the Exchange Server 2003 computer. If a new Exchange Server 2003 computer is being deployed: Perform the Exchange Server 2003 installation on the target computer. If an existing Exchange Server 2003 computer is being deployed: Perform a full backup of the Exchange database to minimize the size of transaction logs.
Planning a Deployment Table 1.4 Sample File Transfer Time Estimate File Type Quantity Size Bytes (Approximate) Exchange database (.edb) 1 6.14 GB 6,593,000,000 Streaming database (.stm) 1 2 MB 2,097,000 Transaction logs 1,375 6.71 GB 7,205,000,000 Total = 13,800,097,000 File transfer rate is approximately 755,000,000 bytes per minute. 13,800,097,000/ 755,000,000 = ~18 File transfer time is approximately 18 minutes.
Planning a Deployment switch that supports virtual LANs (VLANs). A separate connection to the public network is required for access to Active Directory and, optionally, to provide client access for generalpurpose file sharing. Figure 1.5 Topology with Two 2-Node Active/Passive Exchange Server Clusters The Feature Pack also supports one 2-node active/passive Exchange cluster and one stand-alone Exchange server, as shown in Figure 1.6. Figure 1.
Planning a Deployment Remotely Storing Files from an Active/Active Exchange Cluster The Feature Pack supports one active/active Exchange cluster, as shown in Figure 1.7. In the supported configuration, both Exchange servers in the cluster are active and access the Windows Storage Server computer at the same time. If one of the cluster nodes fails, the storage group operations of the failed node are handled by the other node, thereby preventing loss of service.
CHAPTER 2 Installing the Feature Pack This chapter provides instructions for installing the Feature Pack on both the Windows Storage Server computer and the server that is running Microsoft Exchange Server 2003. It describes the components that the Feature Pack installs on each server. These components provide tools and services that allow you to store Exchange databases and transaction logs on a Windows Storage Server computer. This chapter also provides instructions for uninstalling the Feature Pack.
Installing the Feature Pack Components Installed with the Feature Pack The Feature Pack adds new components to both the Windows Storage Server computer and the Exchange server. Windows Storage Server Computer The Feature Pack installation procedure: Adds a New Share for Exchange Files task to the Microsoft Web User Interface for Windows Server Administration (Web UI). The new task allows an administrator to easily create and manage the shares that host Exchange databases and transaction logs.
Installing the Feature Pack Drive Mapping on the Exchange Server The Feature Pack works with Exchange tools and services to enable the Exchange server to access remotely stored databases and transaction logs on the Windows Storage Server computer. The Distributed File System (DFS) sets up and provides access to the paths for remotely stored files and folders.
Installing the Feature Pack Table 2.1 explains how network addresses for remotely stored Exchange files are mapped to a local drive on the Exchange server by different services on the Exchange server. For a full discussion of how link names and link targets relate to the current location and the Active Directory location of remotely stored Exchange database files and transaction logs, see Appendix A, “Interpreting the Detailed Report Log File.” Table 2.1 Drive Mapping for the {StorageServer.
Installing the Feature Pack Procedures for Installing the Feature Pack The installation involves the following tasks: 1. Ensuring that installation requirements are met. 2. Setting up and configuring a dedicated network for Exchange database traffic (recommended). 3. Editing the hosts files on the Exchange server and Windows Storage Server computer to use the dedicated network. 4. Configuring the disk drives on the Windows Storage Server computer. 5.
Installing the Feature Pack Using a Dedicated Network A dedicated network between the Exchange server and the Windows Storage Server computer is recommended to handle Exchange database traffic between the two computers. A second network adapter in each server is used to connect to the public network and to Active Directory. For more information about setting up the dedicated network, see “Setting Up the Dedicated Network” later in this chapter.
Installing the Feature Pack Figure 2.2 shows a network topology for a single Windows Storage Server computer that hosts databases and log files for two Exchange servers. For each Exchange server, a dedicated network handles Exchange database traffic to and from the Windows Storage Server computer. Figure 2.2 Sample Network Topology for a Single Windows Storage Server Computer Hosting Storage Groups for Two Exchange Servers In the simplest case, the dedicated network is created by using a crossover cable.
Installing the Feature Pack To edit the hosts file 1. On each server, open the hosts file, located in the %windir%\system32\drivers\etc\ folder. 2. On the Exchange server, add a line to the hosts file that maps the computer name to the IP address of the Gigabit network adapter. For example: 10.0.0.1 storage-01 3. On the Windows Storage Server computer, add a line to the hosts file that maps the Exchange Server name to the IP address of the Gigabit network adapter. For example: 10.0.0.
Installing the Feature Pack To install the Feature Pack components using the Setup wizard 1. Launch the Feature Pack Installation Web Interface. The Installation Web Interface is launched when the 'WSS 2003 Feature Pack' installation package is first run on the NAS system. To subsequently launch the Installation Web Interface, double click on install.htm, located in the c:\Dell\Install\Feature Pack folder. 2. From the Feature Pack Installation Web Interface, click the Installation Tab.
Installing the Feature Pack Creating an SMB Share for Exchange Server Installation The installation of the Feature Pack creates a folder on the Windows Storage Server computer that contains the setup and installation files for the Exchange server installation of the Feature Pack. Before installing the Feature Pack on the Exchange server, the contents of this folder must be shared. To create an SMB share for Exchange server installation 1.
Installing the Feature Pack To install the Feature Pack on an Exchange 2003 server by using the Setup wizard 1. At the Run command on each Exchange server that requires Feature Pack installation, connect to the SMB share on the Windows Storage Server computer by entering \\servername\sharename where: servername is the name of the Windows Storage Server computer sharename is the name of the SMB share on the Windows Storage Server computer that was previously created 2.
Installing the Feature Pack Pack components while Exchange databases and transaction logs are on a Windows Storage Server computer will cause those databases and transaction logs to be inaccessible from Exchange, and can result in database loss or corruption. If the Feature Pack is being uninstalled on the Exchange server, the uninstaller checks for Exchange databases or transaction logs from the Exchange server that are currently stored on a Windows Storage Server computer.
Installing the Feature Pack To uninstall Feature Pack components by using the Setup wizard (attended mode) Exchange server and Windows Storage Server: 1. In Control Panel, double-click Add or Remove Programs. 2. Click Windows Storage Server 2003 Feature Pack, and then click Uninstall. 3. Repeat this process on the Exchange server (or on all clustered Exchange servers), and on the Windows Storage Server computer.
Installing the Feature Pack Feature Pack Deployment Guide 36
CHAPTER 3 Moving Exchange Files to a NAS System The Feature Pack provides two tools that are used to move the databases and transaction logs for an Exchange storage group to a Windows Storage Server computer: the Remote Storage Wizard and the WSSExchMove.exe command-line tool. These tools perform the configuration updates that are needed to give Microsoft Exchange Server 2003 access to the remotely stored files.
Moving Exchange Files to a NAS System Overview of the Remote Storage Tools for Exchange To move the databases and transaction logs for an Exchange storage group to a Windows Storage Server computer, you must use a remote storage tool. If you move files without using a remote storage tool, Exchange Server 2003 cannot access the remotely stored files. The Feature Pack provides two remote storage tools: Remote Storage Wizard WSSExchMove.
Moving Exchange Files to a NAS System dismounted stores are remounted to restore service from the Exchange databases. After a full move, the Exchange server is fully operational; no further action is required. Configuration Update Configuration updates are performed without transferring the physical files. The existence or the state of the physical files is not verified before any action is taken.
Moving Exchange Files to a NAS System Mapping Exchange Shares to a Local Drive During a full move or a configuration update, a DFS link is created for each database (.edb) file and streaming database (.stm) file that is moved. If transaction logs are moved, a single DFS link is created for the log file path. The link names have the format {servername.
Moving Exchange Files to a NAS System The registry entries for DFS links are stored in the Cluster registry key, which is replicated on all servers in the cluster. Therefore, all Exchange servers in the cluster store the configuration of all remotely stored Exchange storage groups on all of the servers. Note For information about the Exchange cluster configurations the Feature Pack supports, see Chapter 1, “Planning a Deployment.
Moving Exchange Files to a NAS System Moving Files to a Windows Storage Server Computer The remote storage tools for Exchange are used to move the databases and transaction logs for an existing Exchange storage group to existing shared folders on the destination Windows Storage Server computer. For this reason, moving Exchange files to a Windows Storage Server computer involves two steps: 1. On the Windows Storage Server computer, create shared folders to store the Exchange databases and transaction logs.
Moving Exchange Files to a NAS System Using the Administration Web UI to Create an Exchange Share You can use the New Share for Exchange Files task in the Administration Web UI to create a share that is configured to host stores or transaction logs for an Exchange storage group. The Exchange share is configured to use the Server Message Block (SMB) protocol. As you create the share, you can automatically assign the permissions that are needed to give Exchange access to the files.
Moving Exchange Files to a NAS System Sharing a Folder by Using Windows Explorer If you prefer to use Windows Explorer to share a folder to host Exchange databases and transaction logs, create an SMB share. Assign the required Full Control permissions for the share. Then assign the same permissions for the underlying folder. If you create a share by using Windows Explorer, its properties can only be updated by using Windows Explorer.
Moving Exchange Files to a NAS System When you perform a configuration update, it is important to finish copying the files before you attempt to remount the Exchange stores. Mounting the Exchange stores before all existing transaction logs have been moved will invalidate previous backups. If the database is remounted before the transaction logs are moved, the Restore utility will only be able to restore the database through the time of the last backup.
Moving Exchange Files to a NAS System Table 3.2 Moving Exchange Files by Using the Remote Storage Wizard Wizard Page Description Storage Destination Specify either the Windows Storage Server computer or the Exchange server as the storage destination for the Exchange files. Type of Move To specify the type of move, choose either Full move (to update the configuration and move the physical files) or Configuration update (to update the configuration without moving the files).
Moving Exchange Files to a NAS System Table 3.3 WSSExchMove.exe Parameters Used to Move Exchange Files Parameter Description server Specifies the name of the Exchange server that owns the Exchange databases and transaction logs that are to be moved. This is the local Exchange server unless the Exchange server is clustered. For an Exchange cluster, enter the name of the virtual server. Note: When moving a storage group for an Exchange cluster, all servers in the cluster must be online.
Moving Exchange Files to a NAS System To view a Detailed Report From the Remote Storage Wizard, on the completion page, select the View detailed report when the wizard closes check box to view a log file that contains the current configuration when the wizard completes. -Or- To view the results of a move that was just completed using WSSExchMove.exe, open the most recent Detailed Report log file that was saved in your My Documents\Windows Storage Server Logs\ folder.
CHAPTER 4 Using Exchange Tools and Applications The Feature Pack is designed to work seamlessly with the Microsoft Exchange Server 2003 administrative applications and tools that are currently used to manage Exchange Server 2003 storage groups. However, whenever a storage group is remotely stored, the number of network calls that are required to perform basic database operations can increase. These basic database operations include defragmentation, backup, and restoration.
Applications and Exchange Tools Planning for the Use of Exchange Tools and Applications with the Feature Pack Exchange administrative tools and applications are used to perform database procedures that may require the transfer of data between servers and over the network. For example, data is typically transferred between the server that hosts the databases and transaction logs and either the Exchange server or a backup server.
Applications and Exchange Tools Figure 4.2 Configuration 2: Backup/Restore on a Windows Storage Server Computer Configuration 3, shown in Figure 4.3, has the following components: An Exchange server A Windows Storage Server computer hosting the Exchange databases and transaction logs A stand-alone backup server Figure 4.3 Configuration 3: Stand-alone Backup Server Table 4.
Applications and Exchange Tools In general, applications that directly access Exchange databases or transaction logs should be run from the location of the databases or transaction logs. This configuration does not require network data transfers and may reduce processing time. As described earlier, the location of Exchange administrative tools and applications affects the volume of network data traffic.
Applications and Exchange Tools Table 4.2 ESEUtil.exe Procedures that Should Be Run from the Server that Contains the Exchange Databases Procedure Description Defragmentation Eseutil /d Makes used storage contiguous, eliminates unused storage, and compacts the database. Eseutil.exe copies database records to a new database. If there is insufficient space on the original server, the new database could be created on a different server.
Applications and Exchange Tools Table 4.4 ESEUtil.exe Procedures that Can Be Run from Different Locations Procedure Description File Dump Eseutil /m Displays the contents of a file on the screen. Run this procedure from either the Exchange server or the Windows Storage Server computer. Copy File Eseutil /k Reads and writes the database one time. This operation runs faster than the normal file copy process, but only one file can be copied at a time.
Applications and Exchange Tools recovery time. The Feature Pack supports the use of Recovery Storage Groups for Exchange databases that are stored remotely on a Windows Storage Server computer. As with any storage group, either the Remote Storage Wizard or WSSExchMove.exe must be used to move the Recovery Storage Group to the Windows Storage Server computer. In this case, the move must be completed before the databases in the Recovery Storage Group are mounted and before the restore process begins.
Applications and Exchange Tools Feature Pack Deployment Guide 56
CHAPTER 5 Troubleshooting This chapter provides solutions to some common problems that occur when a Dell PowerVault NAS system running Microsoft Windows Storage Server 2003 is used to host Exchange databases and transaction logs. Where multiple solutions are offered, the most common solution is presented first. Apply the solutions in the order in which they are presented.
Troubleshooting What do I do if my installation is not successful? Solution: Eliminate sources of interference, and repeat the installation. 1. Make sure the server meets the software requirements for the Feature Pack. For a listing of software requirements for using the Feature Pack with the Exchange server and the Windows Storage Server computer, see Chapter 2, “Installing the Feature Pack.” 2. Close all open applications and install Microsoft Windows Storage Server 2003 Feature Pack again. 3.
Troubleshooting 2. Assign the required permissions for the shares and for the underlying folders. 3. Use a remote storage tool to perform the full move again. My move was not successful because the databases could not be remounted. Solution: Troubleshoot problems with the Exchange databases. When completing a full move, the remote storage tool attempts to mount any Exchange stores that were involved in the move.
Troubleshooting Solution 2: Reinstall the Feature Pack; then perform a configuration update to recreate the DFS links. Notice Before you uninstall the Feature Pack, it is important to verify that all remotely stored Exchange databases were shut down cleanly. If you reinstall the Feature Pack while corrupted databases are stored on Windows Storage Server computers, recovery procedures in Exchange might not work correctly for those databases. 1.
Troubleshooting Solution 1: Restart the Windows Storage Server Mapping Service to recreate the drive mapping for the DFS root. 1. Restart the Windows Storage Server Mapping Service: a. On the Program menu, click Administrative Tools, and then click Component Services. b. In the console tree, click Services (Local). c. In the detail pane, right-click Windows Storage Server Mapping Service, and then click Start.
Feature Pack Deployment Guide 62
Detailed Report Log File APPENDIX A Detailed Report Log File The Detailed Report log file provides a summary of the current configuration and status of storage groups on the Exchange server when Microsoft Windows Storage Server 2003 Feature Pack is in use. For an Exchange cluster, the log file provides information about all storage groups on each virtual server in the cluster.
Detailed Report Log File Viewing a Detailed Report Log File Whenever a remote storage tool is used to move Exchange databases or transaction logs to a Windows Storage Server computer, a Detailed Report log file is saved. The Detailed Report describes the current configuration of storage groups on the Exchange server, and the status of the shares that are currently being used to host Exchange databases and transaction logs. The log files are numbered sequentially and given the name Detailed Report - 01.
Detailed Report Log File Table A.1 Sections of the Detailed Report Log File Report Section Description Report header Identifies the version of the Feature Pack and the date and time when the report was generated. Storage Group Identifies the locations of transaction logs, system files, and database stores for an Exchange storage group. The report includes a separate section for each storage group on the Exchange server.
Detailed Report Log File Current AD Location contains the mapped drive version of the UNC path, which Exchange uses. For example, remotely stored Exchange transaction logs with the UNC path \\storageserver01\Exchange_TLOGS might have an AD location of S:\{storageserver01.0}, where S: is the local drive letter mapped for Exchange shares on Windows Storage Server computers and {storageserver01.
Detailed Report Log File Store Each “Store” section reports the configuration of the database files in a store. The configuration of the database (.edb) file is listed separately from the configuration of the streaming database (.stm) file. Because the remote storage tools move the .edb and .stm files for a store to the same destination at the same time, the current configuration of any databases that have been moved by using one of the tools should be identical, except for the file names.
Detailed Report Log File the remote storage of Exchange files on Windows Storage Server computers. DFS Root The “DFS Root” section identifies the DFS root folder and root name that Exchange is using. Item Description DFS Root Folder The folder that is hosting the stand-alone DFS root on the Exchange server. This will be the absolute path of %ProgramFiles%\Windows Storage Server\Exchange\DFS. Note: Do not move, rename, or remove this folder at any time. DFS Root Name The name of the DFS root.
Detailed Report Log File WSSExchMapSvc The “WSSExchMapSvc” section indicates the status and run mode of Windows Storage Server Mapping Service, a service that creates the mapped drives and link targets that Exchange uses to recognize Exchange storage groups that are stored on Windows Storage Server computers. Item Description Current Status The current status of Windows Storage Server Mapping Service: Running, Stopped, or Unknown.
Detailed Report Log File Feature Pack Deployment Guide 70
APPENDIX B Additional Resources This appendix lists additional resources that may be helpful when working with the Microsoft Windows Storage Server 2003 Feature Pack.
Additional Resources Installing the Feature Pack For detailed instructions for installing the Feature Pack on the Windows Storage server computer and the Exchange server, see the Microsoft Windows Storage Server 2003 Feature Pack Installation Guide, located in %ProgramFiles%\Windows Storage Server\Exchange\Installation_Guide.doc.
Additional Resources For more information about offline backup and restore processes, see Microsoft Knowledge Base article 296788, “Offline Backup and Restoration Procedures for Exchange” (http://go.microsoft.com/fwlink/?LinkId=23509). Testing Performance of the Exchange Server For more information about LoadSim or to download the tool, see Microsoft Exchange 2003: Load Simulator 2003 on the Microsoft Download Center website (http://go.microsoft.com/fwlink/?LinkId=23364).
