Also, it would be better if you delete the old f_cache and f_cache2 and see how the backup runs.
The file cache (1/8 of physical RAM) must have reached the limit.
Deleting the cache files is likely to be counterproductive. Most of the performance gain for filesystem backups comes from the file cache so if you delete it, you're basically doing a new full during the next backup.
The limit you mentioned only applies to the monolithic cache (i.e. f_cache.dat). It does NOT apply to the paging cache (f_cache2.dat).
Please check the free space on the disk on the client server where the cache files are present. Also, it would be better if you delete the old f_cache and f_cache2 and see how the backup runs.
The file cache (1/8 of physical RAM) must have reached the limit.
ionthegeek
2 Intern
•
2K Posts
3
March 13th, 2015 07:00
Deleting the cache files is likely to be counterproductive. Most of the performance gain for filesystem backups comes from the file cache so if you delete it, you're basically doing a new full during the next backup.
The limit you mentioned only applies to the monolithic cache (i.e. f_cache.dat). It does NOT apply to the paging cache (f_cache2.dat).
Pratique2511
82 Posts
1
March 13th, 2015 07:00
Please check the free space on the disk on the client server where the cache files are present. Also, it would be better if you delete the old f_cache and f_cache2 and see how the backup runs.
The file cache (1/8 of physical RAM) must have reached the limit.
Pratique2511
82 Posts
0
March 13th, 2015 08:00
Oh yes, thanks for correcting that. I dint see the .dat extension.