The size of the SSDs or the SmartDisk used for caching defines the cache area size. The SSDs or the SmartDisks that are used for caching are added in a CACHEPOOL and cannot be used as storage disks.

All the data volumes that are created are implicitly associated with the "auto" cache area. You can change the association to "noauto" and then explicitly associate the data volumes to the cache area. In case of multiple cache areas, only one cache area has an auto association.

Veritas recommends that the SmartDisks must not be used as data disks.

As part of the earlier configuration, if you have cache areas created on a locally attached SSD and plan to use SmartIO in VMware vMotion environment, you must delete the existing cache areas and create them on the SmartDisk attached.

If the data volume is disconnected, caching for that volume is stopped. Caching is restarted afresh once the volume is reconnected and brought online.

If the cache area is disconnected, the cache area is taken offline and hence it stops caching of all the volumes that are linked with it.

If vMotion is initiated when the cache area is offline, SFW does not re-create the cache area. Admin intervention is required to reconnect the disconnected SmartDisk and to bring the cache area online. SFW then performs the operations that are required for recreating the cache area.

You cannot take or restore a snapshot of the virtual machine to which a SmartDisk is attached.

Before taking or restoring the snapshot, you must delete the cache area and unassign the SmartDisk, using the vDMP client. After the snapshot is taken or restored, you must reassign the disk using the vDMP client and then recreate a cache area.