RE: Added disk resource, now cannot fail over to other cluster
- From: JYoung <JYoung@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 16 Jul 2008 08:42:02 -0700
Thanks, that is what I ended up doing (minus the reboots) and it seems to be
working fine.
Thanks for all of your help.
"Mark" wrote:
That is where your problem came from, both servers cannot configure the disk..
the sequence should have been, present the LUN to Server1, format it and
give it a letter on Server1 only, then in cluster Administrator on Server1
create a new cluster group, bring it online, create a physical disk resource
in the new group for the new disk and bring it online. Now, have the SAN LUN
presented to Server2, you may need to do a rescan in Disk Management. Do not
do any disk configuration for this LUN on Server2. Once you see the new disk
on Server2, go into Cluster Admin and move the resource group to Server2.
Please note that the server that does not currently own the disk resource,
that disk will be unavailable in both Explorer and Disk Management, this is
normal cluster disk behavior. What you may have to do in your current
configuration is delete what you have done in Cluster Admin, have the SAN LUN
uppresented from both Server1 and Server2, delete the disk in Disk
Management, reboot both servers and start over, one at a time.
Hope that clears it up a little,
Mark
--
Mark
"JYoung" wrote:
Think this may be where I am misunderstanding the instructions...
What I THOUGHT I needed to do was to create the drive on the 1st node,
confirm it works then create it on the second. I THEN created the disk
resource. Should I have created the resource before creating the physical
Partition (Don't think I can) or create the partition on the 1st server,
create the resource disk, then bring it up on the other node and then create
it as a physical? This seems to make sense...
Thanks for you help.
"Mark" wrote:
The problem is that you created the disk on both nodes before you created the
cluster resource, remember MS clustering is a shared nothing configuration,
only one cluster node at any one time can "own" the disk. What you should
have done was create the SAN LUN and present it to only one cluster node.
Then, go to the cluster node and create a physical disk resource in cluster
administrator, preferably create a new group, dont put it in the default
cluster group. Then bring the physical disk cluster resource online. Once
it is online, now present the same SAN LUN to cluster server2, you may need
to do a rescan in Disk Management. Now you should be able to move the
resource to cluster server2. You should delete what you created and
unpresent the LUN and start fresh.
Hope that helps,
Mark
--
Mark
"JYoung" wrote:
So here is what I did:
Created new drive in SAN at allocated to Cluster group.
Cluster Server 1 – used wizard to set up new drive as basic. Gave it a drive
letter and a name.
Cluster Server 2 – did the same as with Cluster server 1.
In cluster resource group – added new disk as a disk resource.
When I attempt to fail the resources over to the other server
(active-active) they fail on the disk and go back to the one they started
from.
When I shut down the group the drive shows in disk manager on both servers,
and can be read on the server that it was mounted on, but not by the other
server.
What are my options? I tried to simply remove the disk from the group, but
if I do that it wants to remove everything else also. Should I do that and
re-create them?
ANY help would be greatly appriciated.
- References:
- Prev by Date: RE: Added disk resource, now cannot fail over to other cluster
- Next by Date: Clustered Print Server
- Previous by thread: RE: Added disk resource, now cannot fail over to other cluster
- Next by thread: Re: Added disk resource, now cannot fail over to other cluster
- Index(es):
Relevant Pages
|
