Symantec logo

Tuning the autogrow attributes

The highwatermark, autogrowby and maxautogrow attributes determine how the VxVM cache daemon (vxcached) maintains the cache if the autogrow feature has been enabled and vxcached is running.

The following behaviors occur when cache usage reaches the high watermark value:

If the autogrow feature has been disabled, the following behavior occurs:

The vxcached daemon does not remove snapshots that are currently open, and it does not remove the last or only snapshot in the cache.

If the cache space becomes exhausted, the snapshot is detached and marked as invalid. If this happens, the snapshot is unrecoverable and must be removed. Enabling the autogrow feature on the cache helps to avoid this situation occurring. However, for very small caches (of the order of a few megabytes), it is possible for the cache to become exhausted before the system has time to respond and grow the cache.

In such cases, either increase the size of the cache manually, or use the vxcache set command to reduce the value of highwatermark for the cache object, as shown in the following example-

# vxcache -g mydg set highwatermark=60 cobjmydg

See Growing and shrinking a cache.

You can use the maxautogrow attribute to limit the maximum size to which a cache can grow. To estimate this size, consider how much the contents of each source volume are likely to change between snapshot refreshes, and allow some additional space for contingency.

If necessary, you can use the vxcache set command to change other autogrow attribute values for a cache. See the vxcache(1M) manual page for details.

Ensure that the cache is sufficiently large, and that the autogrow attributes are configured correctly for your needs.