Tuesday 22 January 2013

Avamar client files f_cache.dat and p_cache.dat

At the beginning of a backup, the Avamar client process, avtar, loads two cache files from
the var directory into RAM
  •  f_cache.dat (a.k.a "File Cache")
  • p_cache.dat (a.k.a "Hash Cache")

The f_cache.dat cache file stores a 20-byte SHA-1 hash of the file attributes, and is used to
quickly identify which files have previously been backed up to the Avamar server.

The p_cache.dat hash cache stores the hashes of the chunks and composites that have
been sent to the Avamar server. The hash cache is used to quickly identify which chunks
or composites have previously been backed up to the Avamar server. The hash cache is
very important when backing up databases.

By default, the maximum File Cache size can be 1/8 of the RAM and the maximum Hash Cache size will 1/16 of the RAM.

Because the avtar program is a 32-bit application, the maximum file cache size that avtar
can use is limited to less than 2 GB. In an example where a client has 4 GB of RAM, the
maximum size of the file cache is 352 MB.
Each entry in a file cache comprises a 4-byte header plus two 20-byte SHA-1 hashes (44
bytes total):
  • SHA-1 hash entry of the file attributes. The file attributes include: file name, file path, modification time, file size, owner,group, and permissions.
  •  SHA-1 hash entry for the hash of the actual file content, independent of the file attributes.

8 comments:

  1. thank you Jean. could you please let me know how to /var/avamar/p_cache.dat file in Unix or how to recreate it.

    thank you .:-)

    ReplyDelete
  2. Hello Reena.
    The cache files are created automatically the first time your run a backup on a client. A simple restart of "avagent", followed by a manual backup should do it.

    ReplyDelete
  3. Hi,
    Could you let us know how to clean up these dat files, since they are occupying much space in /var

    ReplyDelete
  4. hi Jean,
    one our client's F_cache size is 12 GB. can we try deleting it and allow avamar to recreate during next backup ?

    ReplyDelete
  5. Hi Reena

    this can be delete, the only problem here is, Backup will take more time than time taken by last backup. However there will no other impact.

    ReplyDelete
  6. Hi, it's possible to change location for f_cache2.dat ,because the /var is always full
    Thank you

    ReplyDelete
  7. why this thread is not talking about possibilities to move the Avamar client cache to some kind of centralized file-share? Avamar is filling up /var on all our Linux machines and it becomes a burden for the operations team having to increase storage for /var on several hundred of Linux machines.

    ReplyDelete
  8. The cache when local to the cLient gives you the best backup performance. You can always split your dataset and allocate dedicated cache files to them. Contact emc for more

    ReplyDelete