Avamar - How to check the Avamar client log for file cache or hash cache sizing issues

Locate the client log for the latest backup: Avamar: How to gather logs to troubleshoot backup and restore issues

Search the log files for 'cache' (case insensitive).
 

If the file cache f_cache.dat is sized too small, the log contains a message similar to:

2013-09-1702:29:35 avtar Warning <5650>: CAPACITY WARNING: The file cache is full;filecachemax=127MB, should be at least 177MB

If the hash cache (p_cache.dat) is sized too small, the log contains a message similar to:

<HASH_CACHE>entries=2097152,added=709614, overflow=56849</HASH_CACHE>

An undersized file cache or hash cache has a dramatic effect on the speed of a backup.

If there is a backup performance issue, only change the cache file configuration if the caches are undersized for the amount of data to be backed up.

Inappropriately sized monolithic cache files can cause excessive memory consumption on the client. This can result in problems on the client while backups are running.

For information about tuning the client cache files, see the following:

• Avamar Operational Best Practices guide
• Knowledge Article Avamar - How to set the size of Avamar client caches to prevent cache overflows from causing backup performance problems

See article: Avamar: Troubleshooting slow backup performance