|
|
|
date: Wed, 5 Dec 2007 14:30:54 -0800 (PST),
group: microsoft.public.exchange.clustering
back
Re: MNS with FSW Clustering Problems (E2K7 CCR)
On 6 Dec, 00:44, "Scott Schnoll [MSFT]"
wrote:
> Neither CCR nor the MNS quorum with FSW use physical disk resources (e.g.,
> cluster-managed disks). You need to remove the disk resource from the
> default cluster group (and from any other cluster groups) and configure the
> cluster quorum to use MNS. Seehttp://technet.microsoft.com/en-us/library/bb124038.aspxfor steps to do
> this.
> --
> Regards,
>
> Scott Schnoll
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
>
> "AJ" wrote in message
>
> news:b8b7ce92-9046-4ad9-8c0e-a3511ce309e7@i12g2000prf.googlegroups.com...
>
>
>
> > Hi
> > I'm having a heck of a time deploying CCR. I have done everything
> > correctly as far as I can tell but I've not been able to get the disk
> > groups to move to the other node and get a 1034 error in the event log
> > everytime I try to fail the groups over. The 'cluster group' will
> > failover to the other node without any problems, its just the groups
> > that contain a physical disk resource that won't.
>
> > The event log states the following:
>
> > The disk associated with cluster disk resource 'LUN (D:)' could not be
> > found. The expected signature of the disk was B0C1B79E. If the disk
> > was removed from the server cluster, the resource should be deleted.
> > If the disk was replaced, the resource must be deleted and created
> > again in order to bring the disk online. If the disk has not been
> > removed or replaced, it may be inaccessible at this time because it is
> > reserved by another server cluster node.
>
> > For more information, see Help and Support Center at
> >http://go.microsoft.com/fwlink/events.asp.
>
> > I have tried deleting the physical disk resource and recreating but
> > still no joy. I have checked access to the File Share on the HT server
> > and no problems there either.
>
> > I have come across the same problem on another CCR cluster as well
>
> > The config is 2 servers (HP) each with their own external storage
> > array (HP) SAS drives
> > I carved up the disks on both enclosures exactly the same. Used
> > diskpart to align the disks and formated with NTFS (64K). Created the
> > FSW on one of our HT servers. Configured the MNS to use the FSW etc
> > etc. The OS is Windows Server 2003 SP2 R2.
>
> > As I said before the default cluster group fails over without any
> > problems.
>
> > Anyone offer any help
>
> > Cheers
>
> > AJ- Hide quoted text -
>
> - Show quoted text -
Hi Scott
Thanks for this. I seemed to of missed the small print! also haven't
seen this mentioned anywhere before about removing the physical disk
resource. I'll try again!
Cheers
AJ
date: Thu, 6 Dec 2007 01:18:13 -0800 (PST)
author: AJ
Re: MNS with FSW Clustering Problems (E2K7 CCR)
On 6 Dec, 09:18, AJ wrote:
> On 6 Dec, 00:44, "Scott Schnoll [MSFT]"
>
>
>
>
>
> wrote:
> > Neither CCR nor the MNS quorum with FSW use physical disk resources (e.g.,
> > cluster-managed disks). You need to remove the disk resource from the
> > default cluster group (and from any other cluster groups) and configure the
> > cluster quorum to use MNS. Seehttp://technet.microsoft.com/en-us/library/bb124038.aspxforsteps to do
> > this.
> > --
> > Regards,
>
> > Scott Schnoll
> > Microsoft Corporation
> > This posting is provided "AS IS" with no warranties, and confers no
> > rights. Please do not send email directly to this alias. This alias is for
> > newsgroup purposes only.
>
> > "AJ" wrote in message
>
> >news:b8b7ce92-9046-4ad9-8c0e-a3511ce309e7@i12g2000prf.googlegroups.com...
>
> > > Hi
> > > I'm having a heck of a time deploying CCR. I have done everything
> > > correctly as far as I can tell but I've not been able to get the disk
> > > groups to move to the other node and get a 1034 error in the event log
> > > everytime I try to fail the groups over. The 'cluster group' will
> > > failover to the other node without any problems, its just the groups
> > > that contain a physical disk resource that won't.
>
> > > The event log states the following:
>
> > > The disk associated with cluster disk resource 'LUN (D:)' could not be
> > > found. The expected signature of the disk was B0C1B79E. If the disk
> > > was removed from the server cluster, the resource should be deleted.
> > > If the disk was replaced, the resource must be deleted and created
> > > again in order to bring the disk online. If the disk has not been
> > > removed or replaced, it may be inaccessible at this time because it is
> > > reserved by another server cluster node.
>
> > > For more information, see Help and Support Center at
> > >http://go.microsoft.com/fwlink/events.asp.
>
> > > I have tried deleting the physical disk resource and recreating but
> > > still no joy. I have checked access to the File Share on the HT server
> > > and no problems there either.
>
> > > I have come across the same problem on another CCR cluster as well
>
> > > The config is 2 servers (HP) each with their own external storage
> > > array (HP) SAS drives
> > > I carved up the disks on both enclosures exactly the same. Used
> > > diskpart to align the disks and formated with NTFS (64K). Created the
> > > FSW on one of our HT servers. Configured the MNS to use the FSW etc
> > > etc. The OS is Windows Server 2003 SP2 R2.
>
> > > As I said before the default cluster group fails over without any
> > > problems.
>
> > > Anyone offer any help
>
> > > Cheers
>
> > > AJ- Hide quoted text -
>
> > - Show quoted text -
>
> Hi Scott
>
> Thanks for this. I seemed to of missed the small print! also haven't
> seen this mentioned anywhere before about removing the physical disk
> resource. I'll try again!
>
> Cheers
>
> AJ- Hide quoted text -
>
> - Show quoted text -
You have to remove the physical disks from the second node too after
it joins the cluster. Interesting that this step does not get
mentioned in a number of tutorials out there. I should of thought
about the whole concept and realised you wouldn't have disks failing
over! Anyway thanks for your help and pointing me in the right
direction you have saved me a lot of time!
AJ
date: Thu, 6 Dec 2007 05:33:20 -0800 (PST)
author: AJ
Re: MNS with FSW Clustering Problems (E2K7 CCR)
AJ,
Glad to hear you got it figured out. We do have a note after step 11 on the
page I cited to you that states: "If any physical disk resources are
present, they should be manually removed before adding the second node to
the cluster."
Ideally, you start out with no shared storage so that when you create the
cluster, you don't have shared disks. But after creating the cluster, you
should remove any disk resources before adding the second node.
Hope this helps.
"AJ" wrote in message
news:0893118e-9bab-46e8-af39-edbc2e3decbc@f3g2000hsg.googlegroups.com...
> On 6 Dec, 09:18, AJ wrote:
>> On 6 Dec, 00:44, "Scott Schnoll [MSFT]"
>>
>>
>>
>>
>>
>> wrote:
>> > Neither CCR nor the MNS quorum with FSW use physical disk resources
>> > (e.g.,
>> > cluster-managed disks). You need to remove the disk resource from the
>> > default cluster group (and from any other cluster groups) and configure
>> > the
>> > cluster quorum to use MNS.
>> > Seehttp://technet.microsoft.com/en-us/library/bb124038.aspxforsteps to
>> > do
>> > this.
>> > --
>> > Regards,
>>
>> > Scott Schnoll
>> > Microsoft Corporation
>> > This posting is provided "AS IS" with no warranties, and confers no
>> > rights. Please do not send email directly to this alias. This alias is
>> > for
>> > newsgroup purposes only.
>>
>> > "AJ" wrote in message
>>
>> >news:b8b7ce92-9046-4ad9-8c0e-a3511ce309e7@i12g2000prf.googlegroups.com...
>>
>> > > Hi
>> > > I'm having a heck of a time deploying CCR. I have done everything
>> > > correctly as far as I can tell but I've not been able to get the disk
>> > > groups to move to the other node and get a 1034 error in the event
>> > > log
>> > > everytime I try to fail the groups over. The 'cluster group' will
>> > > failover to the other node without any problems, its just the groups
>> > > that contain a physical disk resource that won't.
>>
>> > > The event log states the following:
>>
>> > > The disk associated with cluster disk resource 'LUN (D:)' could not
>> > > be
>> > > found. The expected signature of the disk was B0C1B79E. If the disk
>> > > was removed from the server cluster, the resource should be deleted.
>> > > If the disk was replaced, the resource must be deleted and created
>> > > again in order to bring the disk online. If the disk has not been
>> > > removed or replaced, it may be inaccessible at this time because it
>> > > is
>> > > reserved by another server cluster node.
>>
>> > > For more information, see Help and Support Center at
>> > >http://go.microsoft.com/fwlink/events.asp.
>>
>> > > I have tried deleting the physical disk resource and recreating but
>> > > still no joy. I have checked access to the File Share on the HT
>> > > server
>> > > and no problems there either.
>>
>> > > I have come across the same problem on another CCR cluster as well
>>
>> > > The config is 2 servers (HP) each with their own external storage
>> > > array (HP) SAS drives
>> > > I carved up the disks on both enclosures exactly the same. Used
>> > > diskpart to align the disks and formated with NTFS (64K). Created the
>> > > FSW on one of our HT servers. Configured the MNS to use the FSW etc
>> > > etc. The OS is Windows Server 2003 SP2 R2.
>>
>> > > As I said before the default cluster group fails over without any
>> > > problems.
>>
>> > > Anyone offer any help
>>
>> > > Cheers
>>
>> > > AJ- Hide quoted text -
>>
>> > - Show quoted text -
>>
>> Hi Scott
>>
>> Thanks for this. I seemed to of missed the small print! also haven't
>> seen this mentioned anywhere before about removing the physical disk
>> resource. I'll try again!
>>
>> Cheers
>>
>> AJ- Hide quoted text -
>>
>> - Show quoted text -
>
> You have to remove the physical disks from the second node too after
> it joins the cluster. Interesting that this step does not get
> mentioned in a number of tutorials out there. I should of thought
> about the whole concept and realised you wouldn't have disks failing
> over! Anyway thanks for your help and pointing me in the right
> direction you have saved me a lot of time!
>
> AJ
date: Thu, 6 Dec 2007 08:23:59 -0800
author: Scott Schnoll [MSFT]
Re: MNS with FSW Clustering Problems (E2K7 CCR)
On 6 Dec, 16:23, "Scott Schnoll [MSFT]"
wrote:
> AJ,
>
> Glad to hear you got it figured out. We do have a note after step 11 on the
> page I cited to you that states: "If any physical disk resources are
> present, they should be manually removed before adding the second node to
> the cluster."
>
> Ideally, you start out with no shared storage so that when you create the
> cluster, you don't have shared disks. But after creating the cluster, you
> should remove any disk resources before adding the second node.
>
> Hope this helps.
>
> "AJ" wrote in message
>
> news:0893118e-9bab-46e8-af39-edbc2e3decbc@f3g2000hsg.googlegroups.com...
>
>
>
> > On 6 Dec, 09:18, AJ wrote:
> >> On 6 Dec, 00:44, "Scott Schnoll [MSFT]"
>
> >> wrote:
> >> > Neither CCR nor the MNS quorum with FSW use physical disk resources
> >> > (e.g.,
> >> > cluster-managed disks). You need to remove the disk resource from the
> >> > default cluster group (and from any other cluster groups) and configure
> >> > the
> >> > cluster quorum to use MNS.
> >> > Seehttp://technet.microsoft.com/en-us/library/bb124038.aspxforstepsto
> >> > do
> >> > this.
> >> > --
> >> > Regards,
>
> >> > Scott Schnoll
> >> > Microsoft Corporation
> >> > This posting is provided "AS IS" with no warranties, and confers no
> >> > rights. Please do not send email directly to this alias. This alias is
> >> > for
> >> > newsgroup purposes only.
>
> >> > "AJ" wrote in message
>
> >> >news:b8b7ce92-9046-4ad9-8c0e-a3511ce309e7@i12g2000prf.googlegroups.com...
>
> >> > > Hi
> >> > > I'm having a heck of a time deploying CCR. I have done everything
> >> > > correctly as far as I can tell but I've not been able to get the disk
> >> > > groups to move to the other node and get a 1034 error in the event
> >> > > log
> >> > > everytime I try to fail the groups over. The 'cluster group' will
> >> > > failover to the other node without any problems, its just the groups
> >> > > that contain a physical disk resource that won't.
>
> >> > > The event log states the following:
>
> >> > > The disk associated with cluster disk resource 'LUN (D:)' could not
> >> > > be
> >> > > found. The expected signature of the disk was B0C1B79E. If the disk
> >> > > was removed from the server cluster, the resource should be deleted.
> >> > > If the disk was replaced, the resource must be deleted and created
> >> > > again in order to bring the disk online. If the disk has not been
> >> > > removed or replaced, it may be inaccessible at this time because it
> >> > > is
> >> > > reserved by another server cluster node.
>
> >> > > For more information, see Help and Support Center at
> >> > >http://go.microsoft.com/fwlink/events.asp.
>
> >> > > I have tried deleting the physical disk resource and recreating but
> >> > > still no joy. I have checked access to the File Share on the HT
> >> > > server
> >> > > and no problems there either.
>
> >> > > I have come across the same problem on another CCR cluster as well
>
> >> > > The config is 2 servers (HP) each with their own external storage
> >> > > array (HP) SAS drives
> >> > > I carved up the disks on both enclosures exactly the same. Used
> >> > > diskpart to align the disks and formated with NTFS (64K). Created the
> >> > > FSW on one of our HT servers. Configured the MNS to use the FSW etc
> >> > > etc. The OS is Windows Server 2003 SP2 R2.
>
> >> > > As I said before the default cluster group fails over without any
> >> > > problems.
>
> >> > > Anyone offer any help
>
> >> > > Cheers
>
> >> > > AJ- Hide quoted text -
>
> >> > - Show quoted text -
>
> >> Hi Scott
>
> >> Thanks for this. I seemed to of missed the small print! also haven't
> >> seen this mentioned anywhere before about removing the physical disk
> >> resource. I'll try again!
>
> >> Cheers
>
> >> AJ- Hide quoted text -
>
> >> - Show quoted text -
>
> > You have to remove the physical disks from the second node too after
> > it joins the cluster. Interesting that this step does not get
> > mentioned in a number of tutorials out there. I should of thought
> > about the whole concept and realised you wouldn't have disks failing
> > over! Anyway thanks for your help and pointing me in the right
> > direction you have saved me a lot of time!
>
> > AJ- Hide quoted text -
>
> - Show quoted text -
Sorry not sure what you mean by starting out with no shared storage?
As far as I was aware I hadn't any shared storage. I simply have two
boxes with the disks carved up identically each with their own arrays.
I then installed/configured the clustering software selecting MNS. By
default I had two physical disk resources for the first node (which I
deleted after seeing the note) and then when I added the second node I
had another two disk groups with physical disk resources in which
again were deleted. I was actually following another well known
tutorial which didn't mention this at all. I see your note but I think
you should make it clearer maybe in bold. This is probably something
that people who are used to creating shared storage clusters (like
myself) probably won't get the grasp of in the first instance.
Incidently I had the same issues on another CCR cluster I deployed.
Thanks for your help
AJ
date: Fri, 7 Dec 2007 01:08:30 -0800 (PST)
author: AJ
Re: MNS with FSW Clustering Problems (E2K7 CCR)
Shared storage refers to disk resources that are managed by the cluster. In
CCR, the disks you connect to the system should be local only, not on a
shared SCSI bus, and not shared between nodes. Because CCR does not use
shared disks, you should not have any disk resources in any cluster groups.
The note about this is called out separately, and NOTE is in bold. I don't
believe the text itself needs to be in bold, but I'll pass on the
suggestion.
In any event, glad you got it working!
--
Regards,
Scott Schnoll
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
>> - Show quoted text -
>
> Sorry not sure what you mean by starting out with no shared storage?
> As far as I was aware I hadn't any shared storage. I simply have two
> boxes with the disks carved up identically each with their own arrays.
> I then installed/configured the clustering software selecting MNS. By
> default I had two physical disk resources for the first node (which I
> deleted after seeing the note) and then when I added the second node I
> had another two disk groups with physical disk resources in which
> again were deleted. I was actually following another well known
> tutorial which didn't mention this at all. I see your note but I think
> you should make it clearer maybe in bold. This is probably something
> that people who are used to creating shared storage clusters (like
> myself) probably won't get the grasp of in the first instance.
> Incidently I had the same issues on another CCR cluster I deployed.
>
> Thanks for your help
>
> AJ
date: Fri, 7 Dec 2007 08:01:06 -0800
author: Scott Schnoll [MSFT]
Re: MNS with FSW Clustering Problems (E2K7 CCR)
On 7 Dec, 16:01, "Scott Schnoll [MSFT]"
wrote:
> Shared storage refers to disk resources that are managed by the cluster. In
> CCR, the disks you connect to the system should be local only, not on a
> shared SCSI bus, and not shared between nodes. Because CCR does not use
> shared disks, you should not have any disk resources in any cluster groups.
>
> The note about this is called out separately, and NOTE is in bold. I don't
> believe the text itself needs to be in bold, but I'll pass on the
> suggestion.
>
> In any event, glad you got it working!
> --
> Regards,
>
> Scott Schnoll
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
>
>
>
> >> - Show quoted text -
>
> > Sorry not sure what you mean by starting out with no shared storage?
> > As far as I was aware I hadn't any shared storage. I simply have two
> > boxes with the disks carved up identically each with their own arrays.
> > I then installed/configured the clustering software selecting MNS. By
> > default I had two physical disk resources for the first node (which I
> > deleted after seeing the note) and then when I added the second node I
> > had another two disk groups with physical disk resources in which
> > again were deleted. I was actually following another well known
> > tutorial which didn't mention this at all. I see your note but I think
> > you should make it clearer maybe in bold. This is probably something
> > that people who are used to creating shared storage clusters (like
> > myself) probably won't get the grasp of in the first instance.
> > Incidently I had the same issues on another CCR cluster I deployed.
>
> > Thanks for your help
>
> > AJ- Hide quoted text -
>
> - Show quoted text -
Well I did on both clusters I configured, must of been magic. Anyhow
it all looks good and seems to work well, pretty cool stuff. Thanks
again for pointing me in the right direction.
AJ
date: Fri, 7 Dec 2007 09:06:15 -0800 (PST)
author: AJ
|
|
