Running low on drive letters on the Windows server? Tired of splitting tons of semi-related data between separate drives or of having to deal with folder-by-folder permissions? Of reinstalling the OS when the primary partition gets full?

…think like a UNIX admin and use Windows mounted drives to create a heirachical tree of drives. It’s simple, no more drive letters to remember or map in a startup script. Just create one lettered drive and then map each type of data, NAS device, or however else you want to segment it, to a folder in that one drive. No need for expensive LUN-aggregation software, just use the Disk Management tools in Windows. It’s even possible to migrate all the data in C:\Program Files\ to a NAS device and then use a mounted drive to make the Windows-OS see the NAS as that “Program Files” folder. Having some performance issues with Exchange or SQL Server? You can use move or add a mounted drive to a separate NAS device to separate the log and database files for both server systems.

1. Open the Computer Management control panel, then the Disk Management sub-panel.
2. Right-click the volume you want to mount and choose “Change Drive Letter and Paths”
3. Click Add, select Mount in the following empty NTFS folder and then choose one of the following options:
   • Already have a folder created: type the path to an empty folder in an NTFS-formatted volume or Browse to it
   • No empty folder created yet: click Browse and find where you’d like to place the new folder, then click New Folder and create away

Drive Number Limits: Technically you can have an unlimited number of drives when they’re mapped to folder names instead of drive letters. In reality, approaching 100 separate mounted drives can start to bog down most stock 1U or 2U servers. More RAM and a faster OS-drive (C: drive) are needed to optimize support many more mounted drives.

Article tagged: Windows, Server, NAS, SAN, drive+letters, mapped, mounted, drives, extend, add, migrate, data, compress+drive, SQL+Server, Exchange, separate, database, log, files, performance

Comment on this post below

You can leave a response, or trackback from your own site.