What the SnapManager Configuration wizard does

The Configuration wizard enables you to move your Exchange data in the following ways—from local disk to LUN, from LUN to LUN, or from LUN to local disk.

From local disk to LUN

If you want to move Exchange databases, you can use the wizard to unmount the mailbox databases or the Exchange databases in a Storage Group, move the Exchange databases and transaction log files to the selected LUN, and remount the databases.

Note: SnapManager takes Exchange databases offline during the transfer operation.

The wizard creates a SnapInfo directory that SnapManager uses to store information about the backup sets and the backed up transaction logs.

The wizard disables circular logging for all mailbox databases and Storage Groups that are moved to a LUN, to enable up-to-the-minute restoring of those Storage Groups and mailbox databases.

The wizard also guides you through several application settings. These settings include enabling notification of SnapManager events using e-mail, Syslog, or the AutoSupport feature.

From LUN to LUN

Resource management issues might require LUN-to-LUN transfer of Exchange data. An example of a situation that requires a LUN-to-LUN transfer is when you want to consolidate the Exchange data on another storage system.

From LUN to local disk

You need to move Exchange data from a LUN to a local disk if the data is no longer managed by using SnapManager. However, Microsoft Cluster Services configurations do not support Exchange data transfer from LUN to local disk.

Note: Protection Manager integration can be enabled without reinstalling SnapManager for Exchange anytime by rerunning the Configuration wizard. You must first ensure that you have configured SnapDrive for Protection Manager integration. If you have not already done so, you can set up SnapDrive Protection Manager integration via the sdcli command, and then restart the SnapDrive service, or you can rerun the SnapDrive setup. (See the SnapDrive help for more information on Protection Manager integration.)

Note: Ensure that all databases in a Storage Group are migrated to LUNs from a local disk. SnapManager does not support heterogeneous configuration. An example of a heterogeneous configuration is Storage Groups with some databases that reside on LUNs, and some on a local disk. Exchange databases must reside on NetApp LUNs to enable SnapManager to back up.