Cannot Delete Backup Files from Managed Hardened Repository

[GregorS]

Case #07590657 - yet unanswered since I'm on an NFR license testing Managed Hardened Repository 0.1.17 (MHR thereafter).

I'm unable to delete backup files from disk. I performed the action "Delete from disk" but it returned some warnings:

Code: Select all

"03.02.2025 14:28:11 Warning    [Test Backup Job to Managed Hardened Repository - <VM name>] Backup deleted with warning"
"03.02.2025 14:28:11 Warning    Failed to delete storage /mnt/veeam-repository01/Test Backup Job to Managed Hardened Repository/<VM name>.vm-159563D2025-01-10T114822_CE45.vbk."

The immutability period expired on 17.01.2025. This behavior was unexpected to me. Now the backup is removed from the VBR console (= from configuration database) but the backup files (.VBK) remained on the repository disk. How can I easily remove backup files from an MHR that are not (should not be) time protected anymore? Without root access we need a kind of a file explorer to manage orphaned files on MHR or else it will quickly become completely unusable if we cannot touch files on it after every hiccup that may occur in production.

Regards,
Gregor

[david.domask]

Hi GregorS,

Sorry to hear about the challenges, at first blush based on your description, the behavior is not expected.

Are you able to check the VBK file on the repository itself with lsattr and see if the immutable bit is set?

e.g.,

lsattr /data/backups/some-backup.vbk

It would be initial guess that perhaps the immutability bit didn't get removed as expected for some reason.

With NFR license, please keep in mind that support is provided on a "best-effort" basis, so your patience is appreciated. Please do upload logs to the case as well for review. (use the 3rd radio button to export logs from hosts, select the Veeam server itself and the hardened repository to export logs from)

[GregorS]

Hi David!

Are you able to check the VBK file on the repository itself with lsattr and see if the immutable bit is set?

How can I do that on an MHR? Is there shell access?

It would be initial guess that perhaps the immutability bit didn't get removed as expected for some reason.

Which process is responsible for removing the immutability attribute? Does the action Delete from disk also check and remove the attribute before deletion attempt? If not, it should, it's a bug to be addressed.

Thank you for the export log guidance, I uploaded them.

[david.domask]

Aha, you should need to boot to Live Mode from the ISO to get temporary access. There are instructions on the linked User Guide page, and two scripts (one to mount data volumes, one to mount system volume).

Once the live mode is booted and you've mounted the data volume(s), check the backup files in question with the lsattr command, I am guessing they're marked as immutable still, though not clear why.

[GregorS]

Thank you, David! Using the Live System I could remove the offended files and learn something new about MHR. So, case closed.

1. the new password for vhradmin needs to be at least 8 characters long, maybe you should update the user guide on Using Live System since it states "There are no complexity or length requirements." ( complexity NO, length YES >= 8 )
2. sudo vhradmin
3. chmod +x mount_datavol.sh
4. ./mount_datavol.sh
5. cd /mnt/veeam-repository01/<backup name>
6. lsattr *
7. chattr -i *
8. rm *