2013-01-23 21:31:07 avtar Error <5803>: Error writing 32-byte header to cache file C:\Program Files\avs\var\avsql_t1_p_cache.dat. Possibly out of disk space (Log #2)
2013-01-23 21:31:07 avtar FATAL <5225>: Unable to open hash cache in directory 'C:\Program Files\avs\var' (Log #2)
I tried both Incremental and Full backup. Both failed. Please let me know how toresolve this issue.
Kill any avtar and avsql processes running on the machine and try again. Avamar has a bad habit of leaving hung processes running which will lock the cache file. Hopefully an enhancement is coming soon to remeny this condition.
I did the above steps and got the issue resolved for couple of days and now again the backups fail. When i take a full backup (manually) the backup completes with exception. I am getting thios exception even for incremental scheduled backups. I am not sure whether it can be ignored or any step has to be taken. The error i am getting is:
avsql Error <15762>: Skipping incremental backup after full for (local)/BLODS database. Error: Unable to get log gap detection data.
Backups of the (local)/BLODS database will only be fulls if the client is unable to get log gap detection data. The log gap detection data is used to ensure that the log chain for this database is intact before the software permits an incremental to run. If there is a gap in the logs (for example because the DBA ran a native SQL backup which truncated the logs), any Avamar incrementals created after the gap would not restore correctly.
If the Avamar SQL plug-in can't retrieve log gap data, it plays it safe and does not permit an incremental to run since the integrity of that incremental backup could not be guaranteed.
Is the BLODS database configured with the Simple Recovery model? Databases configured for Simple Recovery do not support transaction log backup so log gap detection data would not be available. If the database is using a different recovery model, I would recommend opening a service request so support can investigate.
fdxpilot
2 Intern
•
143 Posts
7455
2
Posted January 25th, 2013 20:00
Kill any avtar and avsql processes running on the machine and try again. Avamar has a bad habit of leaving hung processes running which will lock the cache file. Hopefully an enhancement is coming soon to remeny this condition.