i
Table of Contents
Preface . . . 1
Introduction . . . 1
High Availability . . . 2
Users . . . 4
Other Resources . . . 5
Conventions . . . 5
Migrating Microsoft Exchange Server Logs and Databases . . . 6
Assumptions . . . 6
Migrating Microsoft Exchange Logs and Database from the Microsoft Exchange Server 7 Granting Permissions to the New Locations of the Database and Log Files . . . 8
1
Section 1 Preface
Introduction
This guide provides the information needed to move Microsoft Exchange Server logs and databases to storage resources
managedby StoneFly Network’s IP Storage Area Network (IP SAN) solution, the Storage Concentrator ™.
IP SANs provide substantial benefits when combined with a Microsoft Exchange™ Server, including increased reliability through support of clustered configurations, increased efficiency through centralizing storage resources, and reduced complexity in adding additional storage resources when required. An IP SAN, in contrast to a Fibre Channel SAN, offers the added benefits of using existing Ethernet resources, including cabling, equipment, trained staff, and reduced component cost due to the ubiquitous Ethernet networking technology.
When the Storage Concentrator is coupled with the Microsoft Exchange™ Server, it allows the system administrator to optimize performance by segregating the Microsoft Exchange data onto two physical storage devices. The Microsoft Exchange Server databases and mailboxes are placed on a storage device that is optimized for random access, while transaction logs are placed on a storage device that is optimized for sequential access. Figures 1 and 2 illustrate the configuration before and after deploying an IP SAN.
Figure 1: Microsoft Exchange Before Deploying an IP SAN
Exchange Servers Exchange Users 10/100 Ethernet
Direct Attached Storage (RAID Level 0+1) with Exchange Transaction Logs Direct Attached Storage
(RAID Level 5) with Exchange Databases
Preface
StoneFly Networks Migrating Microsoft Exchange Server Data to a Storage Concentrator 2 Figure 2: Microsoft Exchange configuration after deploying an IP SAN
This guide discusses the steps necessary to migrate existing Microsoft Exchange logs and databases to an IP SAN managed by StoneFly Network’s Storage Concentrator.
High Availability
Building an element of high availability is important, even in small Exchange implementations. Here are a few options to consider when building your Exchange IP SAN.
Disk-to-Disk Backup
Technology that creates an independent storage resource, such as a Storage Concentrator, enables sophisticated Exchange backup procedures such as disk-to-disk backup and restore. Disk-based backup reduces backup windows by copying from multiple Exchange servers simultaneously onto the dedicated IP SAN, slashing backup times. Disk-to-disk backup, which would significantly impact a directly attached server, provides a high level of data protection and the fastest recovery.
10/100/1000 Ethernet
Gigabit Ethernet Switch
Storage Concentrator FailOver Cluster Exchange Transaction Log Server Exchange Users
Logical Volume with Transaction Logs Exchange
Database Server
Logical Volume with Exchange Database
Storage Arrays
Preface
StoneFly Networks Migrating Microsoft Exchange Server Data to a Storage Concentrator 3
Logical volume management allows an administrator to create a separate "volume" for each server, which to the server appears as a locally attached disk. Volumes can be created Daily or even more often, if required. Common backup application software supports IP SANs, automating and simplifying the backup process. Once disk backup is complete, an archival copy can be sent to tape as a background activity.
FailOver Clustering
Storage Concentrators can be set up in clustered configurations. If a substantial failure takes down an individual Storage Concentrator, FailOver to a standby Storage Concentrator will occur automatically to ensure continuous access to the Microsoft Exchange data store.
Currently, a Storage Concentrator FailOver Cluster consists of two units---one is active and one is on standby. A cluster appears as a single entity to hosts on the network.
Figure 3: A Storage Concentrator FailOver Cluster
Replication
Mirroring provides a technique for creating and maintaining identical data sets on different physical IP SANs for data migration to a new SAN or replication for disaster recovery planning. If a disk fails within a mirror, it will have an identical set in a separate IP SAN.
• Local (synchronous) mirroring is performed between a host and a Storage Concentrator volume or between two or more Storage Concentrator-based IP SANs within the same storage
ArrayRAID Exchange
Servers
Storage Concentrator FailOver Cluster
Ethernet
Switches Provisioned Exchange
Volumes
Preface
StoneFly Networks Migrating Microsoft Exchange Server Data to a Storage Concentrator 4
environment. For example, building A can keep Exchange Databases in an IP SAN synchronized with a separate IP SAN in building B.
• Remote (asynchronous) mirroring is performed between two or more IP SANs in separate (remote) storage environments across a WAN connection. The remote site typically acts as a disaster recover configuration for the primary location.
Figure 4: Exchange Volumes Replicated to a Remote Site
Users
This guide is intended to be used by network administrators and assumes a basic understanding of:
• Local area networks (LAN)
• Ethernet and Ethernet-switching concepts
• Storage area networking (SAN)
• Microsoft Exchange software terminology
• Microsoft Exchange system administration
• Storage Concentrator volume administration
Local Provisioned
Exchange Volumes Exchange
Servers
Storage Concentrator FailOver Cluster
RAIDArray Storage Concentrator
Ethernet LAN/MAN/WAN
Gigabit Ethernet
Switch
Remote Site With IP SAN
Replicated Exchange Volumes
Preface
StoneFly Networks Migrating Microsoft Exchange Server Data to a Storage Concentrator 5
Other Resources
Find other useful information regarding migrating your Microsoft Exchange databases to the Storage Concentrator in the following documents and Web sites:
• The Storage Concentrator User’s Guide
• The Storage Concentrator Setup Guide
• The StoneFly Networks Web site: www.stonefly.com/support
• The Storage Concentrator Online Help in the administrative interface (following initial setup)
• Microsoft Support: www.microsoft.com/technet/exchange
• Microsoft Knowledge Base Article Q257184:
http://support.microsoft.com/default.aspx?scid=kb;EN- US;q257184
Conventions
The following tables list the conventions used throughout this guide:
Icons
Text
Icon Type Description
Note Special instructions or information
Convention Description
Boldface word An action is required
Type or Enter Input the requested information
6
Section 2 Migrating Microsoft
Exchange Server Logs and
Databases
This section provides instructions for migrating Microsoft Exchange Server logs and databases to an IP SAN managed by one or more Storage Concentrators .
Microsoft Exchange data is best migrated using the Microsoft Exchange System Manager to move the database and log files to IP SAN volumes managed by the Storage Concentrator.
Assumptions
It is assumed that the following conditions exist before proceeding:
• On the drives managed by the Storage Concentrator , the appropriate RAID levels have been configured.
• For fastest sequential access, RAID 0+1 is recommended for the drive where the transaction logs are located.
• To achieve a balance between data protection, integrity and cost, Microsoft recommends RAID 5 for the drive where the database files are located.
• Provisioned logical volumes for the transaction logs and databases have been created on storage volumes managed by the Storage Concentrator. For more information on creating provisioned volumes, see Section 2 of the Storage Concentrator User’s Guide .
• Two volumes are recommended for each Microsoft Exchange storage group: one for the transaction logs on a drive that is configured at RAID 0+1 and one for the database files on a drive configured at RAID 5.
RAID levels are configured at the storage subsystem level, and not through the Storage Concentrator .
Migrating Microsoft Exchange Server Logs and Databases
StoneFly Networks Migrating Microsoft Exchange Server Data to a Storage Concentrator IP SAN 7
Migrating Microsoft Exchange Logs and Database from
the Microsoft Exchange Server
This process changes the path and automatically moves the log and database files to new locations on devices managed by the Storage Concentrator .
During the process of migrating log files and databases, your store of logs and databases are inaccessible to users until the databases are remounted at the completion of the process.
To move log files:
1 Start the Microsoft Exchange System Manager.
2 Locate the administrative group.
3 Expand the servers container.
4 Expand the container of the server you want to modify.
5 Open the properties on the storage group for which you want to change log file paths.
6 On the General tab, click Browse to change the Transaction Log Location . Specify the location for the log files on the volume that was created by the Storage Concentrator . 7 Cl,ose the storage group properties dialog box.
To move databases:
1 Expand the storage group container.
2 Click the Mailbox or Public Folder Store that you want to move.
3 Open the properties on the selected store, and click the Database tab.
4 Click Browse to select the location for the database files that was created by the Storage Concentrator . You can move the
For best performance, it is recommended that you move both the Mailbox and the Public Folder Store.
Migrating Microsoft Exchange Server Logs and Databases
StoneFly Networks Migrating Microsoft Exchange Server Data to a Storage Concentrator IP SAN 8
Microsoft Exchange database (.edb file), the Microsoft Exchange streaming database (.stm file), or both databases.
When the databases are finished migrating, a dialog box appears indicating that the databases have been successfully mounted.
Granting Permissions to the New Locations of the
Database and Log Files
Once the logs and database files have been moved, the following default permissions must be granted to the new directories where the database and log files reside:
• Administrators: Full Control
• Authenticated Users: Read and Execute, List Folder Contents, Read
• Creator Owner: None
• Server Operators: Modify, Read and Execute, List Folder Contents, Read, Write
• System: Full Control
If the databases are still mounted, you will be automatically prompted to dismount the databases and move the location of the files. Click Yes to continue.
If the databases do not automatically remount, manually remount the databases.
Perform these steps only if you have created a file structure on the provisioned logical volumes that identically matches the file structure of the original Microsoft Exchange data storage.
The root drive of the database and log directories may need the following permission: System: Full Control.
Copyright 2004 StoneFly, Inc.
All rights are reserved. No part of this document may be photocopied or reproduced without the prior written consent of StoneFly, Inc.
The information contained in this document is subject to change without notice. StoneFly, Inc shall not be liable for errors contained herein or for consequential damages in connection with the furnishing, performance, or use of this material.
StoneFly, the StoneFly logo, StoneFusion and Storage Concentrator are property of StoneFly Networks Incorporated.
Other brands and their products are trademarks or registered trademarks of their respective holders.
StoneFly, Inc.
21353 Cabot Boulevard Hayward, CA 94545 Tel: 510-265-1616 Fax: 510.265.1565 www.StoneFly.com www.iSCSI.com
Doc. 100061 Rev.B
