Issues creating a new failover cluster on the same server

Giganews Newsgroups
Subject: Issues creating a new failover cluster on the same server
Posted by:  Dan (D…@discussions.microsoft.com)
Date: Tue, 6 Feb 2007

We have a sans and a server box that currently has a SQL 2005 Failover
cluster installed, we are attempting to install a new SQL 2005 Failover
cluster but ran into an issue. After setting up the new cluster group and
installing the instance to this group the installer modified the SQL browser
to use a log file located in my second cluster group (chnsql04). This caused
the CHSSQL04 to fail and not allow logins from remote connections even though
the surface area configuration was set to allow remote and local logons. Once
I changed the path back to g:\ drive my chssql04 cluster works but my
chnsql04 cluster does not.

How can resolve this issue?

We have a second group of users wanting to use our server and we don’t want
them to see the data in the chssql04 cluster which is why we created a new
cluster and instance.

Would it be better to setup the server so that the server program files
“program files\SQL 2005\” are located on one drive that is seen by both
clusters and then create a data drive for each of the cluster groups to store
the db on?

If so how can I share a resource between two clusters?

We have the following setup for our SQL Fail over cluster:

CHSSQL04 Cluster Group
Drives: E, G, K, S, Z
Two file shares
SQL IP address (10.0.50.48)
SQL Network Name (vssql04)
SQL Server (instance name)
SQL server agent (instance name)
SQL Server Fulltext (instance name)

The sql server data and program files are installed on G:

New cluster group setup:

CHNSQL04 Cluster Group
Drives: H and F
The setup then created the following:
SQL IP address (10.0.50.68)
SQL Network name (chnvssql04)
SQL Server (instance name)
SQL server agent (instance name)
SQL Server Fulltext (instance name)

The sql server data and program files are installed on H:

Thanks in advanced,

Daniel

Replies