General (simple!) Questions

#1

For a 2 node cluster, does the "preferred owner" have any meaning?
Under what setting does the cluster automatically failback once the failed
node is restored?
Why are domain groups required in SQL 2005 installation rather than accounts?
When administering the virtual server, should I use the cluster name or the
virtual server name to connect?
I have read that 4 failures will cause a failover - is this counter
cumulative over all time or is it reset?
Many thanks.

#2

Answers Inline

"JB" <JB (AT) discussions (DOT) microsoft.com> wrote

Quote:

For a 2 node cluster, does the "preferred owner" have any meaning?
Not so much for SQL unless you have failback enabled.
Under what setting does the cluster automatically failback once the failed
node is restored?

Failback enabled will move SQL back to the first node in the preferred owner
list.

Quote:

Why are domain groups required in SQL 2005 installation rather than
accounts?

So you can change service accounts without killing cluster functionality.
The account does not carry the permissions, the group does.

Quote:

When administering the virtual server, should I use the cluster name or
the
virtual server name to connect?
Cluster-name for managing the cluster. Virtual Server name for managing the

instance.

Quote:

I have read that 4 failures will cause a failover - is this counter
cumulative over all time or is it reset?
We have two concepts here and I am not sure which you mean. Instance

failover happens after a certain number of LooksAlive and IsAlive failures
within a given time period. Instance failure occurs if a certain number of
failovers happen within a given time period. The actual numbers for events
and times are adjustable. The short answer is that the counters do reset in
both cases.

Quote:

Many thanks.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

#3

Answers Inline

"JB" <JB (AT) discussions (DOT) microsoft.com> wrote

Quote:

For a 2 node cluster, does the "preferred owner" have any meaning?
Not so much for SQL unless you have failback enabled.
Under what setting does the cluster automatically failback once the failed
node is restored?

Failback enabled will move SQL back to the first node in the preferred owner
list.

Quote:

Why are domain groups required in SQL 2005 installation rather than
accounts?

So you can change service accounts without killing cluster functionality.
The account does not carry the permissions, the group does.

Quote:

When administering the virtual server, should I use the cluster name or
the
virtual server name to connect?
Cluster-name for managing the cluster. Virtual Server name for managing the

instance.

Quote:

I have read that 4 failures will cause a failover - is this counter
cumulative over all time or is it reset?
We have two concepts here and I am not sure which you mean. Instance

failover happens after a certain number of LooksAlive and IsAlive failures
within a given time period. Instance failure occurs if a certain number of
failovers happen within a given time period. The actual numbers for events
and times are adjustable. The short answer is that the counters do reset in
both cases.

Quote:

Many thanks.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

#4

Answers Inline

"JB" <JB (AT) discussions (DOT) microsoft.com> wrote

Quote:

For a 2 node cluster, does the "preferred owner" have any meaning?
Not so much for SQL unless you have failback enabled.
Under what setting does the cluster automatically failback once the failed
node is restored?

Failback enabled will move SQL back to the first node in the preferred owner
list.

Quote:

Why are domain groups required in SQL 2005 installation rather than
accounts?

So you can change service accounts without killing cluster functionality.
The account does not carry the permissions, the group does.

Quote:

When administering the virtual server, should I use the cluster name or
the
virtual server name to connect?
Cluster-name for managing the cluster. Virtual Server name for managing the

instance.

Quote:

I have read that 4 failures will cause a failover - is this counter
cumulative over all time or is it reset?
We have two concepts here and I am not sure which you mean. Instance

failover happens after a certain number of LooksAlive and IsAlive failures
within a given time period. Instance failure occurs if a certain number of
failovers happen within a given time period. The actual numbers for events
and times are adjustable. The short answer is that the counters do reset in
both cases.

Quote:

Many thanks.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

#5

Answers Inline

"JB" <JB (AT) discussions (DOT) microsoft.com> wrote

Quote:

For a 2 node cluster, does the "preferred owner" have any meaning?
Not so much for SQL unless you have failback enabled.
Under what setting does the cluster automatically failback once the failed
node is restored?

Failback enabled will move SQL back to the first node in the preferred owner
list.

Quote:

Why are domain groups required in SQL 2005 installation rather than
accounts?

So you can change service accounts without killing cluster functionality.
The account does not carry the permissions, the group does.

Quote:

When administering the virtual server, should I use the cluster name or
the
virtual server name to connect?
Cluster-name for managing the cluster. Virtual Server name for managing the

instance.

Quote:

I have read that 4 failures will cause a failover - is this counter
cumulative over all time or is it reset?
We have two concepts here and I am not sure which you mean. Instance

failover happens after a certain number of LooksAlive and IsAlive failures
within a given time period. Instance failure occurs if a certain number of
failovers happen within a given time period. The actual numbers for events
and times are adjustable. The short answer is that the counters do reset in
both cases.

Quote:

Many thanks.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

#6

Answers Inline

"JB" <JB (AT) discussions (DOT) microsoft.com> wrote

Quote:

For a 2 node cluster, does the "preferred owner" have any meaning?
Not so much for SQL unless you have failback enabled.
Under what setting does the cluster automatically failback once the failed
node is restored?

Failback enabled will move SQL back to the first node in the preferred owner
list.

Quote:

Why are domain groups required in SQL 2005 installation rather than
accounts?

So you can change service accounts without killing cluster functionality.
The account does not carry the permissions, the group does.

Quote:

When administering the virtual server, should I use the cluster name or
the
virtual server name to connect?
Cluster-name for managing the cluster. Virtual Server name for managing the

instance.

Quote:

I have read that 4 failures will cause a failover - is this counter
cumulative over all time or is it reset?
We have two concepts here and I am not sure which you mean. Instance

failover happens after a certain number of LooksAlive and IsAlive failures
within a given time period. Instance failure occurs if a certain number of
failovers happen within a given time period. The actual numbers for events
and times are adjustable. The short answer is that the counters do reset in
both cases.

Quote:

Many thanks.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

#7

Answers Inline

"JB" <JB (AT) discussions (DOT) microsoft.com> wrote

Quote:

For a 2 node cluster, does the "preferred owner" have any meaning?
Not so much for SQL unless you have failback enabled.
Under what setting does the cluster automatically failback once the failed
node is restored?

Failback enabled will move SQL back to the first node in the preferred owner
list.

Quote:

Why are domain groups required in SQL 2005 installation rather than
accounts?

So you can change service accounts without killing cluster functionality.
The account does not carry the permissions, the group does.

Quote:

When administering the virtual server, should I use the cluster name or
the
virtual server name to connect?
Cluster-name for managing the cluster. Virtual Server name for managing the

instance.

Quote:

I have read that 4 failures will cause a failover - is this counter
cumulative over all time or is it reset?
We have two concepts here and I am not sure which you mean. Instance

failover happens after a certain number of LooksAlive and IsAlive failures
within a given time period. Instance failure occurs if a certain number of
failovers happen within a given time period. The actual numbers for events
and times are adjustable. The short answer is that the counters do reset in
both cases.

Quote:

Many thanks.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

#8

Answers Inline

"JB" <JB (AT) discussions (DOT) microsoft.com> wrote

Quote:

For a 2 node cluster, does the "preferred owner" have any meaning?
Not so much for SQL unless you have failback enabled.
Under what setting does the cluster automatically failback once the failed
node is restored?

Failback enabled will move SQL back to the first node in the preferred owner
list.

Quote:

Why are domain groups required in SQL 2005 installation rather than
accounts?

So you can change service accounts without killing cluster functionality.
The account does not carry the permissions, the group does.

Quote:

When administering the virtual server, should I use the cluster name or
the
virtual server name to connect?
Cluster-name for managing the cluster. Virtual Server name for managing the

instance.

Quote:

I have read that 4 failures will cause a failover - is this counter
cumulative over all time or is it reset?
We have two concepts here and I am not sure which you mean. Instance

failover happens after a certain number of LooksAlive and IsAlive failures
within a given time period. Instance failure occurs if a certain number of
failovers happen within a given time period. The actual numbers for events
and times are adjustable. The short answer is that the counters do reset in
both cases.

Quote:

Many thanks.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

#9

Answers Inline

"JB" <JB (AT) discussions (DOT) microsoft.com> wrote

Quote:

For a 2 node cluster, does the "preferred owner" have any meaning?
Not so much for SQL unless you have failback enabled.
Under what setting does the cluster automatically failback once the failed
node is restored?

Failback enabled will move SQL back to the first node in the preferred owner
list.

Quote:

Why are domain groups required in SQL 2005 installation rather than
accounts?

So you can change service accounts without killing cluster functionality.
The account does not carry the permissions, the group does.

Quote:

When administering the virtual server, should I use the cluster name or
the
virtual server name to connect?
Cluster-name for managing the cluster. Virtual Server name for managing the

instance.

Quote:

I have read that 4 failures will cause a failover - is this counter
cumulative over all time or is it reset?
We have two concepts here and I am not sure which you mean. Instance

failover happens after a certain number of LooksAlive and IsAlive failures
within a given time period. Instance failure occurs if a certain number of
failovers happen within a given time period. The actual numbers for events
and times are adjustable. The short answer is that the counters do reset in
both cases.

Quote:

Many thanks.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP

#10

Answers Inline

"JB" <JB (AT) discussions (DOT) microsoft.com> wrote

Quote:

For a 2 node cluster, does the "preferred owner" have any meaning?
Not so much for SQL unless you have failback enabled.
Under what setting does the cluster automatically failback once the failed
node is restored?

Failback enabled will move SQL back to the first node in the preferred owner
list.

Quote:

Why are domain groups required in SQL 2005 installation rather than
accounts?

So you can change service accounts without killing cluster functionality.
The account does not carry the permissions, the group does.

Quote:

When administering the virtual server, should I use the cluster name or
the
virtual server name to connect?
Cluster-name for managing the cluster. Virtual Server name for managing the

instance.

Quote:

I have read that 4 failures will cause a failover - is this counter
cumulative over all time or is it reset?
We have two concepts here and I am not sure which you mean. Instance

failover happens after a certain number of LooksAlive and IsAlive failures
within a given time period. Instance failure occurs if a certain number of
failovers happen within a given time period. The actual numbers for events
and times are adjustable. The short answer is that the counters do reset in
both cases.

Quote:

Many thanks.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP