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. The migration process uses SnapDrive and SnapManager.
This method briefly takes the affected Storage Groups offline as their paths are changed. You do not need to copy the databases themselves from one LUN to another. You save time, and Storage Groups go offline for less time.
Note: A drive letter is used for the mountpoint root volume and not all drive letters are eliminated.
The mountpoint root can be any of the following:
- The local C:\ drive
- The LUN that stores the transaction log files
- A separate dedicated LUN
The best practice is to use the LUN that stores the transaction log files. Using a separate LUN as the mountpoint root adds an additional point of failure to the Exchange server.
Note: In clustered configurations, the mountpoint root must reside on a shared storage device such as the transaction logs LUN.
For configurations using more than one Storage Group, use one LUN with a drive letter for the transaction logs of each Storage Group.
Because the System Attendant cluster resources require dependencies on the physical disk cluster resources in clustered configurations, the entire Exchange virtual server is brought offline during a migration even if only a single Storage Group is migrated. Taking the physical disk resource for the transaction logs offline for one Storage Group takes the System Attendant resource offline and with all other Storage Groups.
