Rerunning partially completed backup jobs

If the last instance of a backup job was partially completed, you can rerun the job to back up virtual machines and databases that were skipped.

About this task

A backup job can be rerun only in the same session ID as the original partially completed backup job. No successful backup of the same resource can have completed since the partial backup job you choose to rerun.

Note: Backup jobs can be rerun only in response to a hypervisor or database backup failure. The following events do not qualify for backup job rerun operations:

A VM backup was completed with an FLI failure.
A snapshot condense failure occurred for a storage system.
A backup job failed with an unknown issue such as a cataloging error.
A resource is missing from the vCenter.

For applications for which log backups are supported, log backups are not disabled when using the rerun feature. Log backups will be disabled for the applicable databases when the job is next started without using the on-demand backup or rerun feature.

Procedure

Complete the following steps to rerun a partially completed backup operation:

In the navigation pane, click Jobs and Operations and then click the Job History tab.
Use the search function and filters to find the last instance of the backup job that was partially completed.
Select the job instance, then click Rerun.

Note:
If the backup job cannot be rerun, the Rerun option is not available.

All SLA options and any exclusions that are associated with the original job are included in the rerun operation. No option or exclusion changes are applied since the partial backup completed. If the rerun job is completed successfully, the job summary is updated to show success.