Skip to main content

How can we help you?

Druva Documentation

Backup retry


By default, Druva Phoenix retries a job twice with a ten-minute interval between the two attempts.

The Backup Retry feature ensures the following:

  • Higher backup success rate, if a backup is failing due to transient issues in your environment. 
  • Optimum utilization of the scheduled window.

 The backup retry for a job is performed only if a job fails. Druva Phoenix does not perform backup retry for jobs that have successfully finished but with errors. 

Note: An automatic job retry is not triggered for a manually triggered job.

Configure backup retry

You can configure automatic retry for the Hyper-V workload via the Manage Backup Policies option. The other workloads in Druva Phoenix automatically retry failed jobs twice in a ten-minute interval.  Automatic retry is not applicable to transaction log backups.


  1. Log in to the Phoenix Management Console. 
  2. On the menu bar, click All Organizations, and select the required organization from the drop-down list.
  3. On the menu bar, click Manage > Backup Policies.
  4. On the Manage Backup Policies page, you can either edit an existing MS-SQL or Hyper-V policy and edit the automatic retry settings, or create a new backup policy for these workloads and define the automatic retry setting. 
  5. Click Create New Backup Policy and select Hyper-V.
  6. In the Summary tab, type the name and description of the Hyper-V backup policy and click Next.
  7. In the Backup Schedule tab, define the schedule for the backup.  Select the Automatic Retry checkbox and enter the automatic retry settings for backup.
    Automatic retry Hyper-V.png
  8. In the Max number of retries field, enter the maximum number of retry attempts for a job. The default value is two retries.
  9. In the Wait interval before each retry list, enter the wait interval between retry attempts. The default value is ten minutes. 
  10. Click Next and provide pre-script and post-script settings, if applicable.
  11. Click Finish to create the backup policy.

Any changes made to the Automatic retry settings during an ongoing job retry will take effect only in next job retry cycle. 

  • Was this article helpful?