Strange issue... I have a 2-node SQL Server 2000 Cluster with SP4
applied. Everything works fine but the Veritas BackupExec program can't
find the SQL Server. When I use Computer Management to connect to the
cluster by the cluster name (and also to the active node of the
cluster), I only found "no items" under Service and Applications -
Microsoft SQL Servers. Guess that is for the same reason that Veritas
can't see SQL Server.
Anyone has any idea what this is? Thanks a bunch!
You have to connect to the virtual SQL Server name, not the cluster name. I
prefer backing up directly to a disk share and then backing up those files
to tape for longer term archive. Veritas does not implement the full
restore functionality of SQL Server.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"maoji" <mr.maoji@.gmail.com> wrote in message
news:1136980331.777473.245220@.o13g2000cwo.googlegr oups.com...
> Strange issue... I have a 2-node SQL Server 2000 Cluster with SP4
> applied. Everything works fine but the Veritas BackupExec program can't
> find the SQL Server. When I use Computer Management to connect to the
> cluster by the cluster name (and also to the active node of the
> cluster), I only found "no items" under Service and Applications -
> Microsoft SQL Servers. Guess that is for the same reason that Veritas
> can't see SQL Server.
> Anyone has any idea what this is? Thanks a bunch!
>
|||Thanks Geoff. Maybe I didn't make myself clear. I am connecting to the
SQL Server Cluster name instead of the Windows cluster name.
I've been using Veritas to backup our databases and I found it works ok
with me. Anyway, being not able to see the SQL resource in Computer
Management is weird, isn't it? There could be other problems in the
future. I just want to make sure this key database application works
all fine along the way.
Geoff N. Hiten wrote:[vbcol=seagreen]
> You have to connect to the virtual SQL Server name, not the cluster name. I
> prefer backing up directly to a disk share and then backing up those files
> to tape for longer term archive. Veritas does not implement the full
> restore functionality of SQL Server.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "maoji" <mr.maoji@.gmail.com> wrote in message
> news:1136980331.777473.245220@.o13g2000cwo.googlegr oups.com...
|||I just tried on two of our SQL Clusters and I connected to the controlling
node just fine. I was able to see Services and Applications just fine. Great
question, since I have not tried doing this before. I wonder if you don't
have a Group Policy Object blocking you or a firewall?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
"maoji" <mr.maoji@.gmail.com> wrote in message
news:1136991184.533925.133310@.z14g2000cwz.googlegr oups.com...
> Thanks Geoff. Maybe I didn't make myself clear. I am connecting to the
> SQL Server Cluster name instead of the Windows cluster name.
> I've been using Veritas to backup our databases and I found it works ok
> with me. Anyway, being not able to see the SQL resource in Computer
> Management is weird, isn't it? There could be other problems in the
> future. I just want to make sure this key database application works
> all fine along the way.
>
> Geoff N. Hiten wrote:
>
|||Thanks everyone. It turns out to be all my fault.
After the successful setup of the SQL Cluster, I tried to rename the
SQL Cluster to another name in order to invisiblly replace another SQL
Server in our network. During that process I changed one of the
registry entries to use the new name, besides changing the SQL cluster
name in Cluster Administration console. And later on I found it was not
so easy as I thought and I changed the SQL server cluster name back in
the CA console, but forgot to change the registry back.
After changing the registry entry back everything is OK.
Thanks everyone! My bad, my bad. Have a good day!
Rodney R. Fournier [MVP] wrote:[vbcol=seagreen]
> I just tried on two of our SQL Clusters and I connected to the controlling
> node just fine. I was able to see Services and Applications just fine. Great
> question, since I have not tried doing this before. I wonder if you don't
> have a Group Policy Object blocking you or a firewall?
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> "maoji" <mr.maoji@.gmail.com> wrote in message
> news:1136991184.533925.133310@.z14g2000cwz.googlegr oups.com...
sql
Showing posts with label cluster. Show all posts
Showing posts with label cluster. Show all posts
Friday, March 30, 2012
Friday, March 23, 2012
No data in Data Mining cube.
Hi,
I've created a Cluster data mining model and seems to correctly return data. However I've created a data mining dimension and cube but when I go to query the cube it doesn't return any data if I select any members on the data mining dimension. Any suggestions to where I can look to resolve this?
Thanks
Sanjay
Hi,
I found out how to see the data in the cube. I was using the data mining dimension in relation with the dimension it was based on. So now I can see data for the years that I've trained my model on. Is there anyway to make the cube predict the values for the other years in the cube with data?
Thanks
Sanjay
|||Are you saying that for example you've created a cluster model on a set of items, and you want to see the cluster values for items not in the set? And you want the slicing behavior to work against those values as well?
If this is the case, unfortunately, that's not the way it works. The cluster dimension is only on the cases for which it was trained. You could apply the clustering to the data outside the cube, write the results to a table and process it as a regular dimension, though.
|||Hi,
Ideally yes. For example if I generate a cluster model and train it with a couple of years data, potentially I would then like to use the data mining dimension and cube to predict or classify the current years data. I will look to use your suggestion.
Thanks
Sanjay
Wednesday, March 21, 2012
No Cluster to Cluster
We are going through a process of clustering windows 2000 & sql 2000. We
currently are running windows 2000 server & sql 2000 on a single server,
non-clustered of course. We have the procedures down for creating the
windows cluster and then the sql cluster, but have questions as to migrating
the existing sql data from the non-clustered hardware currently in use. Are
there any items to be aware of when moving sql data from a non-clustered
setup to a clustered setup? Does anyone have a recommendation for some
articles on the best practice to move the sql data to the cluster while
retaining logins, security, db maint plans, dts packages, and other sql
items?
TIA!
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
$
$ Nick Maxwell, MCSE 2k, CCNA , A+
$ Systems Engineer
$ Heartland Business Systems
$ http://www.hbs.net
$ nmaxwell@.nospam.hbs.net
$
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
The data/databases don't know or care if they are clustered. So you can
detach them from one machine and attach them to another with no problems.
However, you do need to be aware of these factors in a cluster:
* The databases (user and system) all have to be on a shared drive. If the
drive letter of that drive is different from the drive letter of the
originating instance, you have to take some extra steps which are outlined
in the KB article 314546 HOW TO: Move Databases Between Computers That Are
Running SQL Server http://support.microsoft.com/?id=314546.
* The SQL Server resource must be dependent on any drive with SQL Server
data or backups.
* If you plan to upgrade the existing instance to a clustered instance, you
can do so using setup as long as the data is already moved to a shared
drive. So create the Windows cluster, add a shared drive in its own group
that you plan to use for SQL Server, move all databases to that drive, then
run SQL Enterprise Edition setup to upgrade to a virtual server.
* If the virtual server name is different than the original server name,
run sp_dropserver/sp_addserver (local) to get @.@.servername correct. Note
that this only works when moving databases, not for renaming an existing
virtual instance. To rename an existing virtual instance you have to
reinstall with the correct name to get all the registry keys updated
properly.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
currently are running windows 2000 server & sql 2000 on a single server,
non-clustered of course. We have the procedures down for creating the
windows cluster and then the sql cluster, but have questions as to migrating
the existing sql data from the non-clustered hardware currently in use. Are
there any items to be aware of when moving sql data from a non-clustered
setup to a clustered setup? Does anyone have a recommendation for some
articles on the best practice to move the sql data to the cluster while
retaining logins, security, db maint plans, dts packages, and other sql
items?
TIA!
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
$
$ Nick Maxwell, MCSE 2k, CCNA , A+
$ Systems Engineer
$ Heartland Business Systems
$ http://www.hbs.net
$ nmaxwell@.nospam.hbs.net
$
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
The data/databases don't know or care if they are clustered. So you can
detach them from one machine and attach them to another with no problems.
However, you do need to be aware of these factors in a cluster:
* The databases (user and system) all have to be on a shared drive. If the
drive letter of that drive is different from the drive letter of the
originating instance, you have to take some extra steps which are outlined
in the KB article 314546 HOW TO: Move Databases Between Computers That Are
Running SQL Server http://support.microsoft.com/?id=314546.
* The SQL Server resource must be dependent on any drive with SQL Server
data or backups.
* If you plan to upgrade the existing instance to a clustered instance, you
can do so using setup as long as the data is already moved to a shared
drive. So create the Windows cluster, add a shared drive in its own group
that you plan to use for SQL Server, move all databases to that drive, then
run SQL Enterprise Edition setup to upgrade to a virtual server.
* If the virtual server name is different than the original server name,
run sp_dropserver/sp_addserver (local) to get @.@.servername correct. Note
that this only works when moving databases, not for renaming an existing
virtual instance. To rename an existing virtual instance you have to
reinstall with the correct name to get all the registry keys updated
properly.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Tuesday, March 20, 2012
NLB Web App accessing Cluster SQL 2005
Hello Friends
I have a project that will use Failover Cluster for SQL 2005 and NLB for the
web server front-end (using IIS).
That web application will be developed in-house. there are any special
programming considerations that the programmers must embed in the application
in order to support the special features of Failover and NLB clusters?
Does the web App Server must be Cluster-Aware to interact to SQL 2005
Failover Cluster?
Can you please give me any links to some documents that reflect these
situations?
Thanks for Help
Bruno
No. If it can connect to the SQL Server, you are set for the application.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Bruno" <Bruno@.discussions.microsoft.com> wrote in message
news:D6B04BF1-9730-46AA-A6E9-EBFC5C6B4C2D@.microsoft.com...
> Hello Friends
> I have a project that will use Failover Cluster for SQL 2005 and NLB for
> the
> web server front-end (using IIS).
> That web application will be developed in-house. there are any special
> programming considerations that the programmers must embed in the
> application
> in order to support the special features of Failover and NLB clusters?
> Does the web App Server must be Cluster-Aware to interact to SQL 2005
> Failover Cluster?
> Can you please give me any links to some documents that reflect these
> situations?
> Thanks for Help
> Bruno
|||Any SQL client application can connect to a SQL Cluster with no changes. I
recommend using non-persistent connections so the web app can recover in
case of a cluster failover, but that has been general programming practice
for a while now. Your NLB session model and the application session model
will need to work together. I.E. if you only support local sessions in IIS,
you will need to make sure your NLB sessions are "sticky". Your Network
Engineer can help with this.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Bruno" <Bruno@.discussions.microsoft.com> wrote in message
news:D6B04BF1-9730-46AA-A6E9-EBFC5C6B4C2D@.microsoft.com...
> Hello Friends
> I have a project that will use Failover Cluster for SQL 2005 and NLB for
> the
> web server front-end (using IIS).
> That web application will be developed in-house. there are any special
> programming considerations that the programmers must embed in the
> application
> in order to support the special features of Failover and NLB clusters?
> Does the web App Server must be Cluster-Aware to interact to SQL 2005
> Failover Cluster?
> Can you please give me any links to some documents that reflect these
> situations?
> Thanks for Help
> Bruno
|||You need to have reconnect logic built into the application. Whenever a
failover occurs, you will loose connectivity. The advantage of this
solution, however, is that the failover happens automatically, and is
relatively brief.
On the NLB, you need to program "stateless" apps. That is, you can not
guarantee that recovered session are redirect to the same web server during
each pass. If only one server is aware of the state, you find the user
orphaned if redirected to one of the other servers.
Also, to keep your solution clean and to harden security, consider using
some sort of middleware, either through dedicated application hosts, or some
sort of messaging platform.
Sincerely,
Anthony Thomas
"Bruno" <Bruno@.discussions.microsoft.com> wrote in message
news:D6B04BF1-9730-46AA-A6E9-EBFC5C6B4C2D@.microsoft.com...
> Hello Friends
> I have a project that will use Failover Cluster for SQL 2005 and NLB for
the
> web server front-end (using IIS).
> That web application will be developed in-house. there are any special
> programming considerations that the programmers must embed in the
application
> in order to support the special features of Failover and NLB clusters?
> Does the web App Server must be Cluster-Aware to interact to SQL 2005
> Failover Cluster?
> Can you please give me any links to some documents that reflect these
> situations?
> Thanks for Help
> Bruno
I have a project that will use Failover Cluster for SQL 2005 and NLB for the
web server front-end (using IIS).
That web application will be developed in-house. there are any special
programming considerations that the programmers must embed in the application
in order to support the special features of Failover and NLB clusters?
Does the web App Server must be Cluster-Aware to interact to SQL 2005
Failover Cluster?
Can you please give me any links to some documents that reflect these
situations?
Thanks for Help
Bruno
No. If it can connect to the SQL Server, you are set for the application.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Bruno" <Bruno@.discussions.microsoft.com> wrote in message
news:D6B04BF1-9730-46AA-A6E9-EBFC5C6B4C2D@.microsoft.com...
> Hello Friends
> I have a project that will use Failover Cluster for SQL 2005 and NLB for
> the
> web server front-end (using IIS).
> That web application will be developed in-house. there are any special
> programming considerations that the programmers must embed in the
> application
> in order to support the special features of Failover and NLB clusters?
> Does the web App Server must be Cluster-Aware to interact to SQL 2005
> Failover Cluster?
> Can you please give me any links to some documents that reflect these
> situations?
> Thanks for Help
> Bruno
|||Any SQL client application can connect to a SQL Cluster with no changes. I
recommend using non-persistent connections so the web app can recover in
case of a cluster failover, but that has been general programming practice
for a while now. Your NLB session model and the application session model
will need to work together. I.E. if you only support local sessions in IIS,
you will need to make sure your NLB sessions are "sticky". Your Network
Engineer can help with this.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Bruno" <Bruno@.discussions.microsoft.com> wrote in message
news:D6B04BF1-9730-46AA-A6E9-EBFC5C6B4C2D@.microsoft.com...
> Hello Friends
> I have a project that will use Failover Cluster for SQL 2005 and NLB for
> the
> web server front-end (using IIS).
> That web application will be developed in-house. there are any special
> programming considerations that the programmers must embed in the
> application
> in order to support the special features of Failover and NLB clusters?
> Does the web App Server must be Cluster-Aware to interact to SQL 2005
> Failover Cluster?
> Can you please give me any links to some documents that reflect these
> situations?
> Thanks for Help
> Bruno
|||You need to have reconnect logic built into the application. Whenever a
failover occurs, you will loose connectivity. The advantage of this
solution, however, is that the failover happens automatically, and is
relatively brief.
On the NLB, you need to program "stateless" apps. That is, you can not
guarantee that recovered session are redirect to the same web server during
each pass. If only one server is aware of the state, you find the user
orphaned if redirected to one of the other servers.
Also, to keep your solution clean and to harden security, consider using
some sort of middleware, either through dedicated application hosts, or some
sort of messaging platform.
Sincerely,
Anthony Thomas
"Bruno" <Bruno@.discussions.microsoft.com> wrote in message
news:D6B04BF1-9730-46AA-A6E9-EBFC5C6B4C2D@.microsoft.com...
> Hello Friends
> I have a project that will use Failover Cluster for SQL 2005 and NLB for
the
> web server front-end (using IIS).
> That web application will be developed in-house. there are any special
> programming considerations that the programmers must embed in the
application
> in order to support the special features of Failover and NLB clusters?
> Does the web App Server must be Cluster-Aware to interact to SQL 2005
> Failover Cluster?
> Can you please give me any links to some documents that reflect these
> situations?
> Thanks for Help
> Bruno
Monday, March 12, 2012
NIC Teaming Issue
I have a cluster using adapter teaming and it seems that when the virtual
server is hosted on node 1, it is not able to resolve past the local
segment. On the other node 2 it works correctly.
Anyone have a ny input on this issue?
Thanks
Aaron
Just a shot, but did someone tinker with the routing table on that node?
You may want to run ROUTE PRINT on both nodes and compare them.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Aaron Custer" <aaron@.webmastersonlineinc.com> wrote in message
news:Oa%23aP2ByFHA.3892@.TK2MSFTNGP12.phx.gbl...
I have a cluster using adapter teaming and it seems that when the virtual
server is hosted on node 1, it is not able to resolve past the local
segment. On the other node 2 it works correctly.
Anyone have a ny input on this issue?
Thanks
Aaron
|||I just love NIC teaming software - NOT!
Make sure you the latest driver. Check your settings against the working
machine, I am sure it's something simple.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
"Aaron Custer" <aaron@.webmastersonlineinc.com> wrote in message
news:Oa%23aP2ByFHA.3892@.TK2MSFTNGP12.phx.gbl...
>I have a cluster using adapter teaming and it seems that when the virtual
> server is hosted on node 1, it is not able to resolve past the local
> segment. On the other node 2 it works correctly.
> Anyone have a ny input on this issue?
> Thanks
> Aaron
>
|||Try disabling the NIC teaming. If the problem goes away...I think you've
found the source of you issues.
Regards,
John
"Aaron Custer" <aaron@.webmastersonlineinc.com> wrote in message
news:Oa%23aP2ByFHA.3892@.TK2MSFTNGP12.phx.gbl...
> I have a cluster using adapter teaming and it seems that when the virtual
> server is hosted on node 1, it is not able to resolve past the local
> segment. On the other node 2 it works correctly.
> Anyone have a ny input on this issue?
> Thanks
> Aaron
>
|||This might be of interest:
The use of NIC teaming on all cluster networks concurrently is not
supported. At least one of the cluster networks that are enabled for
internal communication between cluster nodes must not be teamed. Typically,
the unteamed network is a private interconnect dedicated to this type of
communication. The use of NIC teaming on other cluster networks is
acceptable; however, if communication problems occur on a teamed network,
Microsoft Product Support Services may require that teaming be disabled. If
this action resolves the problem or issue, then you must seek further
assistance from the manufacturer of the teaming solution.
(Windows 2000, Windows Server 2003)
Server Clusters: Network Configuration Best Practices for Windows 2000 and
Windows Server 2003
http://www.microsoft.com/technet/pro.../clstntbp.mspx
Sincerely,
Anthony Thomas
"Aaron Custer" <aaron@.webmastersonlineinc.com> wrote in message
news:Oa%23aP2ByFHA.3892@.TK2MSFTNGP12.phx.gbl...
> I have a cluster using adapter teaming and it seems that when the virtual
> server is hosted on node 1, it is not able to resolve past the local
> segment. On the other node 2 it works correctly.
> Anyone have a ny input on this issue?
> Thanks
> Aaron
>
server is hosted on node 1, it is not able to resolve past the local
segment. On the other node 2 it works correctly.
Anyone have a ny input on this issue?
Thanks
Aaron
Just a shot, but did someone tinker with the routing table on that node?
You may want to run ROUTE PRINT on both nodes and compare them.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Aaron Custer" <aaron@.webmastersonlineinc.com> wrote in message
news:Oa%23aP2ByFHA.3892@.TK2MSFTNGP12.phx.gbl...
I have a cluster using adapter teaming and it seems that when the virtual
server is hosted on node 1, it is not able to resolve past the local
segment. On the other node 2 it works correctly.
Anyone have a ny input on this issue?
Thanks
Aaron
|||I just love NIC teaming software - NOT!
Make sure you the latest driver. Check your settings against the working
machine, I am sure it's something simple.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
"Aaron Custer" <aaron@.webmastersonlineinc.com> wrote in message
news:Oa%23aP2ByFHA.3892@.TK2MSFTNGP12.phx.gbl...
>I have a cluster using adapter teaming and it seems that when the virtual
> server is hosted on node 1, it is not able to resolve past the local
> segment. On the other node 2 it works correctly.
> Anyone have a ny input on this issue?
> Thanks
> Aaron
>
|||Try disabling the NIC teaming. If the problem goes away...I think you've
found the source of you issues.
Regards,
John
"Aaron Custer" <aaron@.webmastersonlineinc.com> wrote in message
news:Oa%23aP2ByFHA.3892@.TK2MSFTNGP12.phx.gbl...
> I have a cluster using adapter teaming and it seems that when the virtual
> server is hosted on node 1, it is not able to resolve past the local
> segment. On the other node 2 it works correctly.
> Anyone have a ny input on this issue?
> Thanks
> Aaron
>
|||This might be of interest:
The use of NIC teaming on all cluster networks concurrently is not
supported. At least one of the cluster networks that are enabled for
internal communication between cluster nodes must not be teamed. Typically,
the unteamed network is a private interconnect dedicated to this type of
communication. The use of NIC teaming on other cluster networks is
acceptable; however, if communication problems occur on a teamed network,
Microsoft Product Support Services may require that teaming be disabled. If
this action resolves the problem or issue, then you must seek further
assistance from the manufacturer of the teaming solution.
(Windows 2000, Windows Server 2003)
Server Clusters: Network Configuration Best Practices for Windows 2000 and
Windows Server 2003
http://www.microsoft.com/technet/pro.../clstntbp.mspx
Sincerely,
Anthony Thomas
"Aaron Custer" <aaron@.webmastersonlineinc.com> wrote in message
news:Oa%23aP2ByFHA.3892@.TK2MSFTNGP12.phx.gbl...
> I have a cluster using adapter teaming and it seems that when the virtual
> server is hosted on node 1, it is not able to resolve past the local
> segment. On the other node 2 it works correctly.
> Anyone have a ny input on this issue?
> Thanks
> Aaron
>
Subscribe to:
Posts (Atom)