Since we were not planning multiple zimbra instances per vserver host, we simply excluded /opt/zimbra from the hashify process. This conflict between MySQL/InnoDB and VServer hashify does not normally manifest itself because MySQL stores data by default in /var and VServer excludes /var from hashify by default.

If for some reason, we wanted to run multiple zimbra instances, we could have been more specific in our exclusion, e.g., /opt/zimbra/db/data. Hope this helps - John