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
Symantec ApplicationHA 6.0.00000.419 vCenter 5.5 plugin
We have been running the symantec Application plugin with vCenter 4.1 but have now upgraded to vcenter 5.5. Do we need to upgrade the plugin. Is it validated with 5.5 yet and if not when is this likely and with what version number. Thank you.Solved2.1KViews0likes5Comments
Actually Wally - I've hit
Actually Wally - I've hit another snag, which hopefully you can help with. Following the Veritas™ Cluster Server Implementation Guide for Microsoft SQL Server 2008 and 2008 R2, I'm attempting to create the MSDTC resource groupas explained in Chapter 7. I have a separate disk (I: MSDTC) ready on the node I'm configuring the resourceon, and I'm using SQL Server Agent Configuration Wizard to create the resource group with. After specifiying the name of the group and selecting both nodes of the cluster to configre the group on, I click Next and then receive the following error message: I've done some research on the error but haven't found anything other than a patch: https://sort.symantec.com/patch/detail/7842which includes the hotfix Hotfix_6_0_10011_3247363 and mentions the above error, but is intended to fix an issue with the "Windows FileShare" and "SQL Server 2008" agent configuration wizards. Can you offer any advice on the error, please? Thanks, SB.Solved3.2KViews0likes10Comments