UNSOLVED

dileep451

updated

11 years ago

D

dileep451

1 Rookie

82 Posts

0

3908

March 12th, 2015 21:00

Backup completed with exceptions,"Unable to write to cache '/usr/local/avamar/var/f_cache2.dat"

Hi All.

I am seeing this error frequently for the linux server backup. any suggestions would be appreciated.

Here are the logs...

015-03-11 17:02:47 avtar Error <18905>: Unable to write to cache '/usr/local/avamar/var/f_cache2.dat' (Log #1)
2015-03-11 17:02:47 avtar Error <18899>: Write to cache /usr/local/avamar/var/f_cache2.dat failed, creating incomplete backup and additional pages will not be stored on disk (Log #1)
2015-03-11 17:03:58 avtar Error <18898>: Unable to write page 146 due to earlier write errors in backup. (Log #1)
2015-03-11 17:04:23 avtar Error <18898>: Unable to write page 147 due to earlier write errors in backup. (Log #1)


Is this because of more change in data?


2015-03-11 17:07:19 avtar Warning <18902>: Backup 12 is incomplete due to page write errors
2015-03-11 17:07:29 avtar Warning <5079>: Large number of entries (303317 > 50000) in directory "/z8ub/diag/adump" -- Listing not perfectly sorted.


2015-03-11 17:09:40 avtar Warning <18902>: Backup 12 is incomplete due to page write errors
2015-03-11 17:09:42 avtar Warning <5079>: Large number of entries (141962 > 50000) in directory "/z8ud/diag/adump" -- Listing not perfectly sorted.

  • ionthegeek

    2 Intern

    2049 Posts

    2131

    3

    Posted March 13th, 2015 07:00

    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).

  • 2131

    1

    Posted 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.

  • 2131

    0

    Posted March 13th, 2015 08:00

    Oh yes, thanks for correcting that. I dint see the .dat extension.