Table of Contents Preface.................................................... 1 Introduction............................................................. 1 High Availability......................................................... 2 Users................................................................... 4 Other Resources.......................................................... 5 Conventions............................................................. 5 Migrating Microsoft Server Logs and Databases.......... 6 Assumptions............................................................. 6 Migrating Microsoft Logs and Database from the Microsoft Server 7 Granting Permissions to the New Locations of the Database and Log Files.......... 8 i
Section 1 Preface Introduction This guide provides the information needed to move Microsoft 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 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 Server, it allows the system administrator to optimize performance by segregating the Microsoft data onto two physical storage devices. The Microsoft 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 Before Deploying an IP SAN Users 10/100 Ethernet Servers Direct Attached Storage (RAID Level 5) with Databases Direct Attached Storage (RAID Level 0+1) with Transaction Logs 1
Preface Figure 2: Microsoft configuration after deploying an IP SAN Users 10/100/1000 Ethernet Transaction Log Server Database Server Gigabit Ethernet Switch Logical Volume with Database Logical Volume with Transaction Logs Storage Concentrator FailOver Cluster Storage Arrays This guide discusses the steps necessary to migrate existing Microsoft 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 implementations. Here are a few options to consider when building your IP SAN. Disk-to-Disk Backup Technology that creates an independent storage resource, such as a Storage Concentrator, enables sophisticated backup procedures such as disk-to-disk backup and restore. Disk-based backup reduces backup windows by copying from multiple 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. StoneFly Networks Migrating Microsoft Server Data to a Storage Concentrator 2
Preface 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 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. Servers Storage Concentrator FailOver Cluster Ethernet Switches Provisioned Volumes Figure 3: A Storage Concentrator FailOver Cluster RAID Array 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 StoneFly Networks Migrating Microsoft Server Data to a Storage Concentrator 3
Preface environment. For example, building A can keep 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. Storage Concentrator Remote Site With IP SAN Ethernet LAN/MAN/WAN Servers Replicated Volumes Storage Concentrator FailOver Cluster Gigabit Ethernet Switch Local Provisioned Volumes RAID Array Figure 4: 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 software terminology Microsoft system administration Storage Concentrator volume administration StoneFly Networks Migrating Microsoft Server Data to a Storage Concentrator 4
Preface Other Resources Find other useful information regarding migrating your Microsoft 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 Conventions Microsoft Knowledge Base Article Q257184: http://support.microsoft.com/default.aspx?scid=kb;en- US;q257184 The following tables list the conventions used throughout this guide: Icons Icon Type Description Note Special instructions or information Text Convention Boldface word Type or Enter Description An action is required Input the requested information StoneFly Networks Migrating Microsoft Server Data to a Storage Concentrator 5
Section 2 Migrating Microsoft Server Logs and Databases This section provides instructions for migrating Microsoft Server logs and databases to an IP SAN managed by one or more Storage Concentrators. Assumptions Microsoft data is best migrated using the Microsoft System Manager to move the database and log files to IP SAN volumes managed by the Storage Concentrator. 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. RAID levels are configured at the storage subsystem level, and not through the Storage Concentrator. 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 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. 6
Migrating Microsoft Server Logs and Databases Migrating Microsoft Logs and Database from the Microsoft 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 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. For best performance, it is recommended that you move both the Mailbox and the Public Folder Store. 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 StoneFly Networks Migrating Microsoft Server Data to a Storage Concentrator IP SAN 7
Migrating Microsoft Server Logs and Databases Microsoft database (.edb file), the Microsoft streaming database (.stm file), or both databases. 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. When the databases are finished migrating, a dialog box appears indicating that the databases have been successfully mounted. If the databases do not automatically remount, manually remount the databases. Granting Permissions to the New Locations of the Database and Log Files 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 data storage. 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 The root drive of the database and log directories may need the following permission: System: Full Control. StoneFly Networks Migrating Microsoft Server Data to a Storage Concentrator IP SAN 8
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