VMotion vs VCS

Question

&nbsp;
We have a &nbsp;slightly complicated question, it is, however, not really that complicated.
&nbsp;
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 &nbsp;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.....
&nbsp;
My thinking is that changes should occur at higher levels, thereby insulating lower levels, given this logic, &nbsp;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.
&nbsp;
&nbsp;
What do you recommend and why?

mikebounds · Answer

VCS now supports vMotion, so I would install VCS, because as you say, if the O/S, which includes things like the registry keys for your application, gets corrupt, then with VCS you can failover the application to a different O/S. &nbsp;VCS also gives you more flexibilty - see&nbsp;https://www-secure.symantec.com/connect/forums/veritas-global-cluster-solution-vs-esxi-vmware-srm&nbsp;for more details which although started off about a discussion including GCO, most of the discussion does not involve GCO.
Also see&nbsp;https://www-secure.symantec.com/connect/forums/sfhadr-vvr-running-physical-and-virtual-server&nbsp;for details on Vmotion with VCS.
Mike

Forum Discussion

VMotion vs VCS

1 Reply

Related Content

NBU Instant Recovery and vmotion

VCS status show starting

vcs node

VCS cannot startup

global vcs

Recent Discussions

Configure two Mount type resources of nfs FStype attribute using the same share

order

key registration and reservation

Verifying that primary and dr clusters replication is synced

vcs can create logical nic