Loading...
Loading...
The hard drive where the Avamar client writes log files may become full, causing subsequent backups to fail due to the inability to write new log files. Disk space on the Windows client where the Avamar client software is installed (usually the C drive) runs out due to paging cache files named "f_cache2.dat" growing increasingly larger.
A new demand-paging cache format introduces a mechanism to minimize RAM requirements. The client loads small parts of the demand-paging cache to RAM based on the directory currently being processed by the backup. The cache adjusts its size automatically based on the type and amount of data the client backs up. The size of the demand-paging cache on the disk is approximately 20 times higher than the size of the monolithic cache (file and hash cache). The size of the demand-paging file cache is approximately 1 GB per 10 million files on the client, multiplied by the 16 consecutive backups kept in the cache. You can calculate the approximate size of the demand-paging file cache using the following formula: (# of millions of files) / 10 * 1 GB * 16 = (# of GB required for demand-paging file cache)
To redirect the cache files and logs to a specified drive and folder, follow these steps: Create an avtar.cmd file in the avs\var directory. Add the following flag to the file: --vardir=<<drive volume and var folder>> Example flag: --vardir=D:\avs\var Create the var directory on the alternate drive. Copy the existing cache files to the new folder before the next scheduled backup.
Click on a version to see all relevant bugs