Avamar: SQL Database Backup Fails with Operating System Error 0x80070002 Due to Concurrent Backups

Avamar SQL Backup Failures Observed

The following symptoms are commonly reported when Avamar SQL database backups encounter issues:

• Backup jobs (FULL, INCREMENTAL, or DIFFERENTIAL) fail consistently at approximately the same time each day.
• Backup logs contain error entries similar to the examples below.

Typical Error Messages in the Backup Log

avsql Error <9072>: sqlconnectimpl_smo::execute Microsoft.SqlServer.Management.Common.ExecutionFailureException: An exception occurred while executing a Transact-SQL statement or batch. ---> System.Data.SqlClient.SqlException: Cannot open backup device '(local)_XXXXXXXXXXXXXXXXX#1-3006-SQL'. Operating system error 0x80070002(The system cannot find the file specified.).
avsql Error <6478>: VDS::Getconfig failed with 'The api was waiting and the timeout interval had elapsed'
avsql Error <6479>: Timed out. Was Microsoft SQLServer running? 

Backup Collision Leading to Operating System Error 0x80070002

Primary Contributing Factors

The Avamar SQL backup fails because another backup process accesses the same SQL resources at the scheduled time. This conflict generates file‑access errors and VDS timeouts.

• Concurrent native Microsoft SQL Server backup jobs.
• Third‑party backup software running simultaneously with Avamar.
• Both processes attempt to open the same backup device, causing the file not to be found.

Prevent backup collisions by adjusting scheduling

Step‑by‑step resolution

• Identify any native Microsoft SQL Server or third‑party backup jobs that run at the same time as the Avamar backup.
• Open the Windows Task Scheduler or the third‑party backup console and locate the conflicting jobs.
• Disable the identified jobs or change their start time so they do not overlap with the Avamar schedule.
• Save the changes and ensure the new schedule does not conflict with other critical processes.
• Restart the SQL Server Agent (if applicable) to apply the new schedule.
• Run a manual Avamar SQL backup to confirm the issue is resolved.