January 8, 2010 at 7:13 am
I have a 2 node cluster that I would like to create a script to automate a failback once a cluster has failed over. It is possible to trigger using tsql a command to move from say node1 to node 2 when there is zero activity in the database?
January 8, 2010 at 8:00 am
shondelle (1/8/2010)
I have a 2 node cluster that I would like to create a script to automate a failback once a cluster has failed over. It is possible to trigger using tsql a command to move from say node1 to node 2 when there is zero activity in the database?
Isn't there a Maintenance window for such things..?
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
January 8, 2010 at 8:12 am
Unfortunately out maint. window is not until the end of January. 🙁
I was asked to get these cases moved back before then and to do it without causing a disruption to service.:crying:
January 8, 2010 at 8:56 am
Surely a cluster failover will be relatively transparent to your users?
Are the application using it cluster aware?
Gethyn Elliswww.gethynellis.com
January 8, 2010 at 8:58 am
But I don't think using a Trigger to fire upon Zero database activity would be a perfect solution too, as sometimes there may not be an activity for a certain time during the day, which might cause a failover to happen..don't think user management would like it...
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
January 8, 2010 at 9:45 am
How about setting that node you want to failback as the PREFERRED OWNER for your SQL service?
Then whenever that node is available, SQL will failback to there.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply