Veritas Cluster
I need to know the licensing method if i am planning to run 4 Node Window cluster on Virtual machine. 1) Physical Machine having Dual CPU with 12 core ( Intel Xeon E5). 2) Virtual Machine having 16 vcpu each . So need to understand how many license i need to buy to create 4 node Vertias Cluster and which license type . Quick help is appreciated.
NetApp snapmirror resource not getting online with VCS integration
Dear All, I would like to have some help to identify following error while onlining a NetApp SnapMirror agent that was intergrated with VCS. The filer name and its credential s were given properly and even i can able to ssh it from the servers but for some reason the resource is not getting online and shows following error in the engine.log 2014/09/30 15:02:44 VCS WARNING V-16-20059-1002 (node)NetAppSnapMirror:testSM:online:Encountered errors while decrypting password! 2014/09/30 15:02:44 VCS ERROR V-16-20059-1000 (node11) NetAppSnapMirror:testSM:online:ONTAPI 'system-get-version' failed on filer node1.sys Error : in Zapi::invoke, cannot connect to socket Actually i am doing global Clustering configuration where i have two node cluster and a filer at primary site, In dr i have a single node cluster and a filer. the replication is async. Any support highly appreacited. Thanks. Uvi.
VMotion vs VCS
We have a slightly complicated question, it is, however, not really that complicated. We are moving one of our money generating apps over to dedicated UCS blades, and in VCS, (Linux on UCS blades with VCS), there is, however, some talk of using VMware and vMotion, and treat this application like other VM's that we have - in the sense, vMotion them in case of failover. This app has Terabytes of data. It is currently running on powerful Solaris systems and will be migrated to Linux on UCS. I sense that VMware is good for small databases and small apps..... My thinking is that changes should occur at higher levels, thereby insulating lower levels, given this logic, for instance, a failover should occur at the VCS level, not below the os....things like, if the os gets corrupted, vMotion will move the corrupted data alongwith. What do you recommend and why?
Need information on how to configure .vmdks with VCS to allow for vMotion
I was wondering if anyone in this forum has used virtual disks (.vmdk format) VMware 5.1 and SFWHA 6.0.1 while still taking advantage of DRS and vMotion? What a co-worker and I are trying to accomplish is to use vmdk disks instead of RDM in a configuration that allow DRS and vMotion capability. We can failover the application group from virtual system to virtual system without issue but when the guest system with the .vmdk gets vMotion'ed, then the other guest systems in the cluster cannot 'find' the disks/diskgroups for that particular application (in this example, it would be Exchange 2010). I have been looking through the SFWHA documentation but not finding anything directly related on how the environment needs to be setup in order for this to work. If anyone has the info in a document, technote, or SFWHA manual that we missed, it would be greatly appreciated to please reference the information. Thanks, Chip