ApplicationHA 6.1, ESXi 5.5 and SQL 2012 problems
Hi all, Just wondering if anyone out there might be able to throw a bit of advice my way. Currently evaluating AppHA on VMWare (AppHA 6.1 and ESXi 5.5 hosts) with the view to buying as on paper it does exactly what we want. I've installed the High Availability Console server which has plugged into vCenter nicely, installed the ApplicationHA agent onto a VM running Windows 2012 DC R2 and SQL 2012, again all going smoothly up to this point. Now I get around to testing the agent out. I'm doing this by stopping the sql server and sql agent services on the VM and waiting for AppHA to kick in and restart both services, this is when I'm getting into a little trouble. Firstly the services do not shut down as cleanly as when the agent is not configured on the VM, a message pops up saying that windows could not stop the SQL server and that the service did not return an error, helpful I know. This does not happen when the agent is not configured on the VM, the services shut down fine. Secondly when the agent is configured and the services finally shut down, the AppHA plugin for the VM in vCenter displays a faulted status and that the SQL server service is not running and that the SQL agent service could not started. AppHA just sits there and does nothing, it does not restart the services as it should do. Now it's probably something I've done during setup but being new to the product I cannot see what, I have followed all the install pdf's and have read them over many times, I just cannot see what I may have done wrong as the setup seems simple enough. Or am I testing the product in the wrong fashion? As I'm only in evaluation mode I have no technical support with Symantec so any help with this would be very much appreciated as we are looking at buying this product and at the moment this is the final piece of the test I need to get working (probably the most important part) before I can turn to the bean counters and ask for some cash. Many Thanks LeeSolved2.4KViews1like2Comments
VCS AutoStartList ungracefully failover part2
I have two system cms-app-49-51 and cms-app-49-52 that I have been testing an ungraceful shutdown between systems (hard power off) After failing over from cms-app-49-52 to cms-app-49-51 I brought cms-app-49-52 back up and cleared all error (or so I thought.) I checked the system and everything looked to be fine all faults cleared. [root@cms-app-49-52 ~]# hastatus -sum -- SYSTEM STATE -- System State Frozen A cms-app-49-51 FAULTED 0 A cms-app-49-52 RUNNING 0 -- GROUP STATE -- Group System Probed AutoDisabled State B CMSApp_Cluster cms-app-49-52 Y N OFFLINE B CMSApp_Notifier cms-app-49-52 Y N ONLINE [root@cms-app-49-52 ~]# hagrp -display -attribute AutoDisabled #Group Attribute System Value CMSApp_Cluster AutoDisabled cms-app-49-51 0 CMSApp_Cluster AutoDisabled cms-app-49-52 0 CMSApp_Notifier AutoDisabled cms-app-49-51 0 CMSApp_Notifier AutoDisabled cms-app-49-52 0 However CMSApp_Cluster on cms-app-49-52 never started automatically until I "hagrp -online CMSApp_Cluster -sys cms-app-49-52" Attached is the logfile from both systems, please look around 2012/12/06 14:58:38Solved2KViews1like3Comments