Veeam Backup & Replication 10
User Guide for Microsoft Hyper-V
Related documents

Automatic Job Retries

Veeam Backup & Replication automatically retries several operations that are performed within a backup copy job session.

Job Tasks Retry

By default, Veeam Backup & Replication automatically retries a failed backup copy task 5 times within one backup copy job session. A new task is started immediately after the previous one, without any interval.

The backup copy task is retried only if the previous task has failed and a restore point has not been copied to the target backup repository. Veeam Backup & Replication does not perform a retry if a task has finished with the Success or the Warning status.

The backup copy task is retried during the same backup copy session only. If a restore point fails to be copied during all retries in the current backup copy session, Veeam Backup & Replication marks the current task as failed. In case of the periodic copy mode,  Veeam Backup & Replication also waits for the expiration of the backup copy interval. After that, Veeam Backup & Replication performs the necessary transform operations and starts a new backup copy session.

A backup copy job can process several machines. If only some machines are successfully processed by the backup copy task, Veeam Backup & Replication creates a restore point holding data for these machines on the target backup repository. Veeam Backup & Replication will attempt to process restore points for all machines during the next backup copy session.

Automatic Job Retries Note:

Some errors from WAN accelerators can block backup copy job retries. For example, if there is no space in the global cache on the target WAN accelerator, Veeam Backup & Replication put backup copying operations on hold and wait for the expiration of the backup copy session.

Transform Retry

After the backup copying task, Veeam Backup & Replication may perform a number of additional transform operations on the target backup repository. These operations include the backup chain transform, removing of deleted machines from restore points and compacting a full backup file. For more information, see Transform Operations.

Veeam Backup & Replication may fail to perform transform operations: for example, if the backup file on the target backup repository is locked by the file-level restore session. By default, Veeam Backup & Replication automatically retries transform operations for 5 times. The first interval between retries is 1 minute; the interval doubles with every new attempt. If all retries of transform operations failed, Veeam Backup & Replication does the following:

  • [For the immediate copy mode] Stops the job with the Fail status and waits for the new job session.
  • [For the periodic copy mode] Puts the job to the idle state and waits for the new backup copy interval to begin.

Virtual Infrastructure Access Retry

At the beginning of every backup copy session, Veeam Backup & Replication accesses the virtual infrastructure to make up a list of machines processed by the job.

Veeam Backup & Replication may fail to access the virtual infrastructure for some reason: for example, in case the Hyper-V host is not responding. By default, Veeam Backup & Replication automatically retries access operations for 5 times with a 5 minute interval.

This Document Help Center
User Guide for VMware vSphereUser Guide for Microsoft Hyper-VVeeam Backup Enterprise Manager GuideVeeam Agent Management GuideVeeam Cloud Connect GuideVeeam Explorers User GuideVeeam Plug-ins for Enterprise Applications GuideVeeam PowerShell ReferenceVeeam Explorers PowerShell ReferenceVeeam RESTful API ReferenceRequired Permissions for VMware vSphereQuick Start Guide for VMware vSphereQuick Start Guide for Microsoft Hyper-VVeeam Backup for AWS DocumentationVeeam Availability for Nutanix AHV DocumentationVeeam Backup for Microsoft Office 365 DocumentationVeeam ONE DocumentationVeeam Agent for Windows DocumentationVeeam Agent for Linux DocumentationVeeam Management Pack Documentation
I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.