Guest - Guest clustering on single Hardware
Hi Community, I found a document mentioning about the limitations of guest to guest clustering on a virtualized environment (i.e. vmware ESXi) because of the I/O fencing problems in Veritas Cluster Suite 5.1 My question is do we still have this same limitation on v 6.1? You can find the article below; https://www.google.com.tr/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CBsQFjAA&url=http%3A%2F%2Fwww.symantec.com%2Fbusiness%2Fsupport%2Fresources%2Fsites%2FBUSINESS%2Fcontent%2Flive%2FTECHNICAL_SOLUTION%2F169000%2FTECH169366%2Fen_US%2FTechNote_VMware_IOFencing.pdf&ei=T0sIVNXKDOXNygPimoHQCw&usg=AFQjCNFmH2mS-AfGYlJ9WPGzoZwDo4yl7Q&bvm=bv.74649129,d.bGQSolved1.5KViews0likes1Comment
AppHA, SRM, VOM VBS Orchestration
Hello All, I'm working through a complex implementation and have hit a couple of snags along the way. Maybe people have worked on verious bits along the way and may be able to contribute to an overall solution The object of this endeavor is to create a flexible environment between 2 regional datacenters that gives us the ability to bring up a complex multi-tiered application pod at either location. Physicals meeting this HA criteria run VCS-Geo Cluster, some VMs run VCS-Geo Cluster with VVR while other VMs run AppHA..using SRM. They are all logically grouped within 2VOM VBS groups. The Home VBS consists of the AppHA VMs, Service Groups from the VCS nodes in the home datacenter while the DR VBS consists of the AppHA VMs and the matching DR geo cluster Service groups. AppHA seems to work as planned. VMs move through SRM to the datacenters and register fine in the SymHA consoles and report through VCenter with current status. My primary hurdle seems to be the control of those AppHA VMs from VOM VBS. The VBS control relies on a control host scan; and when that scan takes upwards of 6 hrs to run and update status. That time is better spent doing a manual startup sequence. Again VOM communication and dynamic updating of the Virtualization environment seem to be an issue. The VCS based elements are not an issue with my belief that they are based on a static infrastructure. I have successfully started up and shut down the home VBS, but once it moves to the opposing Datacenter...VOM can't find the VM and AppHA Consoles cant tie updates to records Has anyone done VBS orchistration of AppHA assets withe SRM handling transfers? VOM 5.0 VMWare 5.1 SRM 5.1 AppHA 6.0 VCS 5.1 SP2\ 6.0.1 Many Thanks, Many thanksSolved1.5KViews0likes1Comment
Application HA clustering has dropped a disk... :-/
Hi, After I completed the Application HA clustering of SQL2008 across two Windows 2008 R2 nodes, I found that the SQL installation'svirtual Backup disk (M: for reference) remained on the first node after I'd initiated a switch to the second node via the High Availability tab in the vSphere Client. The other disks re-attached to the second node ok. On closer inspection in Cluster Explorer on one of the nodes I discovered that the Mount Point for that disk was completely missing! I attempted to manually create the Mount Point and brought the resource online in the cluster on the first node, but attempting the switch operation again failed as the virtual disk failed to re-attach to the second node. How to fix without blatting the clustering / SQL installations? Thanks!Solved2.9KViews0likes10Comments
Have VCS to send email to admin upon fault
We a looking for a way to have VCS sends off an e-mail alert when the cluster faults to an admin. Looking at some of the previous solutions, I have come across two possible solutions. First I need to setup the traps to detect the fault. https://www-secure.symantec.com/connect/forums/vcs-notifierhanotify Then I need to create a resource to send an alert. https://www-secure.symantec.com/connect/forums/alerting-feature-applicationha Is this correct? I might need help with finding the correct trap status for the fault alert. ThanksSolved3.1KViews1like9CommentsDisable AutoFailOver from stopping services
I have several services that I am monitoring that are set to autofailover to a seconds system. It has some up that occasionally I need to restart a service without HA failing over to another system. I can disable the failover from happening using the following command hagrp -modify App_Cluster AutoFailOver 0 However what happens is that if the service is stopped HA continues to shutdown all the other services that are up. I was researching and I cam across disabling the Evacuate on HA, but even with it disabled, it still shuts down the other services. hagrp -modify App_Cluster Evacuate 0 I want the other services to continue to run even if one went down for some reason. What is the best way to accomplish this?Solved1.9KViews3likes4Comments
Configure GCO with vvr in linux
Totoal number of node on primary site 7. Management ip for all 7 nodes are defined and following are service gorup name with ip service group name 1- IP 10.1.1.1 service group name 2- IP 10.1.1.2 service gorup name 3- IP 10.1.1.3 service group name 4- IP 10.1.1.4 service group name 5- IP 10.1.1.5 Secondary site 3 nodes Managment ip for all 3 nodes are defined . If i want to configure GCO with VVR in this scenario. How many ip address required on both the nodesSolved1.6KViews0likes2Comments
