Corrupted Backup Object Disk Issue

Product version: 11.0

Last modified: 07 August 2025

Problem

The VM backup job has failed with the following error:

error72 - reason=LAST_SAVEPOINT_CORRUPTED ("Corrupted backup object disk (ActionException)")

This error occurs when the Transporter fails to write data to the Backup Repository or move data from the transit folder to the final Backup Object folder. The issue is most commonly seen with cloud-based repositories such as S3 or Wasabi, where write or move operations may be interrupted due to connectivity issues, permission errors, or storage limitations.

Solution

To solve this issue, follow these steps:

  1. Ensure the SSL/TLS certificate used by the cloud repository (e.g., S3, Wasabi) is valid and not expired.

  2. Confirm that the system where the Transporter is running has proper DNS settings.

  3. Enable Explicit File System Sync:

    1. Go to Settings > Repositories and edit the affected repository.

    2. Navigate to the Options tab and select the Enforce explicit file system sync checkbox.

    3. Save the changes.

  1. Limit the Transporter load:

    1. Go to Data Protection and edit the Backup job.

    2. Navigate to the Options tab and set the Transporter load to 1 concurrent task to reduce concurrency and potential file system conflicts.

  2. Ensure that the Options > Active Full backup checkbox is selected for the affected job.

  3. Once the above changes are applied, run the Backup job.