rajkiggal
asked on
Cluster failover on SQL server
I have SQL 2005 (Bussness intelligence) and SQL 2008(biztalk) installed on the same server in cluster,
Cluster has 5 resource groups looks like this
Cluster Name
|
Resource Group
|
Cluster Group (Cluster name ,Quorum and Quorum IP)
|
MSDTC(MSDTC IP, MSDTC Network Name....)
|
Group BI(SQL server 2005, SQL Agent....)
|
Group BT(SQL 2008, SQL agent...)
|
File_share(Folder shares)
here is question
when Cluster Group BI fails, Group BT SQL server and agent terminates (viceversa) and i had to failover the BT to start the SQL server and agent.
Is there a possibility where if one services fail on Either on Group BI or BT, i need the other resources(all the remaining resources) to be failedover.
Cluster has 5 resource groups looks like this
Cluster Name
|
Resource Group
|
Cluster Group (Cluster name ,Quorum and Quorum IP)
|
MSDTC(MSDTC IP, MSDTC Network Name....)
|
Group BI(SQL server 2005, SQL Agent....)
|
Group BT(SQL 2008, SQL agent...)
|
File_share(Folder shares)
here is question
when Cluster Group BI fails, Group BT SQL server and agent terminates (viceversa) and i had to failover the BT to start the SQL server and agent.
Is there a possibility where if one services fail on Either on Group BI or BT, i need the other resources(all the remaining resources) to be failedover.
ASKER
Hi,
Cluster sql 2005 and cluster sql 2008 has different cluster network name and cluster IP address
Cluster file group is same as Cluster name ipaddress.
is there way i can make dependence for each other so that entire cluster failover happens, if once resource is failed.
Cluster sql 2005 and cluster sql 2008 has different cluster network name and cluster IP address
Cluster file group is same as Cluster name ipaddress.
is there way i can make dependence for each other so that entire cluster failover happens, if once resource is failed.
It depend son what resource you are talking about. You can add dependencies and I think this might be what you are looking for.
It is unclear to me what resource failure you want to trigger the failover and to what extend.
Based on your comment that when you failover BI, BT is also seen as down, suggests to be that they are bound/using the same IP resource.
It is unclear to me what resource failure you want to trigger the failover and to what extend.
Based on your comment that when you failover BI, BT is also seen as down, suggests to be that they are bound/using the same IP resource.
ASKER
Cluster sql 2005 and sql2008 has below resources( parameter are deferent for both)
sql server, sql agent , sql analysis services, 8 disk drives(offers path for Database and logs), sql network name, network ip
scenario:
when sql analysis services on sql 2005 executed it will cause the sql server on the same group to fail over (virtual memory issues),
after fail over sql won't comes up until all the resources completely are moved to second node(for any Db application require MSDTC run from same node).
all i want is, one sql server resource (Either on sql 2005 or sql 2008 cluster group) fail over should trigger complete resource group failover! for this i would like to create dependence between cluster groups to facilitate the entire cluster failover!
same happens even sql analysis services runs on sql 2008.
hope this clears
sql server, sql agent , sql analysis services, 8 disk drives(offers path for Database and logs), sql network name, network ip
scenario:
when sql analysis services on sql 2005 executed it will cause the sql server on the same group to fail over (virtual memory issues),
after fail over sql won't comes up until all the resources completely are moved to second node(for any Db application require MSDTC run from same node).
all i want is, one sql server resource (Either on sql 2005 or sql 2008 cluster group) fail over should trigger complete resource group failover! for this i would like to create dependence between cluster groups to facilitate the entire cluster failover!
same happens even sql analysis services runs on sql 2008.
hope this clears
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
cluster sql2005
IP resource, MSDTC, networkname
GROUP BI,SQL Agent
Cluster SQL2008
IP Resource, MSDTC, networkname
GRoup BT, sql, sql agent.
Cluster Filegroup
IP resource, networkname
File_share(folder share)
I.e. if both SQL servers are using the same IP, when you fail the IP to the other node, while the sql resource remains active on the prior node, access only available by use of the Node IP versus the Application cluster IP.