Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

vxcached(1m) [hpux man page]

vxcached(1M)															      vxcached(1M)

NAME

       vxcached - resize cache volumes when required

SYNOPSIS

       /etc/vx/bin/vxcached [-v] [mail-address ...]

DESCRIPTION

       The  Veritas Volume Manager cache daemon, vxcached, is invoked by the VxVM kernel to monitor the cache objects that are used by space-opti-
       mized snapshots.  When usage of a cache volume by space-optimized snapshots reaches the high watermark level that  has  been  set  for  the
       cache, vxcached automatically grows the cache volume if this is required and configured.

       The -v option enables the daemon in verbose mode.  If no mail addresses are given as arguments, mail is sent to root.

       If  the autogrow feature has been enabled on a cache object, the values of the highwatermark, autogrowby and maxautogrow attributes for the
       cache object determine the behavior of vxcached:

       o  When cache usage reaches the high watermark value, highwatermark, (default value is 90 percent), and the new required cache  size  would
	  not  exceed  the  value  of  maxautogrow (default value is twice the size of the cache volume in blocks), vxcached grows the size of the
	  cache volume by the value of autogrowby (default value is 20% of the size of the cache volume in blocks).

       o  When cache usage reaches the high watermark value, and the new required cache size would  exceed  the  value	of  maxautogrow,  vxcached
	  deletes the oldest snapshot in the cache.  If there are several snapshots with the same age, the largest of these is deleted.

       If the autogrow feature has been disabled on a cache object:

       o  When	cache  usage  reaches the high watermark value, vxcached deletes the oldest snapshot in the cache.  If there are several snapshots
	  with the same age, the largest of these is deleted.  If there is only a single snapshot, the snapshot is detached and marked as invalid.

       The values of the highwatermark, autogrowby and maxautogrow attributes can be set when a cache object is created using vxmake.	If  neces-
       sary, you can use the vxcache set command to change the values of these attributes for an existing cache.

NOTES

       The  vxcached  daemon is started automatically if a license for the FastResync feature is already present on the system.  If you add such a
       license while VxVM is running, you can either start vxcached manually, or shut down and reboot the system.

       Killing the vxcached process stops it from removing snapshots.  The daemon can be prevented from being started by commenting out its  entry
       in the startup script, /sbin/init.d/vxvm-recover.

       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.  If this happens, the snapshot is unrecoverable and must be removed manu-
       ally.  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 reduce the value of highwatermark.

       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.

SEE ALSO

       vxcache(1M), vxintro(1M), vxmake(1M), vxsnap(1M)

VxVM 5.0.31.1							    24 Mar 2008 						      vxcached(1M)

Check Out this Related Man Page

DWWW-CACHE(8)							      Debian							     DWWW-CACHE(8)

NAME

       dwww-cache - manage the dwww cache of converted documents

SYNOPSIS

       dwww-cache --lookup type location
       dwww-cache --store type location
       dwww-cache --list type location
       dwww-cache --list-all
       dwww-cache --clean

DESCRIPTION

       dwww-cache  manages the cache of converted documents; it is part of dwww(7).  An option (the first argument) specifies the operation.  Some
       operations operate on the whole cache, and need no other arguments.  Others need the second and third argument  to  specify  the  type  and
       pathname of the original document.  (See dwww-convert(8) for more information about the arguments.)

       The operations are:

       --lookup
	      If the document is in the cache, output it to the standard output.  Otherwise, output nothing and return a non-zero status.

       --store
	      Read the document from the standard input, output it to the standard output and store it into the cache.	If there was an older ver-
	      sion already in the cache, remove it.

       --list Output information about one document in the cache to the standard output.  The information is one line, with four  space  delimited
	      fields: type, pathname of original, pathname of cached, and permanent flag (y or n).

       --list-all
	      Like --list, but for all documents.

       --clean
	      Forget all cached documents that have been deleted.

       dwww-cache  maintains  a  database  with information of the cached documents.  The documents themselves are stored in separate files in the
       cache directory.  When old documents are removed from the cache by a suitable crontab entry, they will still exist in the  database.   This
       operation removes all entries from the database where either the original or the converted file is now missing.

       To  stop  the  cache from growing too large, an entry in root's crontab should remove cached files that have not been accessed for a while.
       For example, the following commands remove all documents that have not been accessed for ten days:

	      find /var/cache/dwww -atime +10 | xargs rm -f
	      dwww-cache --clean

       The idea is to first delete the old cached files and then clean up the database.  The policy of cleaning the cache has been kept outside of
       dwww-cache  to  keep  the  program simple, and to allow maximum flexibility.  The default dwww installation creates a /etc/cron.daily/dwww,
       which automatically cleans the cache each day.

FILES

       /var/cache/dwww/db
	      The cache directory.

       /var/cache/dwww/db/.cache_db
	      The database with information about all cached documents.  This is a binary file, specially encoded for small size and  high  speed,
	      and should not be touched by anyone but dwww-cache.

SEE ALSO

       dwww(7), dwww-convert(8).

AUTHOR

       Lars Wirzenius <liw@iki.fi>.  Modified by Robert Luberda <robert@debian.org>.
       See dwww(7) for copyrights and stuff.

dwww 1.11.1							February 15th, 2009						     DWWW-CACHE(8)
Man Page