Re: What drives should you "see" in Explorer?

Tech-Archive recommends: Fix windows errors by optimizing your registry



This is true, but one useful technique if you just need to browse the drive
from explorer, assuming the physical drive is owned by a virtual server, and
you're logged on as a user with administrative privileges, is to map to the
admin share of that drive on that virtual server.

That is, if NodeA is the active member of the cluster controlling VirtServA
(IP: 192.168.10.11) with disk R, from the passive NodeB, in the Explorer
address bar just type the following:

\\VirtServA\R$

OR

\\192.168.10.11\R$


Of course, this assumes you're not blocking the necessary sharing ports.

"Todd J Heron" wrote:

> MU,
>
> Mike has sent you the article explaining this behavior. I will explain it
> also in plain terms. What you are experiencing is normal cluster behavior.
> Only the active node can access a shared physical disk. Theoretically, if
> more than one disk (shared resource) owner at a time tried to access the
> data at one time, corruption could result therefore this is not allowed
> (this is called a shared-nothing model). Windows Explorer on the passive
> node may or may not "see" resources owned by an active node. If a passive
> node does see a disk which an active node currently owns, this means the
> passive node at one time owned the disk and is simply "remembering" it, but
> when you click on the drive letter you get an error message. Same
> phenomenon occurs with Disk Management MMC. In summary, disk drive letters
> a passive node sees but which an active node controls is actually a bit of
> an illusion because the passive node cannot access a disk controlled by an
> active node node.
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights.
>
>
.



Relevant Pages

  • Re: Shared Storage question
    ... > can access a shared physical disk. ... Windows Explorer on the passive node may or may not ... > "see" resources owned by an active node. ... > Managing Disk Ownership in a Windows Server 2003 Cluster: ...
    (microsoft.public.windows.server.clustering)
  • Re: Cluster service fails after Windows Update
    ... Can you uninstall the patches on your passive node? ... Server 2003) and following reboot the cluster service on that node ... The event log explains the problem as being that "The disk associated ... The currently active node is functioning fine, ...
    (microsoft.public.windows.server.clustering)
  • Re: What drives should you "see" in Explorer?
    ... What you are experiencing is normal cluster behavior. ... Only the active node can access a shared physical disk. ... passive node at one time owned the disk and is simply "remembering" it, ...
    (microsoft.public.windows.server.clustering)
  • Re: add new disk
    ... Well, what you could do, to not cause a service interruption, would be to only assign the LUN to the passive node, reboot that node, configure your cluster disk resource in the resource group, ensure the disk comes online, and then expose the LUN to the active node, fail the resources over to the passive node and reboot the active node, test failover of the new disk, configure your remaining resources. ...
    (microsoft.public.windows.server.clustering)
  • Re: Windows explorer and the swap file.
    ... I am installing it right now on another disk, ... My clients run dozens of Windows XP machines. ... *** They have no problem at all with Explorer. ... *** It's your installation that's the problem, ...
    (microsoft.public.windowsxp.general)