Hi,
I have an active-active SQL 2000 Cluster running on Server 2003. Both nodes
have a vanilla 2003 OS on them. I tried upgrading each nodes to a new custom
build (hotfixes, security templates, etc) and it broke both nodes after I
patched the first one. Any suggestions?
Most likely you broke a driver for your shared storage. Check with your
hardware vendor for cluster-certified drivers for the SCSI cards or HBAs.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:37204249-71C3-41A3-BF26-EA6463E3D662@.microsoft.com...
> Hi,
> I have an active-active SQL 2000 Cluster running on Server 2003. Both
> nodes
> have a vanilla 2003 OS on them. I tried upgrading each nodes to a new
> custom
> build (hotfixes, security templates, etc) and it broke both nodes after I
> patched the first one. Any suggestions?
|||Thanks. Any idea if there is a best practices guide for fail over cluster
maintenance?
"Geoff N. Hiten" wrote:
> Most likely you broke a driver for your shared storage. Check with your
> hardware vendor for cluster-certified drivers for the SCSI cards or HBAs.
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:37204249-71C3-41A3-BF26-EA6463E3D662@.microsoft.com...
>
>
|||Thanks. Any idea if there is a best practices guide for fail over cluster
maintenance?
Jay
"Geoff N. Hiten" wrote:
> Most likely you broke a driver for your shared storage. Check with your
> hardware vendor for cluster-certified drivers for the SCSI cards or HBAs.
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:37204249-71C3-41A3-BF26-EA6463E3D662@.microsoft.com...
>
>
|||Try these. Although a good document throughout, there are two sections
worth noting in your case, Maintenance and Troubleshooting.
SQL Server 2000 Failover Clustering
http://www.microsoft.com/technet/pro.../failclus.mspx
Maintaining a SQL Server 2000 Failover Cluster
http://www.microsoft.com/technet/pro...clus.mspx#EIAA
Troubleshooting SQL Server 2000 Failover Clusters
http://www.microsoft.com/technet/pro...clus.mspx#EHAA
Also, for "rolling upgrades," these are worth a look.
Rolling Upgrades
http://www.microsoft.com/technet/pro...ff977ef91.mspx
Restrictions on rolling upgrades
http://www.microsoft.com/technet/pro...f300fcd61.mspx
Good luck.
Sincerely,
Anthony Thomas
"jay d" <jayd@.discussions.microsoft.com> wrote in message
news:C2404898-825C-4841-B2E4-9815FF0A9378@.microsoft.com...
Thanks. Any idea if there is a best practices guide for fail over cluster
maintenance?
"Geoff N. Hiten" wrote:
[vbcol=seagreen]
> Most likely you broke a driver for your shared storage. Check with your
> hardware vendor for cluster-certified drivers for the SCSI cards or HBAs.
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
> "jay d" <jayd@.discussions.microsoft.com> wrote in message
> news:37204249-71C3-41A3-BF26-EA6463E3D662@.microsoft.com...
I
>
>
Showing posts with label cluster. Show all posts
Showing posts with label cluster. Show all posts
Tuesday, March 20, 2012
Monday, March 12, 2012
patch application procedure
Hi,
I am having an mssql server with sp3. It is in sql cluster
(NT) as well as it participates in replication (merge). My
comany is very paranoid about doing things and all the
more there is no testing environment. Could any one please
explain how to apply SP4 for this server? We need to
consider the problematic conditions and disaster recovery
as well. My recovery mode is set to full.
james bond...-- james bond wrote: --
> Hi,
>> I am having an mssql server with sp3. It is in sql cluster
> (NT) as well as it participates in replication (merge). My
> company is very paranoid about doing things and all the
> more there is no testing environment. Could any one please
> explain how to apply SP4 for this server? We need to
> consider the problematic conditions and disaster recovery
> as well. My recovery mode is set to full.
--
Hi James Bond,
The best source of information for a service pack install is the README.htm of the service pack itself.
Hope this helps,
-Eric Cárdenas
SQL Server support
I am having an mssql server with sp3. It is in sql cluster
(NT) as well as it participates in replication (merge). My
comany is very paranoid about doing things and all the
more there is no testing environment. Could any one please
explain how to apply SP4 for this server? We need to
consider the problematic conditions and disaster recovery
as well. My recovery mode is set to full.
james bond...-- james bond wrote: --
> Hi,
>> I am having an mssql server with sp3. It is in sql cluster
> (NT) as well as it participates in replication (merge). My
> company is very paranoid about doing things and all the
> more there is no testing environment. Could any one please
> explain how to apply SP4 for this server? We need to
> consider the problematic conditions and disaster recovery
> as well. My recovery mode is set to full.
--
Hi James Bond,
The best source of information for a service pack install is the README.htm of the service pack itself.
Hope this helps,
-Eric Cárdenas
SQL Server support
Passwords for cluster and servers
I have a 2 node cluster running Win2000 enterprise and MS clustering.
Also SQL server. Would there be a problem using the same domain
password for SQL and for the clustering service? I thought I read
that there may be a problem but I don't recall where it read it.
Thanks for any help.
I'm using one domain account for SQL and Cluster services and I have no
problems.
Ayad Shammout
SR.DBA/Analyst
Caregroup IS
"Dave" <mine@.none.com> wrote in message
news:foam11pg95kfd57jefn88eou8o160kc3r1@.4ax.com...
> I have a 2 node cluster running Win2000 enterprise and MS clustering.
> Also SQL server. Would there be a problem using the same domain
> password for SQL and for the clustering service? I thought I read
> that there may be a problem but I don't recall where it read it.
> Thanks for any help.
>
|||im using 1 account for cluster and sql services, havent had any issues to
date...
"Dave" <mine@.none.com> wrote in message
news:foam11pg95kfd57jefn88eou8o160kc3r1@.4ax.com...
> I have a 2 node cluster running Win2000 enterprise and MS clustering.
> Also SQL server. Would there be a problem using the same domain
> password for SQL and for the clustering service? I thought I read
> that there may be a problem but I don't recall where it read it.
> Thanks for any help.
>
|||I don't think there's a functional issue, but if you use the same account,
the domain admins will be able to log on to SQL Server as an SA. If you use
separate accounts, you can set the cluster account to have minimal SQL
privledges so the keep alive for SQL will work and not give the domain
admins sa access to the database. In a small environment using the same
account is probably no big deal, but in a larger enterprise it could be.
"Dave" <mine@.none.com> wrote in message
news:foam11pg95kfd57jefn88eou8o160kc3r1@.4ax.com...
> I have a 2 node cluster running Win2000 enterprise and MS clustering.
> Also SQL server. Would there be a problem using the same domain
> password for SQL and for the clustering service? I thought I read
> that there may be a problem but I don't recall where it read it.
> Thanks for any help.
>
|||If you do not want the domain admins to be admins of sql then remove
buildin/admin group, create your own group "Sql Admins" add users who need
admin to sql and add that.
apart for that , using same cluster and sql login is not a prob
"Al" <al@.nospam.com> wrote in message
news:OBnYmUVGFHA.1836@.tk2msftngp13.phx.gbl...
> I don't think there's a functional issue, but if you use the same account,
> the domain admins will be able to log on to SQL Server as an SA. If you
use
> separate accounts, you can set the cluster account to have minimal SQL
> privledges so the keep alive for SQL will work and not give the domain
> admins sa access to the database. In a small environment using the same
> account is probably no big deal, but in a larger enterprise it could be.
> "Dave" <mine@.none.com> wrote in message
> news:foam11pg95kfd57jefn88eou8o160kc3r1@.4ax.com...
>
Also SQL server. Would there be a problem using the same domain
password for SQL and for the clustering service? I thought I read
that there may be a problem but I don't recall where it read it.
Thanks for any help.
I'm using one domain account for SQL and Cluster services and I have no
problems.
Ayad Shammout
SR.DBA/Analyst
Caregroup IS
"Dave" <mine@.none.com> wrote in message
news:foam11pg95kfd57jefn88eou8o160kc3r1@.4ax.com...
> I have a 2 node cluster running Win2000 enterprise and MS clustering.
> Also SQL server. Would there be a problem using the same domain
> password for SQL and for the clustering service? I thought I read
> that there may be a problem but I don't recall where it read it.
> Thanks for any help.
>
|||im using 1 account for cluster and sql services, havent had any issues to
date...
"Dave" <mine@.none.com> wrote in message
news:foam11pg95kfd57jefn88eou8o160kc3r1@.4ax.com...
> I have a 2 node cluster running Win2000 enterprise and MS clustering.
> Also SQL server. Would there be a problem using the same domain
> password for SQL and for the clustering service? I thought I read
> that there may be a problem but I don't recall where it read it.
> Thanks for any help.
>
|||I don't think there's a functional issue, but if you use the same account,
the domain admins will be able to log on to SQL Server as an SA. If you use
separate accounts, you can set the cluster account to have minimal SQL
privledges so the keep alive for SQL will work and not give the domain
admins sa access to the database. In a small environment using the same
account is probably no big deal, but in a larger enterprise it could be.
"Dave" <mine@.none.com> wrote in message
news:foam11pg95kfd57jefn88eou8o160kc3r1@.4ax.com...
> I have a 2 node cluster running Win2000 enterprise and MS clustering.
> Also SQL server. Would there be a problem using the same domain
> password for SQL and for the clustering service? I thought I read
> that there may be a problem but I don't recall where it read it.
> Thanks for any help.
>
|||If you do not want the domain admins to be admins of sql then remove
buildin/admin group, create your own group "Sql Admins" add users who need
admin to sql and add that.
apart for that , using same cluster and sql login is not a prob
"Al" <al@.nospam.com> wrote in message
news:OBnYmUVGFHA.1836@.tk2msftngp13.phx.gbl...
> I don't think there's a functional issue, but if you use the same account,
> the domain admins will be able to log on to SQL Server as an SA. If you
use
> separate accounts, you can set the cluster account to have minimal SQL
> privledges so the keep alive for SQL will work and not give the domain
> admins sa access to the database. In a small environment using the same
> account is probably no big deal, but in a larger enterprise it could be.
> "Dave" <mine@.none.com> wrote in message
> news:foam11pg95kfd57jefn88eou8o160kc3r1@.4ax.com...
>
Subscribe to:
Posts (Atom)