Not a Solaris question - vMotion versus 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?