Thanks but I would disagree. We started with a VM while the environment is small. We assumed we would grow into a dedicated system and then a cluster. We soon realized, we would be better off growing unto a clustered virtualization host for greater stability rather than a stand-alone system until we are ready for a dedicated cluster. The VMs also give us other advantages such as portability.
VServer itself is an interesting technology. Having been a heavy, early Xen user and now a regular KVM user, both of which are fine products, VServer has advantages over both in certain situations of which this is one. It does require understanding how the applications work in order to tune the environment but understanding what one is using is never a bad idea. At some point, we hope to share our internal documentation on how to do this, e.g., we found we had to enable the loopback masking nflag and disable the Single IP Special Casing. We also hit the loginuid issue which is specific to the RedHat family of products.
At this point, we seem to be working fine other than an LDAP warning we are troubleshooting right now (amavis - NOTICE: do_search: trying again: LDAP_OPERATIONS_ERROR) and with a much better utilization of resources than we would have had under Xen or KVM.
This mail loss error smells like something unrelated to VServer. I'm sure it is something we did in our experimenting and troubleshooting. I just want to understand what we did so we don't do it again and can report to the Zimbra team that there is a way users can cause serious damage to theirs systems without warning from Zimbra. Thanks again - John |