Scenario: migrating an existing configuration from using drive letters to using mountpoints for LUN mapping

You can migrate an existing configuration that uses drive letters to map to Data ONTAP LUNs, to a new configuration that uses volume mountpoints instead. In this scenario, the migration process is described using a sample configuration.

About this task

The sample configuration contains the following components:

A single Storage Group
A single database located on LUN I:\

This scenario assumes the following points:

The Exchange transaction logs, MTA and SMTP system files, and the SnapManager SnapInfo directory are collocated on LUN L:\.
The mountpoint root LUN requires a drive letter, and the LUN containing the transaction logs is used as the mountpoint root.
Double-clicking the mountpoint (directory) name takes you to the root of the mounted LUN rather than to an empty directory on the mountpoint root LUN.
The original drive letter mapping, I:\, should not be removed until after you verify that the LUN mappings have been created successfully.
For the Configuration wizard to function properly, SnapManager requires that the original drive letter mappings be in place along with the newly added mountpoints. Unneeded mappings are removed later.

Steps

Launch Windows Explorer, and then browse to the root of the transaction logs, LUN L:\.
For example, create a directory named database under L:\.
Use a directory database.
Launch the SnapDrive MMC, right-click the database LUN I:\, and then select Change Drive Letter and Paths.
In Change Drive Letter and Paths, click Add.
When prompted, enter the path to the appropriate directory on your mountpoint root LUN, L:\database
Verify that the additional LUN mappings are successfully created and reflected in the SnapDrive MMC.
In this example, the LUNs show drive letters of L:\ and L:\database\.

You can also browse to the root of the mountpoint root LUN, drive L:\. The icon for the folder database changes from the standard Windows folder icon to the Windows icon representing a mountpoint.
Launch SnapManager, and then run the Configuration wizard.
In the Welcome window, click Next.
In the Database Verification Server window, click Next.
Although changes can be made here if desired, doing so is not part of this example.
In the Exchange Server to Configure window, verify that you are about to configure the correct server, and then click Next.
In the Select a Storage Group/Database to move to a LUN window, do the following: a. b. c.
1. Select a Storage Group listed in the Database Location Results field, and then click Reconfigure.
  The Storage Group appears in the list of unconfigured databases, and you can reassociate it with any available disk.
2. Select LUN L:\database\, and then click <=> to associate the database with the new path.
  The Storage Group appears in the Database Location Results field again. The old drive letter LUN I appears under the From column. The new mountpoint path L:\database\:appears under the To column.
3. Click Next.
Keep clicking Next to proceed through the next few windows, making additional configuration changes if desired. At the final window, click Finish.
The Configurator Status window appears.
Click Start Now.
The databases are taken offline, and the migration proceeds.
After the SnapManager Configuration wizard completes successfully, return to the SnapDrive MMC.
Using the SnapDrive MMC, right-click the database LUN I:\, and then select Change Drive Letter and Paths.
In Change Drive Letter and Paths, highlight the original drive letter for the database LUN (I:\) and click Remove.
The SnapDrive MMC displays the two LUNs L:\ and L:\database.