01-15-2019 04:50 AM - edited 01-15-2019 07:25 AM
Summary of problem is in: https://www.veritas.com/support/en_US/article.100002643.html SQL Log Backup job fails if run after an AVVI or Hyper-V backup of the SQL Virtual machine.
So this is the scenario:
Backup Job #1: Dedicated job for SQL databases. Weekly full, Daily diff, Hourly Transasction Logs.
Backup Job #2: VM backup of Hyper-V machines.
Backup Job 2 does a FULL Backup of the SQL Server databases, which caused Backup Job #1 to STOP transaction log backups and revert to FULL COPY backups.
This is known issue, and it looks like it has been there for a while. And it doesn't matter if you select GRT or not. I simply do not need the SQL Server databases to be backed up this way. I want to do a small hourly transaction log backup.
All that is needed to fix this is to put the option on the Hyper-V backup: "Do a COPY of the SQL Server databases." So the backup command that Backup Exec sends is "Backup database [name] WITH COPY ONLY".
The "COPY ONLY" will then not interfere with the LSN numbers that are required for Backup Job #1.
Thank you.
01-15-2019 11:12 AM
Can you check the job properties and see if Application GRT is enabled for SQL in the Hyper-V job (Under the Virtual machines section of the job properties)? If it is, try just unchecking that box. This should stop the Hyper-V job from processing the SQL databases.