![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. |
|
We have built a SQL Cluster and all goes well with the failover of the Instances when either node is gracefully shutdown, ie the instances failover in roughly 10 seconds to the other node. The issue we are having is when a non grace full shutdown occurs Ie we are diconnecting the NIC's Heartbeat and LAN the results are 1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. 2. If we fail the other node which has some other instances running on it after about 90-120 seconds they come back online. Where are we going wrong ? Can anyone provide any ideas ? Hardware is HP Blade centre connecting to Iscsi Netapp. |
#3
| |||
| |||
|
|
1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. |
|
We have built a SQL Cluster and all goes well with the failover of the Instances when either node is gracefully shutdown, ie the instances failover in roughly 10 seconds to the other node. The issue we are having is when a non grace full shutdown occurs Ie we are diconnecting the NIC's Heartbeat and LAN the results are 1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. 2. If we fail the other node which has some other instances running on it after about 90-120 seconds they come back online. Where are we going wrong ? Can anyone provide any ideas ? Hardware is HP Blade centre connecting to Iscsi Netapp. |
#4
| |||
| |||
|
|
1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. |
|
We have built a SQL Cluster and all goes well with the failover of the Instances when either node is gracefully shutdown, ie the instances failover in roughly 10 seconds to the other node. The issue we are having is when a non grace full shutdown occurs Ie we are diconnecting the NIC's Heartbeat and LAN the results are 1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. 2. If we fail the other node which has some other instances running on it after about 90-120 seconds they come back online. Where are we going wrong ? Can anyone provide any ideas ? Hardware is HP Blade centre connecting to Iscsi Netapp. |
#5
| |||
| |||
|
|
1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. |
|
We have built a SQL Cluster and all goes well with the failover of the Instances when either node is gracefully shutdown, ie the instances failover in roughly 10 seconds to the other node. The issue we are having is when a non grace full shutdown occurs Ie we are diconnecting the NIC's Heartbeat and LAN the results are 1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. 2. If we fail the other node which has some other instances running on it after about 90-120 seconds they come back online. Where are we going wrong ? Can anyone provide any ideas ? Hardware is HP Blade centre connecting to Iscsi Netapp. |
#6
| |||
| |||
|
|
1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. |
|
We have built a SQL Cluster and all goes well with the failover of the Instances when either node is gracefully shutdown, ie the instances failover in roughly 10 seconds to the other node. The issue we are having is when a non grace full shutdown occurs Ie we are diconnecting the NIC's Heartbeat and LAN the results are 1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. 2. If we fail the other node which has some other instances running on it after about 90-120 seconds they come back online. Where are we going wrong ? Can anyone provide any ideas ? Hardware is HP Blade centre connecting to Iscsi Netapp. |
#7
| |||
| |||
|
|
1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. |
|
We have built a SQL Cluster and all goes well with the failover of the Instances when either node is gracefully shutdown, ie the instances failover in roughly 10 seconds to the other node. The issue we are having is when a non grace full shutdown occurs Ie we are diconnecting the NIC's Heartbeat and LAN the results are 1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. 2. If we fail the other node which has some other instances running on it after about 90-120 seconds they come back online. Where are we going wrong ? Can anyone provide any ideas ? Hardware is HP Blade centre connecting to Iscsi Netapp. |
#8
| |||
| |||
|
|
1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. |
|
We have built a SQL Cluster and all goes well with the failover of the Instances when either node is gracefully shutdown, ie the instances failover in roughly 10 seconds to the other node. The issue we are having is when a non grace full shutdown occurs Ie we are diconnecting the NIC's Heartbeat and LAN the results are 1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. 2. If we fail the other node which has some other instances running on it after about 90-120 seconds they come back online. Where are we going wrong ? Can anyone provide any ideas ? Hardware is HP Blade centre connecting to Iscsi Netapp. |
#9
| |||
| |||
|
|
1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. |
|
We have built a SQL Cluster and all goes well with the failover of the Instances when either node is gracefully shutdown, ie the instances failover in roughly 10 seconds to the other node. The issue we are having is when a non grace full shutdown occurs Ie we are diconnecting the NIC's Heartbeat and LAN the results are 1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. 2. If we fail the other node which has some other instances running on it after about 90-120 seconds they come back online. Where are we going wrong ? Can anyone provide any ideas ? Hardware is HP Blade centre connecting to Iscsi Netapp. |
#10
| |||
| |||
|
|
1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. |
|
We have built a SQL Cluster and all goes well with the failover of the Instances when either node is gracefully shutdown, ie the instances failover in roughly 10 seconds to the other node. The issue we are having is when a non grace full shutdown occurs Ie we are diconnecting the NIC's Heartbeat and LAN the results are 1. If the node is running the 1st instance that was configured on the box and this goes down / away the Instances never fail to the other node. We have to restart cluster services to bring it online. 2. If we fail the other node which has some other instances running on it after about 90-120 seconds they come back online. Where are we going wrong ? Can anyone provide any ideas ? Hardware is HP Blade centre connecting to Iscsi Netapp. |
![]() |
| Thread Tools | |
| Display Modes | |
| |