This post is more than 5 years old
9 Posts
0
15518
Avamar SQL DB backup failed
Hi ,
The SQL DB backup is failing on server 2008 R2. The details are:
Avamar Server - 6.1.0-402
Avamar Client/SQL Plugin - 6.1.1-402
Client OS - Windows 2008 R2
Client machine - Virtual Machine
SQL Version - SQL 2008
The error is as follows:
2013-01-23 21:31:07 avtar Error <5064>: Cannot open file "C:\Program Files\avs\var\avsql_t1_p_cache.dat" (Log #2)
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.
Thank You in advance.
Regards
Sri
+919740082368
fdxpilot
143 Posts
2
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.
Sandeep_Sinha
307 Posts
2
January 24th, 2013 05:00
Hello,
Please refer to these articles :
http://solutions.emc.com/EMCSolutionView.asp?id=esg108226&usertype=C
http://solutions.emc.com/EMCSolutionView.asp?id=esg95612&usertype=C
shreiks
9 Posts
0
February 4th, 2013 23:00
Hi,
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.
Thanks for your support
Srikanth
ionthegeek
2K Posts
1
February 5th, 2013 07:00
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.
shreiks
9 Posts
0
February 6th, 2013 03:00
Hi,
So does it mean that it will take full backup always. Is there any way to troubleshoot and see why its not able to retrieve the log gap path
ionthegeek
2K Posts
0
February 6th, 2013 07:00
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.
pp082c
38 Posts
0
October 21st, 2014 05:00
Hi,
Is your issue resolved !
Can you please post the complete logs over here
If this is the Error which triggers only for a DB sql backup rather than the filesystem which completes fine.
ORA-27030: skgfwrt: sbtwrite2 returned error
Error messages from Avamar log:
2014-10-20 05:53:26 avtar FATAL <5225>: Unable to open hash cache in directory '/usr/local/avamar/var'
2014-10-20 05:53:26 avtar Info <6149>: Error summary: 2 errors: 5225, 5064
It would be a permission issue on /var/avamar directory.
777 is a full permission and therefore DB’s should Have this permissions to run RMAN
Try if this works