Skip to main content
Version: 3.0

Back up Failed VMs

Applicable to Classic mode only

Portworx Backup enables you to retry partial success or failed VM backups with greater precision. This feature enables you to reattempt backup operations specifically for VMs that failed in a prior backup attempt, avoiding duplicate backup of successfully backed-up VMs. For instance, if a backup operation includes multiple VMs and only some fail to be backed up, the retry feature ensures that only the failed VMs are backed up again instead of reprocessing the entire VM set. This allows for more efficient resource usage and provides finer control over VM backup operations, significantly reducing the time involved.

This feature also ensures that the backup status is determined at the individual VM level, including its dependent resources, rather than based solely on underlying volumes or namespace resources. This provides a more accurate reflection of VM backup success or failure.

When a manual backup or scheduled backup is created for one or more VMs, you can retry the backup from the same source. The retry generates a new manual backup that includes only the VMs that failed in the previous attempt.

Portworx Backup creates a new manual backup with a unique name based on the original backup name and the retry timestamp. The new backup includes only the failed VMs. The feature maintains the backup location and volumeSnapshotClass from the original backup, without allowing modifications during the retry. It supports partial success (at least one VM is backed up successfully) and full failure (all VMs selected for the backup failed to be backed up), but does not support namespace-level backups, auto retries, or synced backups. This functionality is supported from Portworx Backup version 2.9.0 onward and requires user intervention to resolve underlying failures before reattempting a retry.

How to retry a failed VM backup​

  1. On the home page, from the left navigation pane, click Clusters.

  2. On the Clusters page, choose the cluster that holds the backup in which some VMs were not backed up.

  3. In the selected cluster page, navigate to Backups tab and then VM tab.

  4. Select the failed or partial success backup and move towards the Vertical Ellipsis at the end of the backup row.

  5. From the Vertical Ellipsis, choose Retry.

    You can also select Retry option from the expandable arrow that appears before every failed or partial success backup in the BACKUP NAME column.

note

You can select only one partial success/failed VM backup (backup with 1 or more failed VMs) for Retry operation.

  1. In the Retry VM Backup window, the following options are available:

By default, retry option selects all the failed VMs of that backup regardless of the search term or OS they belong to.

note

If the original backup was taken with the File-system consistent backup option enabled, you can choose to disable it during a Retry. However, if this option was disabled initially, the Retry does not present this option.

To narrow down the search results, override the default options by deselecting all the failed VMs and applying the following search or filter options:

  • Search by VM name: search by keyword and select specific VMs that have failed based on your requirements.

  • Filter by OS: filter the VMs by the OS they are running.

By default, all the failed VMs are selected for backup. If you have selected only a few VMs and not all failed VMs based on your OS filter, deselect all the VMs and then select the required ones.

You can perform an advanced search for the failed VMs using a combination of the search option and the filter by OS option.

  • Filter by Status: this status is auto-populated with Failed because you are retrying a failed or partial success VM backup.

  • Download CSV: download a detailed CSV report on the failed VMs.

  • Select all the VMs of that backup regardless of search term or OS they belong to.

  • The drop-down at the end of each failed VM entry provides additional details on the failure.

  • Do you want to ignore default rules while retrying the backup?: check this box if you want to ignore the default rules (freeze/unfreeze) associated with the backup.

  1. After selecting the required failed VMs and choosing the required options, click Retry backup to reinitiate the backup operation.

VM backup retry behavior​

  • Rules: If autoExecRules was enabled in the original backup, you can choose to disable it during a retry. However, if autoExecRules was not used initially, the retry does not present this option. In all cases, the retry follows the rule configuration from the original backup.

  • No retry filter changes: labels or advanced filters cannot be modified during VM backup retry.

  • Deleted VMs: retry is not supported for VMs that were deleted after the backup failed.

  • Synced backups: retry fails for synced backups.

  • Backup location: retry uses the same backup location as the original backup.

  • Scheduling: you cannot create schedules for the backups created with retry option.

  • Snapshot class reuse: retry uses the same volumeSnapshotClass as the original backup.

  • Backup type: retry option always triggers a manual backup, even if the original was a scheduled one.

Last updated on