Solution:
Windows Server 2012 Run Windows Powershell (Open as Administrator) Get-ClusterLog –UseLocalTime -TimeSpan 5 -Destination 'E:\Cluster Logs';
- TimeSpan 5 (logs cover the last 5 minutes)
- The event log is in local time and the cluster.log is in GMT. With Windows Server 2012 you can use the Get-ClusterLog –UseLocalTime to generate the Cluster.log in local time. This will make correlating with the event log easier.
Get-ClusterResource
Get-ClusterResource -Name "SQL Server" | Format-List -Property *
Test-Cluster –Node Node1,Node2
Test-Cluster –list
Resources:
Get-ClusterLog
- If only run Get-ClusterLog cmdlet, then go to the C:\Windows\Cluster\Reports folder and open the Cluster.log file - If ever Cluster issues, search cluster log for entries regarding “IsAlive” and/or “LooksAlive”. - For example, if SQL Server does not respond to the LooksAlive request, it will lead to a restart of the resource - but we won’t know why it was unresponsive. Usually, it is due to performance, but in order to know for sure, we would have to capture performance data the next time the issue occurs.
Resource Hosting Subsystem (RHS) In Windows Server 2008 Failover Clusters
Understanding how Failover Clustering Recovers from Unresponsive Resources
Resource DLL Entry-Point Functions
Get-ClusterResource
|
|
|
|
|