About VMware ESXi considerations
Cloud Accelerator for ESXi does not support:
• automatic peering. Appliances deployed with Web Cache Communication Protocol (WCCP) or policy-based routing (PBR) support automatic peering. Appliances deployed with the Discovery Agent do not support automatic peering.
• simplified routing. Appliances deployed with WCCP or PBR do not support simplified routing. Appliances deployed in-path with the Discovery Agent support simplified routing.
• PFS. It is easier to run a separate file server instance in the cloud and not use the Cloud Accelerator for Proxy File Service (PFS).
• WAN visibility mode. Appliances deployed with WCCP or PBR support WAN visibility mode. When deployed with the Discovery Agent, however, WAN visibility mode is not supported.
• CIFS prepopulation. Appliances deployed with WCCP or PBR support CIFS prepopulation. When deployed with the Discovery Agent, however, CIFS prepopulation is not supported.
Reduced data store feature
This feature is only supported on ESXi-based Cloud Accelerator appliances.
The reduced data store support feature checks if 440 GB of disk space is allocated for the data store. If less than 440 GB of disk space has been provisioned, the software creates a 30-GB data store. This allows you to create a Cloud Accelerator that require less disk space but still provide WAN acceleration. The acceleration performance is impacted when you do not use a 440-GB disk for the data store. Performance depends on the size of your working data set.
The Cloud Accelerator uses either 440 GB or 30 GB. If you allocate a disk space that is less than 440 GB, but more than 30 GB (such as 250 GB), the Cloud Accelerator uses only 30 GB; it disregards 220 GB. If you allocate less than 30 GB, the Cloud Accelerator does not function correctly.
After you create a disk, if you resize it to 440 GB, the Cloud Accelerator still uses only 30 GB. To increase the data store size to 440 GB, you must delete the original disk and create a new 440 GB disk. Doing this reverts the data store to a “cold” state; performance improves as the SteelHead executes subsequent data transfers over the WAN.