When doing an Agent for VMware Virtual Infrastructure (AVVI) or Agent for Hyper-V backup, the SQL logs are not truncated and a follow up SQL Log backup will then also fail.
V-79-57344-38728: The SQL Database '<dbname>' on '<vmname>' is configured to maintain transaction logs, but transaction log backups are not being performed. Not backing up the transaction log results in the log growing in size until it fills all available disk space. You should either schedule regular logs backups or change the database to the simple recovery mode.
0xe0000363 V-79-57344-867: The Backup Exec SQL Agent was not used to create the last full, differential, or log backup of this database. You must use the SQL Agent to run a full backup before you can run a differential backup or transaction log backup.
V-79-40960-37914 - Database <dbname> is configured to maintain transaction logs. Transaction log backups are not being performed. This will result in the log growing to fill all available disk space. Regular log backups should be scheduled or the database should be changed to the simple recovery mode.
When an AVVI or Hyper-V backup job runs, a Full SQL backup is performed which does not truncate the logs. This job also records the last backup requestor for the database in SQL as NULL or NONE instead of the Backup Exec SQL Agent, because it was the VM snapshot process that made the last backup request. This then causes a later SQL Log job to also fail, as long as a Full SQL job has not been run since the AVVI or Hyper-V backup job.
For more information on how to identify the requester please see: www.symantec.com/docs/TECH58674
To backup a SQL Server located inside a Virtual Machine (VM), that is not configured for Simple Recovery Mode and to truncate the logs, run standard SQL Agent Full and Log backup through the remote agent installed inside the VM.
If AVVI or Hyper-V backup jobs are still scheduled, these must be scheduled so that they do not interrupt the sequences of SQL Agent Full and Log backup jobs.
Media Server: Backup Exec 2010, R2 or R3 and BE 2012
Operating Systems: Windows 2003, Windows 2008 (all variations)
SQL Versions: All Supported
ESX version: 4.x or Hyper-V