Guys
I have a cluster running on single node and i am trying to add the 2nd node
but getting this error. Any idea? I am using external EMC storage for the
physical disks.
The only different i could see is, in node 1, the mapping of disks in disk
mgmt are different from node 2. Example (Q drive [1G] is in disk 1 in node 1
while the 1G disk is mapped in disk in node 2. Cauld that be the reason? If
yes, Can i change the sequence? How?
TIA
************************************************************
[INFO] CLUSTER001: Checking that all nodes have access to the quorum
resource...
[INFO] CLUSTER001: Checking that all nodes have access to the quorum
resource...
[INFO] CLUSTER001: The following nodes cannot not verify that they can host
the quorum resource...
[ERR ] CLUSTER001: Could not verify that node "SERVER001" can host the
quorum resource. Ensure that your hardware is properly configured and that
all nodes have access to a quorum-capable resource.
[INFO] CLUSTER001: Checking that all nodes have access to the quorum
resource...
[ERR ] CLUSTER001: A multi-node cluster cannot be created because there is
not a quorum-capable resource common to all nodes. In some complex storage
solutions, such as a fiber channel switched fabric, a particular storage unit
might have a different identity (Target ID and/or LUN) on each computer in
the cluster. Although this is a valid storage configuration, it violates the
storage validation heuristics in the Add Nodes Wizard when using the default
Typical (full) configuration option, resulting in an error.
************************************************************As long as you are absolutely sure which disk resource is the Quorum
resource, you can override the verification wizard and designate the quorum
disk manually. I have had that problem in the past when there were many
disks presented to the host nodes. Once the node is added to the cluster,
the drives map correctly.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP.
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:41E599C0-E0CC-4258-B992-7B11B8D49ADA@.microsoft.com...
> Guys
> I have a cluster running on single node and i am trying to add the 2nd
> node
> but getting this error. Any idea? I am using external EMC storage for the
> physical disks.
> The only different i could see is, in node 1, the mapping of disks in disk
> mgmt are different from node 2. Example (Q drive [1G] is in disk 1 in node
> 1
> while the 1G disk is mapped in disk in node 2. Cauld that be the reason?
> If
> yes, Can i change the sequence? How?
> TIA
> ************************************************************
> [INFO] CLUSTER001: Checking that all nodes have access to the quorum
> resource...
> [INFO] CLUSTER001: Checking that all nodes have access to the quorum
> resource...
> [INFO] CLUSTER001: The following nodes cannot not verify that they can
> host
> the quorum resource...
> [ERR ] CLUSTER001: Could not verify that node "SERVER001" can host the
> quorum resource. Ensure that your hardware is properly configured and that
> all nodes have access to a quorum-capable resource.
> [INFO] CLUSTER001: Checking that all nodes have access to the quorum
> resource...
> [ERR ] CLUSTER001: A multi-node cluster cannot be created because there is
> not a quorum-capable resource common to all nodes. In some complex storage
> solutions, such as a fiber channel switched fabric, a particular storage
> unit
> might have a different identity (Target ID and/or LUN) on each computer in
> the cluster. Although this is a valid storage configuration, it violates
> the
> storage validation heuristics in the Add Nodes Wizard when using the
> default
> Typical (full) configuration option, resulting in an error.
> ************************************************************|||hi Geoff,
Sorry i was bit unlcear in explaining my current config in earlier msgs.
What i am trying to say was
in node 1, in disk mgmt, Q drive is mapped in disk 1
in node 2, in disk mgmt, Q drive is mapped to disk 4
Anyway,
In your reply, "override verification wizard" does it mean disabling the
heauristic scanning and join the node first? I have joined the cluster using
minimum config and skipping the verification process. Now, 2nd node is in
cluster and all the disks a hold by 1st node. I wanted to try doing failover
but my worries are it's in production and i afraid the incorrect mapping may
corrupt the data if i do failover. What you think?
"Geoff N. Hiten" wrote:
> As long as you are absolutely sure which disk resource is the Quorum
> resource, you can override the verification wizard and designate the quorum
> disk manually. I have had that problem in the past when there were many
> disks presented to the host nodes. Once the node is added to the cluster,
> the drives map correctly.
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP.
> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:41E599C0-E0CC-4258-B992-7B11B8D49ADA@.microsoft.com...
> > Guys
> > I have a cluster running on single node and i am trying to add the 2nd
> > node
> > but getting this error. Any idea? I am using external EMC storage for the
> > physical disks.
> > The only different i could see is, in node 1, the mapping of disks in disk
> > mgmt are different from node 2. Example (Q drive [1G] is in disk 1 in node
> > 1
> > while the 1G disk is mapped in disk in node 2. Cauld that be the reason?
> > If
> > yes, Can i change the sequence? How?
> > TIA
> >
> > ************************************************************
> > [INFO] CLUSTER001: Checking that all nodes have access to the quorum
> > resource...
> >
> > [INFO] CLUSTER001: Checking that all nodes have access to the quorum
> > resource...
> >
> > [INFO] CLUSTER001: The following nodes cannot not verify that they can
> > host
> > the quorum resource...
> >
> > [ERR ] CLUSTER001: Could not verify that node "SERVER001" can host the
> > quorum resource. Ensure that your hardware is properly configured and that
> > all nodes have access to a quorum-capable resource.
> >
> > [INFO] CLUSTER001: Checking that all nodes have access to the quorum
> > resource...
> >
> > [ERR ] CLUSTER001: A multi-node cluster cannot be created because there is
> > not a quorum-capable resource common to all nodes. In some complex storage
> > solutions, such as a fiber channel switched fabric, a particular storage
> > unit
> > might have a different identity (Target ID and/or LUN) on each computer in
> > the cluster. Although this is a valid storage configuration, it violates
> > the
> > storage validation heuristics in the Add Nodes Wizard when using the
> > default
> > Typical (full) configuration option, resulting in an error.
> > ************************************************************
>
>|||You did exactly what I suggested. Worst case, SQL won't start due to
inability to find the files and it will fail back to the first node with
data intact. I doubt this will happen as the cluster services use disk
signatures to positively ID each disk.
I would wait until a scheduled maintenance window to try a failover, just so
you don't have to explain excessive downtime..
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:92121BBB-5AC8-4B9C-9C32-A7650116F3B7@.microsoft.com...
> hi Geoff,
> Sorry i was bit unlcear in explaining my current config in earlier msgs.
> What i am trying to say was
> in node 1, in disk mgmt, Q drive is mapped in disk 1
> in node 2, in disk mgmt, Q drive is mapped to disk 4
> Anyway,
> In your reply, "override verification wizard" does it mean disabling the
> heauristic scanning and join the node first? I have joined the cluster
> using
> minimum config and skipping the verification process. Now, 2nd node is in
> cluster and all the disks a hold by 1st node. I wanted to try doing
> failover
> but my worries are it's in production and i afraid the incorrect mapping
> may
> corrupt the data if i do failover. What you think?
>
> "Geoff N. Hiten" wrote:
>> As long as you are absolutely sure which disk resource is the Quorum
>> resource, you can override the verification wizard and designate the
>> quorum
>> disk manually. I have had that problem in the past when there were many
>> disks presented to the host nodes. Once the node is added to the
>> cluster,
>> the drives map correctly.
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP.
>> "rupart" <rupart@.discussions.microsoft.com> wrote in message
>> news:41E599C0-E0CC-4258-B992-7B11B8D49ADA@.microsoft.com...
>> > Guys
>> > I have a cluster running on single node and i am trying to add the 2nd
>> > node
>> > but getting this error. Any idea? I am using external EMC storage for
>> > the
>> > physical disks.
>> > The only different i could see is, in node 1, the mapping of disks in
>> > disk
>> > mgmt are different from node 2. Example (Q drive [1G] is in disk 1 in
>> > node
>> > 1
>> > while the 1G disk is mapped in disk in node 2. Cauld that be the
>> > reason?
>> > If
>> > yes, Can i change the sequence? How?
>> > TIA
>> >
>> > ************************************************************
>> > [INFO] CLUSTER001: Checking that all nodes have access to the quorum
>> > resource...
>> >
>> > [INFO] CLUSTER001: Checking that all nodes have access to the quorum
>> > resource...
>> >
>> > [INFO] CLUSTER001: The following nodes cannot not verify that they can
>> > host
>> > the quorum resource...
>> >
>> > [ERR ] CLUSTER001: Could not verify that node "SERVER001" can host the
>> > quorum resource. Ensure that your hardware is properly configured and
>> > that
>> > all nodes have access to a quorum-capable resource.
>> >
>> > [INFO] CLUSTER001: Checking that all nodes have access to the quorum
>> > resource...
>> >
>> > [ERR ] CLUSTER001: A multi-node cluster cannot be created because there
>> > is
>> > not a quorum-capable resource common to all nodes. In some complex
>> > storage
>> > solutions, such as a fiber channel switched fabric, a particular
>> > storage
>> > unit
>> > might have a different identity (Target ID and/or LUN) on each computer
>> > in
>> > the cluster. Although this is a valid storage configuration, it
>> > violates
>> > the
>> > storage validation heuristics in the Add Nodes Wizard when using the
>> > default
>> > Typical (full) configuration option, resulting in an error.
>> > ************************************************************
>>|||hi Geoff,
thank you..let me try when i get the downtime.if it still fails, what can i
do to correct the thing?thanks again
"Geoff N. Hiten" wrote:
> You did exactly what I suggested. Worst case, SQL won't start due to
> inability to find the files and it will fail back to the first node with
> data intact. I doubt this will happen as the cluster services use disk
> signatures to positively ID each disk.
> I would wait until a scheduled maintenance window to try a failover, just so
> you don't have to explain excessive downtime..
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:92121BBB-5AC8-4B9C-9C32-A7650116F3B7@.microsoft.com...
> > hi Geoff,
> > Sorry i was bit unlcear in explaining my current config in earlier msgs.
> > What i am trying to say was
> > in node 1, in disk mgmt, Q drive is mapped in disk 1
> > in node 2, in disk mgmt, Q drive is mapped to disk 4
> >
> > Anyway,
> > In your reply, "override verification wizard" does it mean disabling the
> > heauristic scanning and join the node first? I have joined the cluster
> > using
> > minimum config and skipping the verification process. Now, 2nd node is in
> > cluster and all the disks a hold by 1st node. I wanted to try doing
> > failover
> > but my worries are it's in production and i afraid the incorrect mapping
> > may
> > corrupt the data if i do failover. What you think?
> >
> >
> > "Geoff N. Hiten" wrote:
> >
> >> As long as you are absolutely sure which disk resource is the Quorum
> >> resource, you can override the verification wizard and designate the
> >> quorum
> >> disk manually. I have had that problem in the past when there were many
> >> disks presented to the host nodes. Once the node is added to the
> >> cluster,
> >> the drives map correctly.
> >>
> >> Geoff N. Hiten
> >> Senior Database Administrator
> >> Microsoft SQL Server MVP.
> >>
> >> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> >> news:41E599C0-E0CC-4258-B992-7B11B8D49ADA@.microsoft.com...
> >> > Guys
> >> > I have a cluster running on single node and i am trying to add the 2nd
> >> > node
> >> > but getting this error. Any idea? I am using external EMC storage for
> >> > the
> >> > physical disks.
> >> > The only different i could see is, in node 1, the mapping of disks in
> >> > disk
> >> > mgmt are different from node 2. Example (Q drive [1G] is in disk 1 in
> >> > node
> >> > 1
> >> > while the 1G disk is mapped in disk in node 2. Cauld that be the
> >> > reason?
> >> > If
> >> > yes, Can i change the sequence? How?
> >> > TIA
> >> >
> >> > ************************************************************
> >> > [INFO] CLUSTER001: Checking that all nodes have access to the quorum
> >> > resource...
> >> >
> >> > [INFO] CLUSTER001: Checking that all nodes have access to the quorum
> >> > resource...
> >> >
> >> > [INFO] CLUSTER001: The following nodes cannot not verify that they can
> >> > host
> >> > the quorum resource...
> >> >
> >> > [ERR ] CLUSTER001: Could not verify that node "SERVER001" can host the
> >> > quorum resource. Ensure that your hardware is properly configured and
> >> > that
> >> > all nodes have access to a quorum-capable resource.
> >> >
> >> > [INFO] CLUSTER001: Checking that all nodes have access to the quorum
> >> > resource...
> >> >
> >> > [ERR ] CLUSTER001: A multi-node cluster cannot be created because there
> >> > is
> >> > not a quorum-capable resource common to all nodes. In some complex
> >> > storage
> >> > solutions, such as a fiber channel switched fabric, a particular
> >> > storage
> >> > unit
> >> > might have a different identity (Target ID and/or LUN) on each computer
> >> > in
> >> > the cluster. Although this is a valid storage configuration, it
> >> > violates
> >> > the
> >> > storage validation heuristics in the Add Nodes Wizard when using the
> >> > default
> >> > Typical (full) configuration option, resulting in an error.
> >> > ************************************************************
> >>
> >>
> >>
>
>|||If it won't fail over correctly, you will likely have to use Access Logix to
logically disconnect all the disks from the host computer at the EMC level.
You can then present them back to the host node in the correct order one at
a time.
This exact thing has happened to me before. I had over 10 clustered disks
and the wizard couldn't figure out which one was the Quorum. I manually
designated it and everything then matched right up.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:BDE8B45A-42B4-413E-9102-9C539EE5B8FF@.microsoft.com...
> hi Geoff,
> thank you..let me try when i get the downtime.if it still fails, what can
> i
> do to correct the thing?thanks again
> "Geoff N. Hiten" wrote:
>> You did exactly what I suggested. Worst case, SQL won't start due to
>> inability to find the files and it will fail back to the first node with
>> data intact. I doubt this will happen as the cluster services use disk
>> signatures to positively ID each disk.
>> I would wait until a scheduled maintenance window to try a failover, just
>> so
>> you don't have to explain excessive downtime..
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>> "rupart" <rupart@.discussions.microsoft.com> wrote in message
>> news:92121BBB-5AC8-4B9C-9C32-A7650116F3B7@.microsoft.com...
>> > hi Geoff,
>> > Sorry i was bit unlcear in explaining my current config in earlier
>> > msgs.
>> > What i am trying to say was
>> > in node 1, in disk mgmt, Q drive is mapped in disk 1
>> > in node 2, in disk mgmt, Q drive is mapped to disk 4
>> >
>> > Anyway,
>> > In your reply, "override verification wizard" does it mean disabling
>> > the
>> > heauristic scanning and join the node first? I have joined the cluster
>> > using
>> > minimum config and skipping the verification process. Now, 2nd node is
>> > in
>> > cluster and all the disks a hold by 1st node. I wanted to try doing
>> > failover
>> > but my worries are it's in production and i afraid the incorrect
>> > mapping
>> > may
>> > corrupt the data if i do failover. What you think?
>> >
>> >
>> > "Geoff N. Hiten" wrote:
>> >
>> >> As long as you are absolutely sure which disk resource is the Quorum
>> >> resource, you can override the verification wizard and designate the
>> >> quorum
>> >> disk manually. I have had that problem in the past when there were
>> >> many
>> >> disks presented to the host nodes. Once the node is added to the
>> >> cluster,
>> >> the drives map correctly.
>> >>
>> >> Geoff N. Hiten
>> >> Senior Database Administrator
>> >> Microsoft SQL Server MVP.
>> >>
>> >> "rupart" <rupart@.discussions.microsoft.com> wrote in message
>> >> news:41E599C0-E0CC-4258-B992-7B11B8D49ADA@.microsoft.com...
>> >> > Guys
>> >> > I have a cluster running on single node and i am trying to add the
>> >> > 2nd
>> >> > node
>> >> > but getting this error. Any idea? I am using external EMC storage
>> >> > for
>> >> > the
>> >> > physical disks.
>> >> > The only different i could see is, in node 1, the mapping of disks
>> >> > in
>> >> > disk
>> >> > mgmt are different from node 2. Example (Q drive [1G] is in disk 1
>> >> > in
>> >> > node
>> >> > 1
>> >> > while the 1G disk is mapped in disk in node 2. Cauld that be the
>> >> > reason?
>> >> > If
>> >> > yes, Can i change the sequence? How?
>> >> > TIA
>> >> >
>> >> > ************************************************************
>> >> > [INFO] CLUSTER001: Checking that all nodes have access to the quorum
>> >> > resource...
>> >> >
>> >> > [INFO] CLUSTER001: Checking that all nodes have access to the quorum
>> >> > resource...
>> >> >
>> >> > [INFO] CLUSTER001: The following nodes cannot not verify that they
>> >> > can
>> >> > host
>> >> > the quorum resource...
>> >> >
>> >> > [ERR ] CLUSTER001: Could not verify that node "SERVER001" can host
>> >> > the
>> >> > quorum resource. Ensure that your hardware is properly configured
>> >> > and
>> >> > that
>> >> > all nodes have access to a quorum-capable resource.
>> >> >
>> >> > [INFO] CLUSTER001: Checking that all nodes have access to the quorum
>> >> > resource...
>> >> >
>> >> > [ERR ] CLUSTER001: A multi-node cluster cannot be created because
>> >> > there
>> >> > is
>> >> > not a quorum-capable resource common to all nodes. In some complex
>> >> > storage
>> >> > solutions, such as a fiber channel switched fabric, a particular
>> >> > storage
>> >> > unit
>> >> > might have a different identity (Target ID and/or LUN) on each
>> >> > computer
>> >> > in
>> >> > the cluster. Although this is a valid storage configuration, it
>> >> > violates
>> >> > the
>> >> > storage validation heuristics in the Add Nodes Wizard when using the
>> >> > default
>> >> > Typical (full) configuration option, resulting in an error.
>> >> > ************************************************************
>> >>
>> >>
>> >>
>>|||hi Geoff,
Actually mine is SQL cluster. Right now 2nd node does not have the SQL
binaries. How do i get them installed? Today we had power trip and used that
opportunity to do failover. Q failover as expected but not the sql cluster
binaries because i just relaized the 2nd node doesnt have the binaries. If we
used wizard, it shd have done that(i mean rebuilding the sql) for us. But how
abt in this case? How to do manually? or any other way?
thanks a lot again
"Geoff N. Hiten" wrote:
> If it won't fail over correctly, you will likely have to use Access Logix to
> logically disconnect all the disks from the host computer at the EMC level.
> You can then present them back to the host node in the correct order one at
> a time.
> This exact thing has happened to me before. I had over 10 clustered disks
> and the wizard couldn't figure out which one was the Quorum. I manually
> designated it and everything then matched right up.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:BDE8B45A-42B4-413E-9102-9C539EE5B8FF@.microsoft.com...
> > hi Geoff,
> > thank you..let me try when i get the downtime.if it still fails, what can
> > i
> > do to correct the thing?thanks again
> >
> > "Geoff N. Hiten" wrote:
> >
> >> You did exactly what I suggested. Worst case, SQL won't start due to
> >> inability to find the files and it will fail back to the first node with
> >> data intact. I doubt this will happen as the cluster services use disk
> >> signatures to positively ID each disk.
> >>
> >> I would wait until a scheduled maintenance window to try a failover, just
> >> so
> >> you don't have to explain excessive downtime..
> >>
> >> --
> >> Geoff N. Hiten
> >> Senior Database Administrator
> >> Microsoft SQL Server MVP
> >>
> >> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> >> news:92121BBB-5AC8-4B9C-9C32-A7650116F3B7@.microsoft.com...
> >> > hi Geoff,
> >> > Sorry i was bit unlcear in explaining my current config in earlier
> >> > msgs.
> >> > What i am trying to say was
> >> > in node 1, in disk mgmt, Q drive is mapped in disk 1
> >> > in node 2, in disk mgmt, Q drive is mapped to disk 4
> >> >
> >> > Anyway,
> >> > In your reply, "override verification wizard" does it mean disabling
> >> > the
> >> > heauristic scanning and join the node first? I have joined the cluster
> >> > using
> >> > minimum config and skipping the verification process. Now, 2nd node is
> >> > in
> >> > cluster and all the disks a hold by 1st node. I wanted to try doing
> >> > failover
> >> > but my worries are it's in production and i afraid the incorrect
> >> > mapping
> >> > may
> >> > corrupt the data if i do failover. What you think?
> >> >
> >> >
> >> > "Geoff N. Hiten" wrote:
> >> >
> >> >> As long as you are absolutely sure which disk resource is the Quorum
> >> >> resource, you can override the verification wizard and designate the
> >> >> quorum
> >> >> disk manually. I have had that problem in the past when there were
> >> >> many
> >> >> disks presented to the host nodes. Once the node is added to the
> >> >> cluster,
> >> >> the drives map correctly.
> >> >>
> >> >> Geoff N. Hiten
> >> >> Senior Database Administrator
> >> >> Microsoft SQL Server MVP.
> >> >>
> >> >> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> >> >> news:41E599C0-E0CC-4258-B992-7B11B8D49ADA@.microsoft.com...
> >> >> > Guys
> >> >> > I have a cluster running on single node and i am trying to add the
> >> >> > 2nd
> >> >> > node
> >> >> > but getting this error. Any idea? I am using external EMC storage
> >> >> > for
> >> >> > the
> >> >> > physical disks.
> >> >> > The only different i could see is, in node 1, the mapping of disks
> >> >> > in
> >> >> > disk
> >> >> > mgmt are different from node 2. Example (Q drive [1G] is in disk 1
> >> >> > in
> >> >> > node
> >> >> > 1
> >> >> > while the 1G disk is mapped in disk in node 2. Cauld that be the
> >> >> > reason?
> >> >> > If
> >> >> > yes, Can i change the sequence? How?
> >> >> > TIA
> >> >> >
> >> >> > ************************************************************
> >> >> > [INFO] CLUSTER001: Checking that all nodes have access to the quorum
> >> >> > resource...
> >> >> >
> >> >> > [INFO] CLUSTER001: Checking that all nodes have access to the quorum
> >> >> > resource...
> >> >> >
> >> >> > [INFO] CLUSTER001: The following nodes cannot not verify that they
> >> >> > can
> >> >> > host
> >> >> > the quorum resource...
> >> >> >
> >> >> > [ERR ] CLUSTER001: Could not verify that node "SERVER001" can host
> >> >> > the
> >> >> > quorum resource. Ensure that your hardware is properly configured
> >> >> > and
> >> >> > that
> >> >> > all nodes have access to a quorum-capable resource.
> >> >> >
> >> >> > [INFO] CLUSTER001: Checking that all nodes have access to the quorum
> >> >> > resource...
> >> >> >
> >> >> > [ERR ] CLUSTER001: A multi-node cluster cannot be created because
> >> >> > there
> >> >> > is
> >> >> > not a quorum-capable resource common to all nodes. In some complex
> >> >> > storage
> >> >> > solutions, such as a fiber channel switched fabric, a particular
> >> >> > storage
> >> >> > unit
> >> >> > might have a different identity (Target ID and/or LUN) on each
> >> >> > computer
> >> >> > in
> >> >> > the cluster. Although this is a valid storage configuration, it
> >> >> > violates
> >> >> > the
> >> >> > storage validation heuristics in the Add Nodes Wizard when using the
> >> >> > default
> >> >> > Typical (full) configuration option, resulting in an error.
> >> >> > ************************************************************
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||Check out "How to add nodes to an existing virtual server" in the BOL.
Also, once that is done, install the service pack on the *new* node, while
the SQL group is running on the *existing* node.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:8FD9E670-66DC-4540-8829-8A438FF2AE5C@.microsoft.com...
> hi Geoff,
> Actually mine is SQL cluster. Right now 2nd node does not have the SQL
> binaries. How do i get them installed? Today we had power trip and used
> that
> opportunity to do failover. Q failover as expected but not the sql cluster
> binaries because i just relaized the 2nd node doesnt have the binaries. If
> we
> used wizard, it shd have done that(i mean rebuilding the sql) for us. But
> how
> abt in this case? How to do manually? or any other way?
> thanks a lot again
> "Geoff N. Hiten" wrote:
>> If it won't fail over correctly, you will likely have to use Access Logix
>> to
>> logically disconnect all the disks from the host computer at the EMC
>> level.
>> You can then present them back to the host node in the correct order one
>> at
>> a time.
>> This exact thing has happened to me before. I had over 10 clustered
>> disks
>> and the wizard couldn't figure out which one was the Quorum. I manually
>> designated it and everything then matched right up.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>> "rupart" <rupart@.discussions.microsoft.com> wrote in message
>> news:BDE8B45A-42B4-413E-9102-9C539EE5B8FF@.microsoft.com...
>> > hi Geoff,
>> > thank you..let me try when i get the downtime.if it still fails, what
>> > can
>> > i
>> > do to correct the thing?thanks again
>> >
>> > "Geoff N. Hiten" wrote:
>> >
>> >> You did exactly what I suggested. Worst case, SQL won't start due to
>> >> inability to find the files and it will fail back to the first node
>> >> with
>> >> data intact. I doubt this will happen as the cluster services use disk
>> >> signatures to positively ID each disk.
>> >>
>> >> I would wait until a scheduled maintenance window to try a failover,
>> >> just
>> >> so
>> >> you don't have to explain excessive downtime..
>> >>
>> >> --
>> >> Geoff N. Hiten
>> >> Senior Database Administrator
>> >> Microsoft SQL Server MVP
>> >>
>> >> "rupart" <rupart@.discussions.microsoft.com> wrote in message
>> >> news:92121BBB-5AC8-4B9C-9C32-A7650116F3B7@.microsoft.com...
>> >> > hi Geoff,
>> >> > Sorry i was bit unlcear in explaining my current config in earlier
>> >> > msgs.
>> >> > What i am trying to say was
>> >> > in node 1, in disk mgmt, Q drive is mapped in disk 1
>> >> > in node 2, in disk mgmt, Q drive is mapped to disk 4
>> >> >
>> >> > Anyway,
>> >> > In your reply, "override verification wizard" does it mean
>> >> > disabling
>> >> > the
>> >> > heauristic scanning and join the node first? I have joined the
>> >> > cluster
>> >> > using
>> >> > minimum config and skipping the verification process. Now, 2nd node
>> >> > is
>> >> > in
>> >> > cluster and all the disks a hold by 1st node. I wanted to try doing
>> >> > failover
>> >> > but my worries are it's in production and i afraid the incorrect
>> >> > mapping
>> >> > may
>> >> > corrupt the data if i do failover. What you think?
>> >> >
>> >> >
>> >> > "Geoff N. Hiten" wrote:
>> >> >
>> >> >> As long as you are absolutely sure which disk resource is the
>> >> >> Quorum
>> >> >> resource, you can override the verification wizard and designate
>> >> >> the
>> >> >> quorum
>> >> >> disk manually. I have had that problem in the past when there were
>> >> >> many
>> >> >> disks presented to the host nodes. Once the node is added to the
>> >> >> cluster,
>> >> >> the drives map correctly.
>> >> >>
>> >> >> Geoff N. Hiten
>> >> >> Senior Database Administrator
>> >> >> Microsoft SQL Server MVP.
>> >> >>
>> >> >> "rupart" <rupart@.discussions.microsoft.com> wrote in message
>> >> >> news:41E599C0-E0CC-4258-B992-7B11B8D49ADA@.microsoft.com...
>> >> >> > Guys
>> >> >> > I have a cluster running on single node and i am trying to add
>> >> >> > the
>> >> >> > 2nd
>> >> >> > node
>> >> >> > but getting this error. Any idea? I am using external EMC storage
>> >> >> > for
>> >> >> > the
>> >> >> > physical disks.
>> >> >> > The only different i could see is, in node 1, the mapping of
>> >> >> > disks
>> >> >> > in
>> >> >> > disk
>> >> >> > mgmt are different from node 2. Example (Q drive [1G] is in disk
>> >> >> > 1
>> >> >> > in
>> >> >> > node
>> >> >> > 1
>> >> >> > while the 1G disk is mapped in disk in node 2. Cauld that be the
>> >> >> > reason?
>> >> >> > If
>> >> >> > yes, Can i change the sequence? How?
>> >> >> > TIA
>> >> >> >
>> >> >> > ************************************************************
>> >> >> > [INFO] CLUSTER001: Checking that all nodes have access to the
>> >> >> > quorum
>> >> >> > resource...
>> >> >> >
>> >> >> > [INFO] CLUSTER001: Checking that all nodes have access to the
>> >> >> > quorum
>> >> >> > resource...
>> >> >> >
>> >> >> > [INFO] CLUSTER001: The following nodes cannot not verify that
>> >> >> > they
>> >> >> > can
>> >> >> > host
>> >> >> > the quorum resource...
>> >> >> >
>> >> >> > [ERR ] CLUSTER001: Could not verify that node "SERVER001" can
>> >> >> > host
>> >> >> > the
>> >> >> > quorum resource. Ensure that your hardware is properly configured
>> >> >> > and
>> >> >> > that
>> >> >> > all nodes have access to a quorum-capable resource.
>> >> >> >
>> >> >> > [INFO] CLUSTER001: Checking that all nodes have access to the
>> >> >> > quorum
>> >> >> > resource...
>> >> >> >
>> >> >> > [ERR ] CLUSTER001: A multi-node cluster cannot be created because
>> >> >> > there
>> >> >> > is
>> >> >> > not a quorum-capable resource common to all nodes. In some
>> >> >> > complex
>> >> >> > storage
>> >> >> > solutions, such as a fiber channel switched fabric, a particular
>> >> >> > storage
>> >> >> > unit
>> >> >> > might have a different identity (Target ID and/or LUN) on each
>> >> >> > computer
>> >> >> > in
>> >> >> > the cluster. Although this is a valid storage configuration, it
>> >> >> > violates
>> >> >> > the
>> >> >> > storage validation heuristics in the Add Nodes Wizard when using
>> >> >> > the
>> >> >> > default
>> >> >> > Typical (full) configuration option, resulting in an error.
>> >> >> > ************************************************************
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||The Cluster wizard only handles the cluster configuration. You still have
to add SQL. As Tom pointed out, there is a section in BOL on maintaining a
failover cluster. The topic How to Add Nodes to a Failover Cluster will
walk you through the basic install. You will need to reapply any service
packs and hotfixes to bring the binaries fully up to date.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:8FD9E670-66DC-4540-8829-8A438FF2AE5C@.microsoft.com...
> hi Geoff,
> Actually mine is SQL cluster. Right now 2nd node does not have the SQL
> binaries. How do i get them installed? Today we had power trip and used
> that
> opportunity to do failover. Q failover as expected but not the sql cluster
> binaries because i just relaized the 2nd node doesnt have the binaries. If
> we
> used wizard, it shd have done that(i mean rebuilding the sql) for us. But
> how
> abt in this case? How to do manually? or any other way?
> thanks a lot again
> "Geoff N. Hiten" wrote:
>> If it won't fail over correctly, you will likely have to use Access Logix
>> to
>> logically disconnect all the disks from the host computer at the EMC
>> level.
>> You can then present them back to the host node in the correct order one
>> at
>> a time.
>> This exact thing has happened to me before. I had over 10 clustered
>> disks
>> and the wizard couldn't figure out which one was the Quorum. I manually
>> designated it and everything then matched right up.
>> --
>> Geoff N. Hiten
>> Senior Database Administrator
>> Microsoft SQL Server MVP
>> "rupart" <rupart@.discussions.microsoft.com> wrote in message
>> news:BDE8B45A-42B4-413E-9102-9C539EE5B8FF@.microsoft.com...
>> > hi Geoff,
>> > thank you..let me try when i get the downtime.if it still fails, what
>> > can
>> > i
>> > do to correct the thing?thanks again
>> >
>> > "Geoff N. Hiten" wrote:
>> >
>> >> You did exactly what I suggested. Worst case, SQL won't start due to
>> >> inability to find the files and it will fail back to the first node
>> >> with
>> >> data intact. I doubt this will happen as the cluster services use disk
>> >> signatures to positively ID each disk.
>> >>
>> >> I would wait until a scheduled maintenance window to try a failover,
>> >> just
>> >> so
>> >> you don't have to explain excessive downtime..
>> >>
>> >> --
>> >> Geoff N. Hiten
>> >> Senior Database Administrator
>> >> Microsoft SQL Server MVP
>> >>
>> >> "rupart" <rupart@.discussions.microsoft.com> wrote in message
>> >> news:92121BBB-5AC8-4B9C-9C32-A7650116F3B7@.microsoft.com...
>> >> > hi Geoff,
>> >> > Sorry i was bit unlcear in explaining my current config in earlier
>> >> > msgs.
>> >> > What i am trying to say was
>> >> > in node 1, in disk mgmt, Q drive is mapped in disk 1
>> >> > in node 2, in disk mgmt, Q drive is mapped to disk 4
>> >> >
>> >> > Anyway,
>> >> > In your reply, "override verification wizard" does it mean
>> >> > disabling
>> >> > the
>> >> > heauristic scanning and join the node first? I have joined the
>> >> > cluster
>> >> > using
>> >> > minimum config and skipping the verification process. Now, 2nd node
>> >> > is
>> >> > in
>> >> > cluster and all the disks a hold by 1st node. I wanted to try doing
>> >> > failover
>> >> > but my worries are it's in production and i afraid the incorrect
>> >> > mapping
>> >> > may
>> >> > corrupt the data if i do failover. What you think?
>> >> >
>> >> >
>> >> > "Geoff N. Hiten" wrote:
>> >> >
>> >> >> As long as you are absolutely sure which disk resource is the
>> >> >> Quorum
>> >> >> resource, you can override the verification wizard and designate
>> >> >> the
>> >> >> quorum
>> >> >> disk manually. I have had that problem in the past when there were
>> >> >> many
>> >> >> disks presented to the host nodes. Once the node is added to the
>> >> >> cluster,
>> >> >> the drives map correctly.
>> >> >>
>> >> >> Geoff N. Hiten
>> >> >> Senior Database Administrator
>> >> >> Microsoft SQL Server MVP.
>> >> >>
>> >> >> "rupart" <rupart@.discussions.microsoft.com> wrote in message
>> >> >> news:41E599C0-E0CC-4258-B992-7B11B8D49ADA@.microsoft.com...
>> >> >> > Guys
>> >> >> > I have a cluster running on single node and i am trying to add
>> >> >> > the
>> >> >> > 2nd
>> >> >> > node
>> >> >> > but getting this error. Any idea? I am using external EMC storage
>> >> >> > for
>> >> >> > the
>> >> >> > physical disks.
>> >> >> > The only different i could see is, in node 1, the mapping of
>> >> >> > disks
>> >> >> > in
>> >> >> > disk
>> >> >> > mgmt are different from node 2. Example (Q drive [1G] is in disk
>> >> >> > 1
>> >> >> > in
>> >> >> > node
>> >> >> > 1
>> >> >> > while the 1G disk is mapped in disk in node 2. Cauld that be the
>> >> >> > reason?
>> >> >> > If
>> >> >> > yes, Can i change the sequence? How?
>> >> >> > TIA
>> >> >> >
>> >> >> > ************************************************************
>> >> >> > [INFO] CLUSTER001: Checking that all nodes have access to the
>> >> >> > quorum
>> >> >> > resource...
>> >> >> >
>> >> >> > [INFO] CLUSTER001: Checking that all nodes have access to the
>> >> >> > quorum
>> >> >> > resource...
>> >> >> >
>> >> >> > [INFO] CLUSTER001: The following nodes cannot not verify that
>> >> >> > they
>> >> >> > can
>> >> >> > host
>> >> >> > the quorum resource...
>> >> >> >
>> >> >> > [ERR ] CLUSTER001: Could not verify that node "SERVER001" can
>> >> >> > host
>> >> >> > the
>> >> >> > quorum resource. Ensure that your hardware is properly configured
>> >> >> > and
>> >> >> > that
>> >> >> > all nodes have access to a quorum-capable resource.
>> >> >> >
>> >> >> > [INFO] CLUSTER001: Checking that all nodes have access to the
>> >> >> > quorum
>> >> >> > resource...
>> >> >> >
>> >> >> > [ERR ] CLUSTER001: A multi-node cluster cannot be created because
>> >> >> > there
>> >> >> > is
>> >> >> > not a quorum-capable resource common to all nodes. In some
>> >> >> > complex
>> >> >> > storage
>> >> >> > solutions, such as a fiber channel switched fabric, a particular
>> >> >> > storage
>> >> >> > unit
>> >> >> > might have a different identity (Target ID and/or LUN) on each
>> >> >> > computer
>> >> >> > in
>> >> >> > the cluster. Although this is a valid storage configuration, it
>> >> >> > violates
>> >> >> > the
>> >> >> > storage validation heuristics in the Add Nodes Wizard when using
>> >> >> > the
>> >> >> > default
>> >> >> > Typical (full) configuration option, resulting in an error.
>> >> >> > ************************************************************
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||hi Tom,
is BOL=beginning of line? i cant see any link or reference or does BOL means
sth else...
"Tom Moreau" wrote:
> Check out "How to add nodes to an existing virtual server" in the BOL.
> Also, once that is done, install the service pack on the *new* node, while
> the SQL group is running on the *existing* node.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:8FD9E670-66DC-4540-8829-8A438FF2AE5C@.microsoft.com...
> > hi Geoff,
> > Actually mine is SQL cluster. Right now 2nd node does not have the SQL
> > binaries. How do i get them installed? Today we had power trip and used
> > that
> > opportunity to do failover. Q failover as expected but not the sql cluster
> > binaries because i just relaized the 2nd node doesnt have the binaries. If
> > we
> > used wizard, it shd have done that(i mean rebuilding the sql) for us. But
> > how
> > abt in this case? How to do manually? or any other way?
> > thanks a lot again
> >
> > "Geoff N. Hiten" wrote:
> >
> >> If it won't fail over correctly, you will likely have to use Access Logix
> >> to
> >> logically disconnect all the disks from the host computer at the EMC
> >> level.
> >> You can then present them back to the host node in the correct order one
> >> at
> >> a time.
> >>
> >> This exact thing has happened to me before. I had over 10 clustered
> >> disks
> >> and the wizard couldn't figure out which one was the Quorum. I manually
> >> designated it and everything then matched right up.
> >>
> >> --
> >> Geoff N. Hiten
> >> Senior Database Administrator
> >> Microsoft SQL Server MVP
> >>
> >> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> >> news:BDE8B45A-42B4-413E-9102-9C539EE5B8FF@.microsoft.com...
> >> > hi Geoff,
> >> > thank you..let me try when i get the downtime.if it still fails, what
> >> > can
> >> > i
> >> > do to correct the thing?thanks again
> >> >
> >> > "Geoff N. Hiten" wrote:
> >> >
> >> >> You did exactly what I suggested. Worst case, SQL won't start due to
> >> >> inability to find the files and it will fail back to the first node
> >> >> with
> >> >> data intact. I doubt this will happen as the cluster services use disk
> >> >> signatures to positively ID each disk.
> >> >>
> >> >> I would wait until a scheduled maintenance window to try a failover,
> >> >> just
> >> >> so
> >> >> you don't have to explain excessive downtime..
> >> >>
> >> >> --
> >> >> Geoff N. Hiten
> >> >> Senior Database Administrator
> >> >> Microsoft SQL Server MVP
> >> >>
> >> >> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> >> >> news:92121BBB-5AC8-4B9C-9C32-A7650116F3B7@.microsoft.com...
> >> >> > hi Geoff,
> >> >> > Sorry i was bit unlcear in explaining my current config in earlier
> >> >> > msgs.
> >> >> > What i am trying to say was
> >> >> > in node 1, in disk mgmt, Q drive is mapped in disk 1
> >> >> > in node 2, in disk mgmt, Q drive is mapped to disk 4
> >> >> >
> >> >> > Anyway,
> >> >> > In your reply, "override verification wizard" does it mean
> >> >> > disabling
> >> >> > the
> >> >> > heauristic scanning and join the node first? I have joined the
> >> >> > cluster
> >> >> > using
> >> >> > minimum config and skipping the verification process. Now, 2nd node
> >> >> > is
> >> >> > in
> >> >> > cluster and all the disks a hold by 1st node. I wanted to try doing
> >> >> > failover
> >> >> > but my worries are it's in production and i afraid the incorrect
> >> >> > mapping
> >> >> > may
> >> >> > corrupt the data if i do failover. What you think?
> >> >> >
> >> >> >
> >> >> > "Geoff N. Hiten" wrote:
> >> >> >
> >> >> >> As long as you are absolutely sure which disk resource is the
> >> >> >> Quorum
> >> >> >> resource, you can override the verification wizard and designate
> >> >> >> the
> >> >> >> quorum
> >> >> >> disk manually. I have had that problem in the past when there were
> >> >> >> many
> >> >> >> disks presented to the host nodes. Once the node is added to the
> >> >> >> cluster,
> >> >> >> the drives map correctly.
> >> >> >>
> >> >> >> Geoff N. Hiten
> >> >> >> Senior Database Administrator
> >> >> >> Microsoft SQL Server MVP.
> >> >> >>
> >> >> >> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> >> >> >> news:41E599C0-E0CC-4258-B992-7B11B8D49ADA@.microsoft.com...
> >> >> >> > Guys
> >> >> >> > I have a cluster running on single node and i am trying to add
> >> >> >> > the
> >> >> >> > 2nd
> >> >> >> > node
> >> >> >> > but getting this error. Any idea? I am using external EMC storage
> >> >> >> > for
> >> >> >> > the
> >> >> >> > physical disks.
> >> >> >> > The only different i could see is, in node 1, the mapping of
> >> >> >> > disks
> >> >> >> > in
> >> >> >> > disk
> >> >> >> > mgmt are different from node 2. Example (Q drive [1G] is in disk
> >> >> >> > 1
> >> >> >> > in
> >> >> >> > node
> >> >> >> > 1
> >> >> >> > while the 1G disk is mapped in disk in node 2. Cauld that be the
> >> >> >> > reason?
> >> >> >> > If
> >> >> >> > yes, Can i change the sequence? How?
> >> >> >> > TIA
> >> >> >> >
> >> >> >> > ************************************************************
> >> >> >> > [INFO] CLUSTER001: Checking that all nodes have access to the
> >> >> >> > quorum
> >> >> >> > resource...
> >> >> >> >
> >> >> >> > [INFO] CLUSTER001: Checking that all nodes have access to the
> >> >> >> > quorum
> >> >> >> > resource...
> >> >> >> >
> >> >> >> > [INFO] CLUSTER001: The following nodes cannot not verify that
> >> >> >> > they
> >> >> >> > can
> >> >> >> > host
> >> >> >> > the quorum resource...
> >> >> >> >
> >> >> >> > [ERR ] CLUSTER001: Could not verify that node "SERVER001" can
> >> >> >> > host
> >> >> >> > the
> >> >> >> > quorum resource. Ensure that your hardware is properly configured
> >> >> >> > and
> >> >> >> > that
> >> >> >> > all nodes have access to a quorum-capable resource.
> >> >> >> >
> >> >> >> > [INFO] CLUSTER001: Checking that all nodes have access to the
> >> >> >> > quorum
> >> >> >> > resource...
> >> >> >> >
> >> >> >> > [ERR ] CLUSTER001: A multi-node cluster cannot be created because
> >> >> >> > there
> >> >> >> > is
> >> >> >> > not a quorum-capable resource common to all nodes. In some
> >> >> >> > complex
> >> >> >> > storage
> >> >> >> > solutions, such as a fiber channel switched fabric, a particular
> >> >> >> > storage
> >> >> >> > unit
> >> >> >> > might have a different identity (Target ID and/or LUN) on each
> >> >> >> > computer
> >> >> >> > in
> >> >> >> > the cluster. Although this is a valid storage configuration, it
> >> >> >> > violates
> >> >> >> > the
> >> >> >> > storage validation heuristics in the Add Nodes Wizard when using
> >> >> >> > the
> >> >> >> > default
> >> >> >> > Typical (full) configuration option, resulting in an error.
> >> >> >> > ************************************************************
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||BOL is SQL Server Books OnLine, the documentation that comes with SQL Server.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:F26E7D76-71C2-4FF6-B913-B0D6EB852DCB@.microsoft.com...
> hi Tom,
> is BOL=beginning of line? i cant see any link or reference or does BOL means
> sth else...
> "Tom Moreau" wrote:
>> Check out "How to add nodes to an existing virtual server" in the BOL.
>> Also, once that is done, install the service pack on the *new* node, while
>> the SQL group is running on the *existing* node.
>> --
>> Tom
>> ----
>> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
>> SQL Server MVP
>> Columnist, SQL Server Professional
>> Toronto, ON Canada
>> www.pinpub.com
>> "rupart" <rupart@.discussions.microsoft.com> wrote in message
>> news:8FD9E670-66DC-4540-8829-8A438FF2AE5C@.microsoft.com...
>> > hi Geoff,
>> > Actually mine is SQL cluster. Right now 2nd node does not have the SQL
>> > binaries. How do i get them installed? Today we had power trip and used
>> > that
>> > opportunity to do failover. Q failover as expected but not the sql cluster
>> > binaries because i just relaized the 2nd node doesnt have the binaries. If
>> > we
>> > used wizard, it shd have done that(i mean rebuilding the sql) for us. But
>> > how
>> > abt in this case? How to do manually? or any other way?
>> > thanks a lot again
>> >
>> > "Geoff N. Hiten" wrote:
>> >
>> >> If it won't fail over correctly, you will likely have to use Access Logix
>> >> to
>> >> logically disconnect all the disks from the host computer at the EMC
>> >> level.
>> >> You can then present them back to the host node in the correct order one
>> >> at
>> >> a time.
>> >>
>> >> This exact thing has happened to me before. I had over 10 clustered
>> >> disks
>> >> and the wizard couldn't figure out which one was the Quorum. I manually
>> >> designated it and everything then matched right up.
>> >>
>> >> --
>> >> Geoff N. Hiten
>> >> Senior Database Administrator
>> >> Microsoft SQL Server MVP
>> >>
>> >> "rupart" <rupart@.discussions.microsoft.com> wrote in message
>> >> news:BDE8B45A-42B4-413E-9102-9C539EE5B8FF@.microsoft.com...
>> >> > hi Geoff,
>> >> > thank you..let me try when i get the downtime.if it still fails, what
>> >> > can
>> >> > i
>> >> > do to correct the thing?thanks again
>> >> >
>> >> > "Geoff N. Hiten" wrote:
>> >> >
>> >> >> You did exactly what I suggested. Worst case, SQL won't start due to
>> >> >> inability to find the files and it will fail back to the first node
>> >> >> with
>> >> >> data intact. I doubt this will happen as the cluster services use disk
>> >> >> signatures to positively ID each disk.
>> >> >>
>> >> >> I would wait until a scheduled maintenance window to try a failover,
>> >> >> just
>> >> >> so
>> >> >> you don't have to explain excessive downtime..
>> >> >>
>> >> >> --
>> >> >> Geoff N. Hiten
>> >> >> Senior Database Administrator
>> >> >> Microsoft SQL Server MVP
>> >> >>
>> >> >> "rupart" <rupart@.discussions.microsoft.com> wrote in message
>> >> >> news:92121BBB-5AC8-4B9C-9C32-A7650116F3B7@.microsoft.com...
>> >> >> > hi Geoff,
>> >> >> > Sorry i was bit unlcear in explaining my current config in earlier
>> >> >> > msgs.
>> >> >> > What i am trying to say was
>> >> >> > in node 1, in disk mgmt, Q drive is mapped in disk 1
>> >> >> > in node 2, in disk mgmt, Q drive is mapped to disk 4
>> >> >> >
>> >> >> > Anyway,
>> >> >> > In your reply, "override verification wizard" does it mean
>> >> >> > disabling
>> >> >> > the
>> >> >> > heauristic scanning and join the node first? I have joined the
>> >> >> > cluster
>> >> >> > using
>> >> >> > minimum config and skipping the verification process. Now, 2nd node
>> >> >> > is
>> >> >> > in
>> >> >> > cluster and all the disks a hold by 1st node. I wanted to try doing
>> >> >> > failover
>> >> >> > but my worries are it's in production and i afraid the incorrect
>> >> >> > mapping
>> >> >> > may
>> >> >> > corrupt the data if i do failover. What you think?
>> >> >> >
>> >> >> >
>> >> >> > "Geoff N. Hiten" wrote:
>> >> >> >
>> >> >> >> As long as you are absolutely sure which disk resource is the
>> >> >> >> Quorum
>> >> >> >> resource, you can override the verification wizard and designate
>> >> >> >> the
>> >> >> >> quorum
>> >> >> >> disk manually. I have had that problem in the past when there were
>> >> >> >> many
>> >> >> >> disks presented to the host nodes. Once the node is added to the
>> >> >> >> cluster,
>> >> >> >> the drives map correctly.
>> >> >> >>
>> >> >> >> Geoff N. Hiten
>> >> >> >> Senior Database Administrator
>> >> >> >> Microsoft SQL Server MVP.
>> >> >> >>
>> >> >> >> "rupart" <rupart@.discussions.microsoft.com> wrote in message
>> >> >> >> news:41E599C0-E0CC-4258-B992-7B11B8D49ADA@.microsoft.com...
>> >> >> >> > Guys
>> >> >> >> > I have a cluster running on single node and i am trying to add
>> >> >> >> > the
>> >> >> >> > 2nd
>> >> >> >> > node
>> >> >> >> > but getting this error. Any idea? I am using external EMC storage
>> >> >> >> > for
>> >> >> >> > the
>> >> >> >> > physical disks.
>> >> >> >> > The only different i could see is, in node 1, the mapping of
>> >> >> >> > disks
>> >> >> >> > in
>> >> >> >> > disk
>> >> >> >> > mgmt are different from node 2. Example (Q drive [1G] is in disk
>> >> >> >> > 1
>> >> >> >> > in
>> >> >> >> > node
>> >> >> >> > 1
>> >> >> >> > while the 1G disk is mapped in disk in node 2. Cauld that be the
>> >> >> >> > reason?
>> >> >> >> > If
>> >> >> >> > yes, Can i change the sequence? How?
>> >> >> >> > TIA
>> >> >> >> >
>> >> >> >> > ************************************************************
>> >> >> >> > [INFO] CLUSTER001: Checking that all nodes have access to the
>> >> >> >> > quorum
>> >> >> >> > resource...
>> >> >> >> >
>> >> >> >> > [INFO] CLUSTER001: Checking that all nodes have access to the
>> >> >> >> > quorum
>> >> >> >> > resource...
>> >> >> >> >
>> >> >> >> > [INFO] CLUSTER001: The following nodes cannot not verify that
>> >> >> >> > they
>> >> >> >> > can
>> >> >> >> > host
>> >> >> >> > the quorum resource...
>> >> >> >> >
>> >> >> >> > [ERR ] CLUSTER001: Could not verify that node "SERVER001" can
>> >> >> >> > host
>> >> >> >> > the
>> >> >> >> > quorum resource. Ensure that your hardware is properly configured
>> >> >> >> > and
>> >> >> >> > that
>> >> >> >> > all nodes have access to a quorum-capable resource.
>> >> >> >> >
>> >> >> >> > [INFO] CLUSTER001: Checking that all nodes have access to the
>> >> >> >> > quorum
>> >> >> >> > resource...
>> >> >> >> >
>> >> >> >> > [ERR ] CLUSTER001: A multi-node cluster cannot be created because
>> >> >> >> > there
>> >> >> >> > is
>> >> >> >> > not a quorum-capable resource common to all nodes. In some
>> >> >> >> > complex
>> >> >> >> > storage
>> >> >> >> > solutions, such as a fiber channel switched fabric, a particular
>> >> >> >> > storage
>> >> >> >> > unit
>> >> >> >> > might have a different identity (Target ID and/or LUN) on each
>> >> >> >> > computer
>> >> >> >> > in
>> >> >> >> > the cluster. Although this is a valid storage configuration, it
>> >> >> >> > violates
>> >> >> >> > the
>> >> >> >> > storage validation heuristics in the Add Nodes Wizard when using
>> >> >> >> > the
>> >> >> >> > default
>> >> >> >> > Typical (full) configuration option, resulting in an error.
>> >> >> >> > ************************************************************
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
