Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, May 20, 2019 6:49 AM
Hello team,
i have two nodes windows cluster running on window server 2008R2 which is running in vsphere environment and Logical disk are virtual disks(Sql DB, SQL logs)only and not in the LUN wants to know is it normal behavior because i didn't know the disk were added already in the storage disk page as you may see the below screenshot
i have checked that the cluster report and says that no disks were found.
Please let me know the solution. DBA guys says that, issue because of disk is missing in the failover cluster manager under storage but cluster report and cluster events no critical and error messages.
Many thanks in advance
Ansar
All replies (13)
Monday, May 20, 2019 6:55 AM
Hello Ansar,
As the cluster validation report states, the warnings tell you what may be the reason for this, in general it is due to the disks not being shared disks, did you make sure the disks are shared?
You can check here for more information:
VMware ESXi: Shared Disk Between VMs
Best regards,
Leon
Blog: https://thesystemcenterblog.com LinkedIn:
Monday, May 20, 2019 8:57 AM
Hi Leon,
thanks for your reply.like as said in the earlier message vmdk it's not shared via RDM or LUN just four disks(C,d ,D,E_SQL DB and F- SQL_log) were assigned as attached screenshot for your reference.
so does these disk should showed in the failover cluster manager under storage? or not necessary? some more quorum is in node file share majority which is shared via storage .no other disk was shared via SAN storage as LUN.
Monday, May 20, 2019 8:59 AM
If you want to add disks to your cluster, the disks need to be shared, otherwise you cannot add them to the cluster and they will not be shown in the cluster.
Blog: https://thesystemcenterblog.com LinkedIn:
Monday, May 20, 2019 9:29 AM
Hi Leon,
I agreed that's what I tried to say that local disks are not showing in the cluster which is normal behavior.
DB guys claiming that issue because of disk is not showing here. My stand with him that this is the normal behavior, if the issue in disk it could be error in cluster validation report.
need your advise on this.
Monday, May 20, 2019 9:33 AM | 1 vote
Yes it's normal behavior, the cluster nodes should still see the disks in Disk Management, but as they are local disks they cannot be added to the cluster, hence why the cluster validation report giving warnings about this.
Blog: https://thesystemcenterblog.com LinkedIn:
Tuesday, May 21, 2019 3:35 AM
Hi,
Thanks for posting in our forum!
Yes, local storage cannot be used for any cluster/high-available Windows 208R2 based solution, so they will not be shown in the cluster.
If you want to use local disk, you should use 3rd party options like DataKeeper, Starwind or DataCore for storage virtualization.
/en-us/windows-server/failover-clustering/clustering-requirements
So, Cluster validation reports are correct. Generally speaking, when we encounter cluster problems, cluster validation reports will give us some guidance.
Hope this can help you, if you have any question, please feel free to let me know.
Best Regards,
Daniel
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, May 23, 2019 3:13 AM
Hi,
Just want to confirm the current situations.
Please feel free to let us know if you need further assistance.
Best Regards,
Daniel
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, May 24, 2019 12:14 AM
hi
kindly give me some guideness about warning in the cluster report.
Friday, May 24, 2019 12:36 AM
hi,
situation is ok now but not fully resolved due to below reasons.
we have two listener on for windows clustering and other one for SQL Database availability group
For the windows clustering listener :
nodes are running in the windows clustering but failed back to original node after rebooted for some situation like patch reboot ,hardware upgrades but windows clustering listener still hosting the secondary node i am not wrong supposed to be primary node.is this the normal behavior or any issues on the windows clustering settings?.
For the SQL database availability group listener:
same situation such like patch reboot ,virtual hardware but we manually failover DB secondary node but status on listener still showing secondary in AlwaysOn High Availabiliy but primary node showing as primary so on.
is this normal behavior or any issues in clustering SQL Database availability group.
your reply and solution greatly appreciated
FYI: i have generated Cluster logs that i could found only below error continuously from the both nodes
00000dd0.00002200::2019/05/24-00:55:05.058 ERR [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQ returned 21.'
00000d08.00002f7c::2019/05/24-00:55:05.058 WARN [RCM] Failed to load restype 'MSMQ': error 21.
00000dd0.00002200::2019/05/24-00:55:05.061 ERR [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQ returned 21.'
00000d08.00002f7c::2019/05/24-00:55:05.061 WARN [RCM] Failed to load restype 'MSMQ': error 21.
00000dd0.00002200::2019/05/24-00:55:05.089 ERR [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQTriggers returned 21.'
00000d08.00002f7c::2019/05/24-00:55:05.089 WARN [RCM] Failed to load restype 'MSMQTriggers': error 21.
00000dd0.00002200::2019/05/24-00:55:05.091 ERR [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQTriggers returned 21.'
00000d08.00001b60::2019/05/24-00:55:05.091 WARN [RCM] Failed to load restype 'MSMQTriggers': error 21.
00000dd0.00002200::2019/05/24-00:55:05.314 ERR [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQ returned 21.'
00000d08.00001b60::2019/05/24-00:55:05.314 WARN [RCM] Failed to load restype 'MSMQ': error 21.
00000dd0.00002200::2019/05/24-00:55:05.316 ERR [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQ returned 21.'
00000d08.00002f7c::2019/05/24-00:55:05.316 WARN [RCM] Failed to load restype 'MSMQ': error 21.
00000dd0.00002200::2019/05/24-00:55:05.325 ERR [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQTriggers returned 21.'
00000d08.00002f7c::2019/05/24-00:55:05.325 WARN [RCM] Failed to load restype 'MSMQTriggers': error 21.
00000dd0.00002200::2019/05/24-00:55:05.326 ERR [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQTriggers returned 21.'
00000d08.00002f7c::2019/05/24-00:55:05.326 WARN [RCM] Failed to load restype 'MSMQTriggers': error 21.
Monday, May 27, 2019 9:05 AM
I will discuss with SQL HA experts over here:
https://social.technet.microsoft.com/Forums/en-US/home?forum=sqldisasterrecovery
Regards,
Daniel
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, June 12, 2019 6:09 AM
thanks daniel
Wednesday, June 12, 2019 6:29 AM
You are welcome!
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, June 12, 2019 7:20 AM
Hi Ansar,
As mentioned, the cluster validation report is giving expected results when no shared storage is present.
If you have any questions related to SQL database availability groups, you can reach out to the experts in the SQL forum over here:
SQL Server > SQL Server High Availability and Disaster Recovery
Blog: https://thesystemcenterblog.com LinkedIn: