Issues creating a new failover cluster on the same server



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
.



Relevant Pages

  • Re: Clustering Question
    ... You could make a test environnement through Virtual Machine to get a picture on Cluster. ... I have worked with Windows 2003 Small Business Server, Exchange Server 2003 and 2000 SQL server but not in a clustered environment. ... > you cannot install Cluster on a Small Business Edition, ...
    (microsoft.public.windows.server.clustering)
  • Re: Cant get SQL 2000 installed on new node in Cluster
    ... You can apply a service pack to a new node without taking the Virtual SQL ... server offline. ... When the install is asking for a virtual server name, ... one for the MSCS cluster or the one for the SQL cluster? ...
    (microsoft.public.sqlserver.clustering)
  • Re: Exchange 2007 CCR on Windows 2008 x64 RTM
    ... install guide, but I always did it too quickly after the failure. ... I'm an MCITP on Server 2008 & Exchange ... I'm told that this is caused by the way the cluster service creates the ... respond to the start or control request in a timely fashion occured ...
    (microsoft.public.exchange.setup)
  • Unable to Apply SP4 to SQL 2000 Cluster (new Node)
    ... SQL Server 2000 EE ... I had a three-node A/A/P cluster. ... Install SQL 2000 binaries on newly added node for Instance 1 ... "All cluster disks available to this virtual server are owned by other nodes." ...
    (microsoft.public.sqlserver.clustering)
  • RE: How do I get back to base SQL server on my SBS 2003 server?
    ... After you uninstall SQL 2005, the instance which you upgraded will not go ... Uninstall and then reinstall ISA server. ... Uninstall and then reinstall the Monitoring component. ... Tools to Maintenance, change Monitoring component to Install, and then ...
    (microsoft.public.windows.server.sbs)