Managing Your SQL Backup Jobs

As explained above, with log backup switched on, SQL Server backup job comprises 2 jobs:

1. ‘Parent’ job, which performs image-level VM backup and is explicitly created and named by user as <job_name>, for example, MyTestJob.
2. ‘Child’ job, which performs transaction log processing and is named automatically using SQL Backup suffix: <job_name> SQL Backup. So, for our example it will be MyTestJob SQL Backup.

Child job is created by Job Manager if it detects that there is a parent job, scheduled to backup at least one SQL Server VM, with application-aware image processing enabled.

Parent job session starts on schedule or is started manually by user; child job (transaction log processing) follows it - to ensure that full backup is periodically created, and log backups then will be of use to restore the VM to the required state. Child job (transaction log processing) runs permanently in background with the specified interval. It can be stopped or disabled under certain conditions.

In This Section

• Starting, Stopping, Enabling and Disabling the Job
• Viewing Job Information
• Reconfiguring Jobs with Microsoft SQL Server VMs
• Log Backup Import