07-17-2017 12:17 PM
Each time our incremental backup job runs, SQL registers two backup jobs. Is this normal behavior? Here are the details:
When reviewing the BackupExec log for the job, it runs the VMDK backup first and includes that it "discovered and protected Microsoft SQL Server data on virtual machine 'server.mydomain.com'". That takes about 4 minutes.
It then proceeds to the SQL-specific backup. It performs consistency checks and then backs up the 13 databases.
I think that's all normal and to be expected. The DBA managing the application in question sees the following behavior in the SQL logs during an incremental backup (attached):
My DBA is only expecting to see steps 8 and 9.
The most important question for me right now is this: Am I correct in my understanding that the VMDK backup is what is logging steps 1-6 (i.e. this is expected behavior)?
Secondarily, is there a more efficient way to be doing this or is this the best way to protect both the VMDK and SQL?
07-18-2017 07:19 PM
Since option "Run a SQL Log backup after backing up the virtual machine" is selected in VM job (VMware agent), you are seeing events 1-6. When this option is selected, Backup Exec backs up the SQL logs for the databases that use logging. After the logs are backed up, the data from the logs is committed to the database and the log is emptied so that it can receive new data.
More details are documented in : https://www.veritas.com/support/en_US/article.000109164
Since you are already running a separate backup job to protect SQL database and logs it is not required to select the above option in VMware job.
In case of disaster recovery scenario you may recover the complete VM using VMware backup set and run another restore job to restore SQL databases and logs.
Thanks and Regards,
Riyaj