Lose server in cluster

Hello,
It looks like the documentation is telling me to delete the instances in order to uncluster servers. So, if you have some servers clustered you pretty much have to delete the instances and start all over again to uncluser them.
That leads me to thinking. What happens if I have two servers cluster together and one complete breaks. Can I grab another server, install AppServer EE and introduce it to the cluster? Or am I stuck recreating the cluster and redeploying my applications?
Mike Brown

Hi Barney,
Technically what you want is an "upstream backup" - this can be achieved by using coherence as a durable source of events and replay the events from Coherence in the case of a restart. If your relation moves in time then the other approach is to use servers in parallel to maintain continuity - in the simple case you have two servers processing the same set of events but only one outputing results (co-ordinated by any one of the HA adapters that we ship). If you restart one of these then the other node will output the correct sequence until the relation window has been rebuilt in the newly started server, at that point you can restart the other server.
andy

Similar Messages

Connecting managed server to cluster's administration server

Hello,
I have a problem when trying to connect managed server to cluster's
administration server.
When starting the managed server I get a security exception:
[javax.naming.AuthenticationException [Root exception is
java.lang.SecurityException: Administrators must log in over admin port with
admin protocol.]]
weblogic.management.configuration.ConfigurationException: admin URL:
t3://192.168.14.15:7001 - with nested exception:
[javax.naming.AuthenticationException [Root exception is
java.lang.SecurityException: Administrators must log in over admin port with
admin protocol.]]
at
weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:893)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
I get the same result when testing the connection setup with
java weblogic.Admin -url 192.168.14.15:7001 -username system -password xyz
CONNECT 1
Background for this problem:
I'm trying to evaluate WLS6.0 clustering for my RMI services. I have two
machines setup with my test domain (DEdomain) and one cluster (DECluster)
within it.
In administration server (machine A) I defined two servers to be run in
machine A and machine B:
DEserver2 in machine B (to be started as managed server) and DEserver3
in machine A
I'm going to bind a same service into these above servers of my DECluster.
In machine B's startManagedWeblogic.sh I have:
java -ms64m -mx64m -classpath
$CLASSPATH -Dweblogic.Domain=DEdomain -Dweblogic.Name=$SERVER_NAME -Dweblogi
c.management.server=$ADMIN_URL -Djava.security.policy==$WL_HOME/lib/weblogic
.policy -Dweblogic.management.username=system -Dweblogic.management.password
=$WLS_PW weblogic.Server
In machine A I have administration server DEserver1 listening port 7001.
And for the domain and cluster building I followed all relevant e-docs
manual pages. It's still somewhat blurry what kind of preparations I have to
make in managed server side to join the domain; for example do I have to
have identical domain directory structure within machine B and do I have to
configure something with admin console or is everything handled by
connecting to the administation server and reading the domain's config.xml
from machine A.
I'm sure I have missed some fundamental idea for building clustered services
and would greatly appreciate if someone had any good tips or ideas.
Best regards,
Harri

Hi Kumar,
and thank you. That fixed my problem
Best regards,
Harri
"Kumar Allamraju" <[email protected]> wrote in message
news:[email protected]...
It appears you had set the administration port & listen port on the admin
server.
Logging onto admin server via admin port is broken currently. I wouldsuggest
you to set only listen port
and see how that goes.
Kumar
"Harri Töhönen" wrote:
Hello,
I have a problem when trying to connect managed server to cluster's
administration server.
When starting the managed server I get a security exception:
[javax.naming.AuthenticationException [Root exception is
java.lang.SecurityException: Administrators must log in over admin portwith> > admin protocol.]
weblogic.management.configuration.ConfigurationException: admin URL:
t3://192.168.14.15:7001 - with nested exception:
[javax.naming.AuthenticationException [Root exception is
java.lang.SecurityException: Administrators must log in over admin portwith> > admin protocol.]
at
weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:893)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
I get the same result when testing the connection setup with
java weblogic.Admin -url 192.168.14.15:7001 -username system -password
xyz
CONNECT 1
Background for this problem:
I'm trying to evaluate WLS6.0 clustering for my RMI services. I have two
machines setup with my test domain (DEdomain) and one cluster(DECluster)
within it.
In administration server (machine A) I defined two servers to be run in
machine A and machine B:
DEserver2 in machine B (to be started as managed server) andDEserver3
in machine A
I'm going to bind a same service into these above servers of myDECluster.
>>
In machine B's startManagedWeblogic.sh I have:
java -ms64m -mx64m -classpath
$CLASSPATH -Dweblogic.Domain=DEdomain -Dweblogic.Name=$SERVER_NAME -Dweblogi
>>
c.management.server=$ADMIN_URL -Djava.security.policy==$WL_HOME/lib/weblogic
>>
.policy -Dweblogic.management.username=system -Dweblogic.management.password
=$WLS_PW weblogic.Server
In machine A I have administration server DEserver1 listening port 7001.
And for the domain and cluster building I followed all relevant e-docs
manual pages. It's still somewhat blurry what kind of preparations Ihave to
make in managed server side to join the domain; for example do I have to
have identical domain directory structure within machine B and do I haveto
configure something with admin console or is everything handled by
connecting to the administation server and reading the domain'sconfig.xml
from machine A.
I'm sure I have missed some fundamental idea for building clusteredservices
and would greatly appreciate if someone had any good tips or ideas.
Best regards,
Harri

How to install a DB Instance in a SQL Server 2005 cluster

Hi all,
I have an installation scenaro is install SCS/CI in machine A, and DB instance on a already exist cluster. This is based on Windows 2003 SR2 and SQL Server 2005 cluster. But now after i finish SCS, i don't know how to install the DB instance. Do i just need sign in the active node of the DB cluster and start the sapinst.exe. I am worry about any of my mis-action will broke the cluster.. Appreciate any tips or idea about it, thanks.
Peter

directly start sapinst.exe on the cluster node.

Service Accounts for Reporting Service in SQL Server Failover Cluster setup

I am setting up 2 Report Services (SSRS) in SQL Failover Clustering (Version: 2012SP1) on Windows 2012, as part of scale out architecture.
There are 2 options to configure the service account for SSRS:
Option 1) Using domain accounts, as what I have done for DB Engine and SQL Agent.
Option 2) accept the default, which is virtual account for SSRS. Per documentation URL:
http://msdn.microsoft.com/en-us/library/ms143504.aspx
which is the recommended one? is it option 2?
There is security note on above URL as well, but does not clearly mention that option 1 is not recommended.
Security Note: Always run SQL Server services by using the lowest possible user rights. Use a MSA or virtual account when possible. When MSA and virtual accounts are not possible, use a specific low-privilege user account or domain account instead
of a shared account for SQL Server services. Use separate accounts for different SQL Server services. Do not grant additional permissions to the SQL Server service account or the service groups. Permissions will be granted through group membership or granted
directly to a service SID, where a service SID is supported.
Thanks very much for your help!

Hi Luo Donghua,
In SQL Server Failover Cluster Instance, personally two options can run well. If you use the virtual account for SQL Server Reporting Service. Virtual accounts in Windows Server 2008 R2 and Windows 7 are managed local accounts that provide the features to
simplify service administration. The virtual account is auto-managed, and the virtual account can access the network in a domain environment.
Of cause, you can also use domain accounts in your clustering.
Just make sure your service account is set up here, or that it is using a proper built-in account.For more information, see:http://ermahblerg.com/2012/11/08/cluster-ssrs-in-2008/
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

Problem starting managed server in Cluster

Hi,
I'm using cluster with 2 managed server. other managed server2 is runing ok in the cluster now when I am starting managed server1 in a cluster this error is coming
The WebLogic Server encountered a critical failure
Reason: Assertion violated
Exception in thread "main" java.lang.NoClassDefFoundError
at weblogic.protocol.ServerIdentityManager.findServerIdentity(ServerIdentityManager.java:65)
at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:170)
at weblogic.server.ServerLifeCycleRuntime.getLifeCycleOperationsRemote(ServerLifeCycleRuntime.java:677)
at weblogic.t3.srvr.ServerRuntime.sendStateToAdminServer(ServerRuntime.java:406)
at weblogic.t3.srvr.ServerRuntime.updateRunState(ServerRuntime.java:392)
at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:172)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:373)
at weblogic.Server.main(Server.java:67)
Could you pl tell the reason of this error?
Thanks in advance
Hi,
Can anybody help?
Edited by: user10680571 on Dec 4, 2008 4:42 AM

Thanks David.
During starting this managed server in cluster when I do tail -f <log_file_name> I can see this error message. But this message I can't see in log however ending log details- Is this something related with CLASSPATH problem?
<04-Dec-2008 10:11:18 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
he end of the classpath:
/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
<04-Dec-2008 10:11:21 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
<04-Dec-2008 10:11:33 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
06 783464 >
<04-Dec-2008 10:12:06 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
<04-Dec-2008 10:12:06 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<04-Dec-2008 10:12:06 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<04-Dec-2008 12:12:26 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
he end of the classpath:
/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
<04-Dec-2008 12:12:35 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
<04-Dec-2008 12:13:03 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
06 783464 >
<04-Dec-2008 12:13:56 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
<04-Dec-2008 12:13:58 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<04-Dec-2008 12:14:00 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<05-Dec-2008 06:21:55 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
he end of the classpath:
/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
<05-Dec-2008 06:21:57 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
<05-Dec-2008 06:22:04 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
06 783464 >
<05-Dec-2008 06:22:23 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
<05-Dec-2008 06:22:23 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<05-Dec-2008 06:22:23 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
Thanks for your help.....

How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)

I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
single Windows Server Failover Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

please post you question on failover clusters in the cluster forum. THey will explain how this works and point you at scipts.
You should also look in the Gallery for cluster management scripts.
¯\_(ツ)_/¯

How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster) with scrpiting

I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
single Windows Server Failover Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

You are trying to implement manually what should be happening automatically in the cluster. If the primary SQL Server becomes unavailable in the data center, it should fail over to the secondary SQL Server automatically. Is that not working?
You also might want to run this configuration by some SQL experts. I am not a SQL expert, but if you have both hosts in the data center in a cluster, there is no need for replication between those two nodes as they would be accessing
the database from some form of shared storage. Then it looks like you are trying to implement Always On to the DR site. I'm not sure you can mix both types of failover in a single configuration.
FYI, it would make more sense to establish a file share witness in your DR site instead of placing a third node in the data center for Node Majority quorum.
. : | : . : | : . tim

SQL Server Failover Cluster Questions

Dear All,
            I am building a two-node failover cluster on SQL Server 2012 SP1 (inside Hyper-V as a Guest Cluster) and want clarification on few things that I am facing.
1.  I am receiving MSDTC Warning. I can go ahead and create the cluster, but want to understand whether this MSDTC is to be configured as a role on the cluster or not. I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases
and Reports through it so in such a scenario, do I need MSDTC? If yes, how much should be the size of the MSDTC Drive? Is following process correct?
http://www.sqlnotebook.info/configure-msdtc-on-windows-cluster-2012/
2. During First Node configuration, one needs to provide the "SQL CLUSTER RESEOURCE GROUP NAME". Does it have any bearing on how it will be accessed by other servers for databases and logs? or is it just how the cluster resource group
would be named? would it be required for every instance that is created inside the cluster? Just to be clear, so one can name it according to the instance name.
3. During the instance creation, one needs to provide "SQL Server Network Name". As stated above, I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through it, so would I be required to provide this
for all instances that I create or this is only required once in the cluster:
4. During the instance creation, one needs to provide the features required for installation i.e. instance features and shared features. As stated above, I plan to run SCVMM, SCOM, Orchestrator and Windows Azure Pack Databases and Reports through
it, so which features should be selected? so that there is less workload on the server.
5. All the instances use TempDB for databases that are present inside it. What would be the best practice with respect to TempDB. One TempDB for all instance on the servers on a separate LUN or all instance having their own TempDB LUN?  What
should be the ideal size of the TempDB LUN?
6. Should all the disks required for DBs and Logs be added to Cluster?  Should they be added normal disks or CSV Volumes?
Thanks in advance.

Hello,
1.You can run the Microsoft Distributed Transaction Coordinator service (MSDTC) as a clustered resource on a failover cluster server for increased reliability, based on the failover capabilities of the clustered servers. You can
refer to the MSDTC section of the following blog about determine whether the Microsoft Distributed Transaction Coordinator (MSDTC) cluster resource must be created.
Reference:http://msdn.microsoft.com/en-us/library/ms189910.aspx#MSDTC
2. The Cluster Resource Group is where SQL Server failover cluster resource will be placed. Each clustered SQL Server will belong to a Failover
Cluster Resource Group. For example, if you had configure a two node SQL Server Cluster, each clustered instance on the two node belong to a same Cluster Resource Group.
You can change the Cluster Resource Group name, but notes the following name is reserved and already used as Resource Group names: Available Storage, Cluster Group.
3. Each SQL Server cluster is assigned a virtual Network name and IP address, which client applications use to connect to the clustered SQL Server.
4. Not familiar with SCVMM, SCOM, Orchestrator, but you should install the Database Engine Services and SQL Server Management tools.If you want to use SQL Server Reporting Services, you can install Reporting Servers, but Report Server service cannot participate
in a failover cluster.
5. You can use isolated disk for user database and temp DB of each SQL Server Cluster
6. Yes. You should use Cluster Disks which add to Clustered Shared Volumes to host the data file and log of databases.
http://www.pythian.com/blog/how-to-install-a-clustered-sql-server-2012-instance-step-by-step-part-1/
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Prepositioning files on a Server 2008 Cluster

I recently replaced a Server 2003 cluster with a server 2008 cluster. After the migration my prepostioning stopped functioning. The virtual servers are named the same and all the credentials, etc are the same. If I go into one of the preposition definitions and click browse I get a could not access cifs://<servername>. If I point to any of the other servers I am able to browse. Doesn't matter if they are server 2003 or 2008. The clustered servers are domain controllers. The version is 4.1.1c

Could you elaborate on this,as I am having the same issues? Our prepositioning works on the 2003 boxes but not the new 2008 ones.
Where abouts did you turn off the server signing .My serevr team say they have done this,but i would like to check myself.Is there anything else you changed? I can browse the files and select them fine,its just that once the schedule has started,no files get copied.
thanks,
Nick

Does a sql server client application needs to be modified to allow it to have benefits of running on a SQL Server 2012 cluster?

I have a client application in c++ which interacts with sql server database. My question is whether I need to make any changes to the client application code to allow it to have the benefits of running on a SQL server 2012 cluster environment.
To elaborate more on my query my concern is for e.g if my application has called an api to execute a sql query and during
the execution of this query the sql server (part of the cluster) goes down then as per my understanding the sql cluster would ensure that another node takes up the task from the current sql server which has gone down. Is this transition transparent to the
client application or in such a case my client application needs to again make a new connection and again execute the query?

Hello,
Just as Shanky post above, When you connected to a database in an availability group and specify the availability group listener in the connection string, if the availability group fails over, the original connection is broken, your application
should try a new connection after the failover.
So, when connect to an availability group, please try to increasing connection timeout and implementing connection retry logic to increase the probability of successful connection.
Reference:SqlClient Support for High Availability, Disaster Recovery
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

Howto take SQL Server 2005 Cluster AND Cluster Group Offline

I need to update firmware on the backend storage used by our Active/Passive SQL Server 2005 Cluster. The first step in the process states that all I/O to the disks should be stopped. Per that, I need to take the the SQL Server cluster offline AND the cluster group; however, I then need to use one of the servers that participates in the cluster to perform the upgrade on the storage array. Using the process (which doesn't account for having to use one of clustered servers to perform updates) outlined at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1550288&SiteID=1 as a basis, below is my best guess regarding what I will need to do:
Shutdown:
1. Backup all of your databases prior to the outage and ensure they are in a safe place (NOT on the disk drives in the cluster)
2. Take the SQL Server group OFFLINE. This will cleanly shutdown the SQL Server and it will remain offline when you power the machine back on.
3. Once SQL Server is offline, power off the node which does NOT have the cluster resource currently running on it
4. Save the node which is running the cluster group for last - make a note of this machine as it will be the first one you power back on. MY ADDITION: Before powering it down, set the cluster service to manual so that when you restart the server to perform the storage array maintenance, the cluster will not be running - and likewise not generating I/O against the disk array.
MY ADDITION: 5. Restart the server from step 4. Takes the cluster offline "cleanly" and brings the server back on line so that the storage array maintenance can be performed.
6. Update the firmware on the storage array. After that is complete, set the cluster service back to "Automatic".
Start up:
1. Restart the server. Per the previous steps, the server to be restarted will be the server that last hosted the cluster group and the one used to update the firmware on the storage array.
2. RDP into the node, open cluster administrator, and verify that the cluster came back online successfully and everything looks clean
3. Power on the second node.
4. Failover the cluster group across each node in the cluster and validate that everything looks OK
5. Bring your SQL Server groups back online
6. Validate that everything is operational
Is there a better way to do this or official documentation for the process?
Thanks.

FYI: I did use the process outlined above to briing the cluster offline, perform updates, and bring it back online. It worked as I had hoped. As a test, I had also done the same on a test [non-SQL] cluster prior to making the updates to our SQL cluster. Is it the best way to do it? Who knows. Did it work? Yes.

The lease timeout between avaiability group and the Windows Server Failover Cluster has expired

Hi,
I am having some issues where I get a lease timeout from time to time. I have a Windows 2012 Failover Cluster with 2 nodes and 2 SQL 2012 Always-on Availability Groups. Both nodes
are a physical machines and each node is the primary for an AG.
From what I understand if
the HealhCheckTimeout
is exceeded without the signal exchange the lease is declared 'expired' and the SQL Server resource dll reports that the SQL Server availability group no longer 'looks alive' to the Windows cluster manager. Here are the properties I have setup
which are the default settings:
LeaseTimeout - 20000
HealthCheckTimeout - 30000
VerboseLoging - 0>
FailureConditionLevel – 3
Here are the events that occur in the Application Event Viewer:
Event ID 19407:
The lease between availability group 'AG_NAME' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover
Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster.
Event ID 35285:
The recovery LSN (120881:37533:1) was identified for the database with ID 32. This is an informational message only. No user action is required.
SQl server logs are too long to post in this box but I can send them if you request.
The AG is setup to failover automatically but it did not failover. I am trying to figure out why the lease timed out. Thanks.

From what I've been able to find out, this is due to an issue with the procedure sp_server_diagnostics. It sounds like the cluster is expecting this procedure to regularly log good status "Clean" in the log files, but the procedure is designed not
to flood the logs with "Clean" messages, so only reports changes, and does not make an entry when the last status was "Clean" and the current status is "Clean". The result is that the cluster looks to be unresponsive. However, once it initiates
the failover, the primary machine responds, since it was never really down, and the failover operation stops.
The end result is that there really never is a failover, but the database becomes unavailable for a few minutes while this is resolved.
I'm going to try setting the cluster's failure condition level to 2 (instead of 3) and see if that prevents the down time.
blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx

Failover of ASCS takes very long on a Windows Server 2008 Cluster

Hello everybody,
I have configured a ABAP SCS (NetWeaver 7.0) running on a Windows Server 2008 Cluster. The database runs on SQL Server 2008 which is also configured for use in the MSCS. The ASCS and the database run fine in the Cluster. So far so good.
When I want to move the SAP Group which contains the ASCS from on node the other node, then the failover will take very long (approximately 2-3 minutes). The Service of the group will go offline in a few seconds, but the Instance needs about 1 minute to go offline and on the other node it needs more then one minute to become online.
The failover of the databaseinstance will take only about 10 seconds.
Have you got any ideas why the failover of the SAP Group will take so long?
Thanks for your help in advance!
Kind Regards,
Wolfgang

One minute would be somewhat long if you are running a faster server and just the ABAP environment. But I've seen ABAP/JAVA systems take up to 10 minutes to restart on a win 2005 clustered system.
Have you looked through the developer traces?
J. Haynes

New SQL Server Failover Cluster Installation - No disk is available to select in section "Cluster Disk Slection"

Hello Everyone,
I am in a deep need for your help regarding the problem I am facing.
I am doing a New SQL Server Failover Cluster Installation in a virtual server that is part of a failover cluster. I am able to complete all the steps successfully but, when I reach the point where I am supposed to select the shared disk that will
be included in the SQL server resource cluster group, I don't find any disk in the list (as u can see in the figure below).
I have already created the a 2 nodes failover cluster and added 3 disks (1 as a witness in Quorum and 2 other available storage).
No roles were created, 2 nodes are available and 1 network is there in the cluster.
If u take a look at the message it say: "The search for mount points failed. Error: the system cannot find the path specified". What is this and how can I solve this issue??
Thanks in advance for your support and looking forward for your valuable feedbacks.
Mark as answer if it was an answer for you question.. Please don't hesitate to ask for any further help..

Dear Ashwin,
I have granted the privileges mentioned in the link you provided as below:
Act as Part of the Operating Sywstem = SeTcbPrivileg
  Bypass Traverse Checking = SeChangeNotify
  Lock Pages In Memory = SeLockMemory
  Log on as a Batch Job = SeBatchLogonRight
  Log on as a Service = SeServiceLogonRight
  Replace a Process Level Token = SeAssignPrimaryTokenPrivilege
I was not able to solve the problem by giving these privileges to the domain account I am using to install SQL.
Mark as answer if it was an answer for you question.. Please don't hesitate to ask for any further help..

Can a SQL Server Failover Cluster Instance (FCI) be Implemented Between Two Hyper-V Hosted Virtual Machines?

I haven't had the opportunity to implement a SQL Server Failover Cluster Instance (FCI) for over 10 years and that was done with two physical, identical database servers way back in the day of Windows Server 2003 and SQL Server 2000 (old school).
Can a SQL Server 2008 R2 Failover Cluster Instance (FCI) be implemented between two Hyper-V hosted virtual machines? The environment in question already has Windows Server 2012 R2 Hyper-V hosts in place, so I'm just looking to see if this is even
possible and/or supported when utilizing virtual machines.
The client in question is currently using SQL Server 2008 R2 instances running on Win2008R2, Win2012, and Win2012R2, but I'd also be interested how this can be done or not with SQL Server 2012 or 2014 as well. Thanks in advance.
Bill Thacker

Yes, it can be done with Hyper-V guests. In fact, with Windows Server 2012 R2 Hyper-V, guests can use the Shared VHDX feature for shared storage used by Windows clusters. The guests can run Windows Server 2008 and higher provided that the Hyper-V Integration
Services are installed to support Shared VHDX. The only challenge here is making the Hyper-V hosts highly available as well, running it on WSFC.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Lose server in cluster

Similar Messages

Maybe you are looking for