To configure your Exchange data store for SnapManager 3.1 for Microsoft Exchange, complete the following steps.
Note
The windows shown in this procedure are for the Exchange 2000 or 2003 version of SnapManager. If you are using Exchange 5.5, some of the text you see is slightly different. However, the actions you take to perform these steps are the same.
| 1 |
In the Windows user interface, click Start > Programs > SnapManager for Microsoft Exchange. Caution Note ResultSnapManager is launched, and the Connect to Exchange Server window is displayed. |
| 2 |
In the Connect to Exchange Server window, select the Exchange server you want this instance of SnapManager to manage and click OK. |
| 3 |
If the Configuration Wizard is not already started, click the Configuration Wizard button to start it now. |
| 4 |
Click Next on the Welcome window to begin the configuration. ResultThe Database Verification Server window appears. |
| 5 |
In the Database Verification Server window, enter or browse to the computer to be used for database verification, then click Next. If the computer used for database verification does not have Exchange installed, you must put the necessary files on it. For details, see Remote verification. Note |
| 6 |
On the Exchange Server to Configure window, click Next to confirm the server to be configured. ResultThe Where to Move Databases window is displayed. |
| 7 |
In the Where to Move Databases window, associate your Exchange storage groups (Stores) or databases with the correct LUNs according to your SnapManager data configuration plan. For more information about using this window, see Moving databases using the Configuration Wizard. After you associate all databases with a LUN, click Next. Example:In the following example, the SG2 storage group has already been associated with LUN S. When you click the move (<=>) button, the First Storage Group is associated with LUN T, and you can proceed to the next window.
|
| 8 |
In the Where to Move Transaction Logs window, associate your transaction logs with the correct LUNs according to your SnapManager data configuration plan. For more information about using this window, see Moving transaction logs using the Configuration Wizard. After you associate all transaction logs with a LUN, click Next. Example:In the following example, the transaction logs for the First Storage Group have been associated with LUN L. When you click the move (<=>) button, the transaction logs for SG2 will be associated with LUN L also, and you can proceed to the next window.
|
| 9 |
In the Where to Move SMTP and MTA System Files window, determine the location of your SMTP and MTA system files. Note For more information about using this window, see About the SMTP and MTA queue location. After you determine the location of all listed system files, click Next. |
| 10 |
In the Where to Put the SnapInfo Directory window, select the SnapInfo files and the LUN to move them to, then click the move (<=>) button and click Next. |
| 11 |
If you are installing SnapManager on a stand-alone system that has the Microsoft iSCSI initiator installed, select whether you want to configure your Microsoft iSCSI service as a dependency for the Microsoft Exchange System Attendant, and click Next. Note |
| 12 |
In the Configure Automatic Event Notification window, you can configure SnapManager to notify a designated recipient, or NetApp, when problems occur. After you configure your event notification, click Next. Note For information about configuring e-mail notification, see Configuring e-mail notification. For information about configuring Autosupport, see Configuring filer SysLog and Autosupport. |
| 13 |
Review the configuration summary in the Completing the Configuration Wizard window. If the configuration summary is satisfactory, click Finish to display a list of tasks the Configuration Wizard performs, based on the configuration information you specified. ResultThe SnapManager Configuration Wizard displays the task list to be used. |
| 14 |
Click Start Now to migrate your databases and their transaction logs and SnapInfo files to the LUNs you specified. ResultThe SnapManager Configuration Wizard moves the databases and transaction logs to their specified LUNs and displays a task check-off list. Note |
| 15 |
Create a SnapManager backup immediately. For information about creating a SnapManager backup, see Backing Up with SnapManager Backup. |
TheSnapManager 3.1 for Microsoft Exchange Configuration Wizard enables you to choose which LUNs will store your Exchange databases when you complete the wizard. You use the Where to Move Databases window to perform these tasks:
For details, see Moving storage groups to a LUN.
For details, see Moving individual databases to a LUN.
For details, see Changing the location of a storage group or database.
For details, see Viewing the full path for your database files.
Note
The list of available drives changes as you make choices that rule out other choices.
To put an entire storage group on a single LUN, complete the following steps.
To move an individual database to a LUN, complete the following steps.
To change the location of a storage group you already associated with a LUN or local disk, complete the following step.
To view the full path for your database or storage group files, complete the following steps.
The SnapManager 3.1 for Microsoft Exchange Configuration Wizard enables you to choose which LUNs will store your Exchange transaction logs when you complete the wizard. You use the Where to Move Transaction Logs window to perform these tasks:
For details, see Moving transaction logs to a LUN.
For details, see Changing the location of a transaction log files.
For details, see Viewing the full path for your transaction log files.
Note
The list of available drives changes as you make choices that rule out other choices.
To put the transaction logs for a storage group on a disk, complete the following steps.
To change the location of transaction log files you already associated with a LUN, complete the following step.
To view the full path for your transaction log files, complete the following step.
The SMTP and MTA queues are used by Exchange. Usually, the location of these files does not matter, as long as they do not reside on the same LUN as the Exchange databases.
For stand-alone systems, the SMTP and MTA system files can be placed on any disk or LUN that does not contain Exchange databases (the default location of the original local installation disk is acceptable). For Windows clusters, they must be moved to a shared LUN that does not contain Exchange databases.
Copyright © 1994-2004, Network Appliance, Inc. All rights
reserved.
Part No. 215-00858
File: config3.htm
Last updated: Tue Jun 15 15:34:08 2004