Backup failed with access denied, now files are missing

[Flole]

Case #07420915

For some reason a backup to a B&R repo failed with:

Code: Select all

Failed to apply retention policy
Full backup file merge failed Error: Agent: Failed to process method {Transform.Patch}: Access is denied. Failed to duplicate extent. Target file: D:\XXXXXX\XXXXX\XXXXXX_2024-08-28T024413.vbk, Source file: D:\XXXXXX\XXXXX\XXXXXX_2024-08-29T024233.vib, TgtOffset: 5270253142016, SrcOffset: 59304116224, DataSize: 1114112
Failed to perform transform operation Error: Agent: Failed to process method {Transform.Patch}: Access is denied. Failed to duplicate extent. Target file: D:\XXXXXX\XXXXX\XXXXXX_2024-08-28T024413.vbk, Source file: D:\XXXXXX\XXXXX\XXXXXX_2024-08-29T024233.vib, TgtOffset: 5270253142016, SrcOffset: 59304116224, DataSize: 1114112
Full backup file merge failed
Failed to perform backup

and now all backups are failing with "Some backup files are missing in repository". I assume that this is a bug, and I need help recovering from this situation without deleting the whole repository and starting over. Also someone might want to look into how this happened in the first place.

[PTide]

Hi,

Would you double check the case number please? I don't see this number in our internal tracking system.

Thanks!

[Flole]

I have double-checked it, the case number is definitely 07420915, I have copied it from the support portal.

[Flole]

Now the case has been closed. Sad, that nobody wants to have a look at something that appears to be a critical bug anymore which leads to corruption of backups. I have "fixed" my issue by starting over with a clean repo again.

[PTide]

Hi,

We will review the case tomorrow and see what can be done. Depending on the outcome the case might be reopened and escalated. Stay tuned.

Thanks!

[rovshan.pashayev]

Hi Flole,

Your case involved a product that used a free license, and due to limited availability of support staff, we were unable to process your request. As a result, the support case has been automatically archived.

However, please reopen a new case and post it here so that we could assist you once support staff becomes available.

[Flole]

I have opened case #07433780.

In the meantime I recovered from this situation by deleting the whole repo and starting over, so this bug report is only for you to further improve the product and prevent this issue from occurring on other, critical instances.