With the Backup Retry option, you can specify the number of times you want Phoenix to retry a failed scheduled backup job. By default, Phoenix sets the Automatic Retry field to 2 with a 10-minute interval between the two attempts. However, you can change the number of retries while configuring or reconfiguring the backup policy. The maximum number of retry attempts allowed is 99, and the maximum interval between each two retry attempts can be 1440 minutes.
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. 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
Phoenix provides the ability to automatically retry the backup jobs within a scheduled backup window. Automatic retry is not applicable to the transaction log backup.
- Log on to Phoenix Management Console.
- On the menu bar, click All Organizations, and select the required organization from the drop-down list.
- On the menu bar, click Manage > Backup Policies.
- Click Create New Backup Policy and select the required server or virtual machine from the list.
- On the Summary tab, type the name and description of the backup policy and click Next.
- On the Backup Schedule tab, select the Automatic Reply check box to define the automatic retrial options for backup.
- From the Max number of retries list, select the maximum number of retry attempts for a job.
- By default, the field is set to 2 attempts.
- From the Wait interval before each retry list, select the wait interval between each retry.
By default, the field is set to 10 minutes.
- Click Next and provide pre-script and post-script settings, if applicable.
- 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.