About deployment considerations
These features are not supported:
• PFS. It is easier and simpler for you to run a separate file server instance in the cloud and not use the SteelHead for Proxy File Service (PFS).
• WAN visibility mode. Appliances currently support only correct addressing. They do not support full transparency and port transparency.
• CIFS prepopulation. Typically, you configure prepopulation on the remote branch appliance instead of the cloud appliance.
About Microsoft Azure considerations
Multiple network interface cards (NICs), policy-based routing (PBR), and web cache communication protocol (WCCP) are not supported.
Some appliance models for Azure use multiple disks with Fault Tolerant Storage (FTS) to achieve their large data store capacity. Because of this different disk layout, upgrading to these models requires clearing the data store.
About Amazon AWS considerations
Deployments into AWS do not support:
• simplified routing and connection forwarding. Appliances deployed into AWS are configured in a unique out-of-path method using one interface. Simplified routing and connection forwarding do not apply.
• WCCP/PBR/L4. Appliances deployed into AWS use a unique redirection mechanism that enables deployments in any cloud environment. WCCP/PBR/L4 redirection are supported when made available by the cloud provider. Amazon EC2 does not support these traditional redirection mechanisms.
About VMware ESXi considerations
Deployments into ESXi do not support:
• automatic peering. Appliances deployed with Web Cache Communication Protocol (WCCP) or policy-based routing (PBR) support automatic peering.
• simplified routing. Appliances deployed with WCCP or PBR do not support simplified routing.
Reduced data store feature
This feature is only supported on appliances deployed into ESXi.
The reduced data store feature checks if the licensed amount of disk space is allocated for the data store. If less than the maximum amount of licensed disk space has been provisioned, the software creates a 30-GB data store. This allows you to create an appliance that requires less disk space but still provides WAN acceleration. The acceleration performance is impacted when you do not allocate maximum disk space for the data store. Performance depends on the size of your working data set.
The appliance uses either the maximum amount of licensed disk space or 30 GB. If you allocate a disk space that is less than the maximum, but more than 30 GB, the appliance uses only 30 GB, disregarding your specified amount. If you allocate less than 30 GB, the appliance does not function correctly.
To increase the data store size from 30 GB to a larger size, you must delete the existing disk and create a new one. Doing this reverts the data store to a “cold” state; performance improves as the appliance executes subsequent data transfers.