RE: Drive mappings on clustered servers

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi,

It sounds like the problem you're experiencing occurs, because drive letter
mapping for the home folder succeeds and causes a conflict with the drive
letter mapping for the physical disk. Therefore, the storage device loses
the drive letter and causes the failure of the physical disk resource to
occur. On a stand-alone server, similar behavior may occur if a home folder
mapping conflicts with the drive letter mapping of a storage device. In
this scenario, the storage device loses the drive letter assignment and the
home folder mapping succeeds; the storage device becomes inaccessible. If
the physical disk resource is the quorum resource, the Cluster service may
stop working.

To work around this problem, avoid the drive letter mapping conflict by
selecting drive letters for the physical disk resources that do not
conflict with the automatic mapping for home folders. When you map a drive
manually, the operating system only offers unused drive letters for
selection.

NOTE: On a Windows Clustering server, drive letters may be listed as
available even when they are already mapped to drives by another node in
the cluster.

To resolve this problem, and to guarantee the highly available status of
clustered systems, review the following articles to ensure nothing is being
missed.

224967 How to create file shares on a cluster
http://support.microsoft.com/?id=224967

256926 Implementing Home Folders on a Server Cluster
http://support.microsoft.com/?id=256926

318534 Best Practices for Drive-Letter Assignments on a Server Cluster
http://support.microsoft.com/?id=318534

--------------------
Hope this helps,
Mike Rosado
Windows 2000 MCSE + MCDBA
Microsoft Enterprise Platform Support
Windows NT/2000/2003 Cluster Technologies

====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
<http://www.microsoft.com/info/cpyright.htm>

-----Original Message-----
> From: <idontknow@xxxxxxxxxxxxxxxxx>
> Subject: Drive mappings on clustered servers
> Date: Fri, 25 Nov 2005 16:34:02 -0800
>
> After rebooting the clustered servers the 5 folder mappings have to be
> recreated. What is the correct way to set them up so they will remain
after a
> reboot?
>
>

.

Relevant Pages

  • RE: Drive mappings on clustered servers
    ... the information you gave me is what I needed to redo the folder share ... > It sounds like the problem you're experiencing occurs, because drive letter ... > letter mapping for the physical disk. ... > the physical disk resource is the quorum resource, the Cluster service may ...
    (microsoft.public.windows.server.clustering)
  • Kindof Update
    ... since I think all the home folder is really doing for everything aside ... from server 2003 TS is mapping the drive letter I mapped it with the ... What is home folder used for aside from this 2003 thing and mapping the ...
    (microsoft.public.win2000.termserv.apps)
  • Re: N+1 Configuration
    ... Server would try and start before the Tempdb mount point came fully online. ... different from using a drive letter, in which case the SQL Server resource ... The current cluster is Active/Passive. ...
    (microsoft.public.sqlserver.clustering)
  • Re: N+1 Configuration
    ... Every clustered instance will require it's own drive letter but off that you ... can hang a bunch of mount points. ... How to configure volume mount points on a Microsoft Cluster Server ...
    (microsoft.public.sqlserver.clustering)
  • Re: N+1 Configuration
    ... I'm all straight on using mount points and now only a single root LUN ... The current cluster is Active/Passive. ... I'm adding a new third server that has four LUNS presented to only it so far ... two instances of SQL can be using the same drive letter though (even if, ...
    (microsoft.public.sqlserver.clustering)