SQL Log backup checkbox if selected results in a SQL Full Copy backup being run after Differential or Incremental SQL Virtual Machine Backup.
To perform a SQL Application Virtual Machine Backup which is located on a Hyper V Server, it is recommended to enable this checkbox "Enable GRT for Microsoft SQL ( database-level only ) on virtual machines".
To ensure the SQL log backup is performed after every Full , Diff or Incremental ( depending on how the Job definition is setup ) it is recommended to also select "Run a SQL Log backup after backing up the virtual machine".
In this case the log backup of SQL runs after the Full VM backup completes, however after a Differential or Incremental VM backup a SQL Copy Full backup is run instead of a SQL Log backup, which adds more size to the Backup Job.
This issue is resolved in Backup Exec 23
Workaround:
After the Full Backup completes, a Log backup is run.
If a Differential or Incremental definition is added to the Job, which does the Differential or Incremental VM backup but also end up doing a Full SQL Copy Backup of the SQL Instance.
Therefore, ensure enough space is available when those two checkboxes are selected:
"Enable GRT for Microsoft SQL ( database-level only ) on virtual machines"
"Run a SQL Log backup after backing up the virtual machine"
or
Remove the Incremental/Differential stage and run the Full backup more frequently.
Note:
If the log backup of the SQL instance (databases) are required more frequently, an agent based backup can be run which includes Full, Incremental and frequent Log backup strategy.
Differential or Incremental Hyper-V SQL Virtual Machine backup runs a SQL Copy Full Backup instead of a SQL Log Backup.
The same issue is not seen when the SQL Virtual Machine is located on a VMware ESX system.
A Log Backup of the SQL Instance for Differential and Incremental VM backup is performed as expected.
ETrack: 4029357