Committing a Backup Job for Virtual Server Agents
Administrators can commit a backup job for a subclient that protects multiple virtual machines in the following situations:
- Commit a running backup job when backups for one or more virtual machines have completed, and you want immediate access to backup data without waiting for other VMs in the job to complete.
- Commit scheduled backup jobs automatically to interrupt jobs that are running beyond a scheduled backup window.
About This Task
When the job is committed, any virtual machine backups that have completed successfully are retained, and the current index for the job is archived so that backed up VMs can be browsed for restores. All virtual machine backups that are not yet completed are marked as failed so that those virtual machines can be protected when a subsequent incremental job is run to back up unprotected virtual machines.
- A backup job commit is available only for regular streaming backup jobs. Commit is not available for synthetic full backups, SnapProtect backups, backup copy, or catalog snapshot jobs.
- The Commit option is available for running jobs when at least one full virtual machine is completed, and at least 2 GB of data have been written for the backup job.
- Only active running jobs can be committed, not suspended, waiting, or killed jobs. If a backup job is suspended and then resumed, the resumed job must write at least 2 GB of data before the Commit option is available.
- When you run a job to back up unprotected virtual machines, any virtual machines that were marked as Failed for the original backup job are included in the new job.
Commit requests are submitted automatically for jobs that exceed the expected total running time. You can set the total running time for individual backup job or use schedule policies for Virtual Server Agent backup jobs. For more information, see Setting the Total Running Time for Jobs.
- From the CommCell Console ribbon, on the Home tab, click Job Controller.
The Job Controller window is displayed.
- Right-click a backup job and click Commit.
Note: After backup jobs are committed, the job progress bar for a subsequent backup may not show the actual progress.
- To complete the commit request, click Yes.
When a Commit request is processed, either automatically based on the scheduled backup window or manually by committing a running job, the following actions occur:
- When the job is committed, any virtual machine backups that have completed successfully are retained, and the current index for the job is archived so that backed up VMs can be browsed for restore operations.
- The backup job status changes to Archiving Index, and the index cache is updated for virtual machines that were successfully backed up.
- Any virtual machines that were successfully backed up are marked as Completed in the Job Details window for the job.
- Any virtual machines for which backups were pending or in progress are marked as Failed, so that those virtual machines can be protected when a subsequent incremental job is run to back up unprotected virtual machines.
- When the job completes, it is marked as Completed with errors in the Job Controller window.
- On the Backup History window, the job status is Committed.