Best practices for deployment and administration of Symantec Messaging Gateway Virtual Edition (SMG VE) appliances.
The SMG Getting Started Guide, SMG Installation Guide and SMG Administration Guide provide the basics to properly deploy, configure and administer SMG. This document highlights some aspects that should be considered if the base documentation is not enough to cover the administrator's needs. Always refer to the SMG guides first when looking for documentation on how to deploy and administer the product.
SMG VE must be deployed according to the requirements as detailed in the SMG Getting Started Guide
The SMG Installation Guide for your product version will provide minimum and recommended memory requirements. This setting does not guarantee that the full amount of configured memory will be available to the virtual machine as physical (fast) memory. By default, ESX/ESXi does not reserve any memory to the virtual machines. This can compromise performance in certain scenarios. Symantec suggests the administrator also reserves 100% of the configured memory on the SMG VE host, or if that is not possible, a minimum of 8GB. That can be achieved by editing the SMG VE settings and configuring the reserved memory from the Resources tab.
When deploying SMG VE, it will use the media configured into ESX/ESXi as the storage unit for virtual machines. Regardless of the media used, make sure the media can be accessed properly and timely to avoid storage-related issues. Some NFS volumes can trigger errors or corruption on the virtual machine file system when storage does not perform according to the host needs.
As with hardware appliances, the same best practices apply to get the most of the product. Symantec strongly suggests SMG VE is configured according to the best practices.
In order to maximize the performance of your SMG VE, the VMware platform hosting the appliance should be tuned for best results. The following document outlines the best practices for VMware vSphere 4.1 and 5: