February 26, 2014 at 6:15 pm
We have an active-passive cluster with 2 nodes, A and B, hosting a failover-cluster SQL instance (FCI).
When first installing the FCI, we first installed it on A and then used the "Add node to cluster" feature to install it on B.
So A was the "active" and B the "passive" node in the cluster configuration of the FCI.
Now A has been corrupted and we need to rebuild the server and re-install the SQL on A.
Should I be using the "Add node to cluster" feature to re-install the SQL on the rebuilt A server?
So my question is:
how do I re-install the SQL failover-cluster instance on a new node that is substituting a failed "ACTIVE" node in a cluster?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
February 26, 2014 at 6:36 pm
When you said A has been corrupted, you mean databases?
February 27, 2014 at 3:32 am
No, the server itself is unusable; something happened and we are no longer able to even remote-desktop to it.
It needs to be rebuilt and the SQL re-installed. Problem is this was initially the "active" node in the cluster configuration.
The SQL instance now resides in the "passive" node, B, but we have no HA for it; if something happens to server B, we have no failover option at the moment.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
February 27, 2014 at 3:50 am
Marios Philippopoulos (2/26/2014)
We have an active-passive cluster with 2 nodes, A and B, hosting a failover-cluster SQL instance (FCI).When first installing the FCI, we first installed it on A and then used the "Add node to cluster" feature to install it on B.
So A was the "active" and B the "passive" node in the cluster configuration of the FCI.
Now A has been corrupted and we need to rebuild the server and re-install the SQL on A.
Should I be using the "Add node to cluster" feature to re-install the SQL on the rebuilt A server?
So my question is:
how do I re-install the SQL failover-cluster instance on a new node that is substituting a failed "ACTIVE" node in a cluster?
Did you evict the node from the cluster or remove it cleanly or did you just shut it down and rebuild it?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 27, 2014 at 7:43 am
Marios Philippopoulos (2/27/2014)
No, the server itself is unusable; something happened and we are no longer able to even remote-desktop to it.It needs to be rebuilt and the SQL re-installed. Problem is this was initially the "active" node in the cluster configuration.
The SQL instance now resides in the "passive" node, B, but we have no HA for it; if something happens to server B, we have no failover option at the moment.
So you have all the databases live on the other node which was passive before active server went down. So failover happened to passive node before the active went down, right? If yes, the cluster can be on the single node. Try to work on the other node and fix it. Try to run the remove node from sql installation and then evict the node and start from scratch.
February 27, 2014 at 8:09 am
Perry Whittle (2/27/2014)
Marios Philippopoulos (2/26/2014)
We have an active-passive cluster with 2 nodes, A and B, hosting a failover-cluster SQL instance (FCI).When first installing the FCI, we first installed it on A and then used the "Add node to cluster" feature to install it on B.
So A was the "active" and B the "passive" node in the cluster configuration of the FCI.
Now A has been corrupted and we need to rebuild the server and re-install the SQL on A.
Should I be using the "Add node to cluster" feature to re-install the SQL on the rebuilt A server?
So my question is:
how do I re-install the SQL failover-cluster instance on a new node that is substituting a failed "ACTIVE" node in a cluster?
Did you evict the node from the cluster or remove it cleanly or did you just shut it down and rebuild it?
We have not done anything yet to fix this.
We have the SQL instance running fine on the passive node B; it had failed over cleanly when node A failed.
Assuming we can get a new server added to the cluster, how should I re-install the SQL on that node?
Use the "Add another node" installation option? Would that work?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
February 27, 2014 at 8:14 am
muthyala_51 (2/27/2014)
Marios Philippopoulos (2/27/2014)
No, the server itself is unusable; something happened and we are no longer able to even remote-desktop to it.It needs to be rebuilt and the SQL re-installed. Problem is this was initially the "active" node in the cluster configuration.
The SQL instance now resides in the "passive" node, B, but we have no HA for it; if something happens to server B, we have no failover option at the moment.
So you have all the databases live on the other node which was passive before active server went down. So failover happened to passive node before the active went down, right? If yes, the cluster can be on the single node. Try to work on the other node and fix it. Try to run the remove node from sql installation and then evict the node and start from scratch.
Correct.
When you say "start from scratch", do you mean add a fresh new node to the cluster and use the "Add another node" installation option on the new node to install another "passive" node for the FCI?
I am just not sure about the specifics of what to do once a new node has been added to the cluster (to replace the failed one, which we cannot fix, BTW) and I am ready to install the failover-cluster instance on that new node. Bear in mind, I already have the FCI running on node B.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
February 27, 2014 at 9:04 am
Marios Philippopoulos (2/27/2014)
Perry Whittle (2/27/2014)
Marios Philippopoulos (2/26/2014)
We have an active-passive cluster with 2 nodes, A and B, hosting a failover-cluster SQL instance (FCI).When first installing the FCI, we first installed it on A and then used the "Add node to cluster" feature to install it on B.
So A was the "active" and B the "passive" node in the cluster configuration of the FCI.
Now A has been corrupted and we need to rebuild the server and re-install the SQL on A.
Should I be using the "Add node to cluster" feature to re-install the SQL on the rebuilt A server?
So my question is:
how do I re-install the SQL failover-cluster instance on a new node that is substituting a failed "ACTIVE" node in a cluster?
Did you evict the node from the cluster or remove it cleanly or did you just shut it down and rebuild it?
We have not done anything yet to fix this.
We have the SQL instance running fine on the passive node B; it had failed over cleanly when node A failed.
Assuming we can get a new server added to the cluster, how should I re-install the SQL on that node?
Use the "Add another node" installation option? Would that work?
OK, evict the node from the cluster and perform a clean rebuild. When you reinstall you use the add node wizard to join the existing instance running on node B
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 27, 2014 at 9:10 am
Thank you!
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply