Question

Experiences with orphaned backup files


Userlevel 7
Badge +4

This week I was investigating some imbalance in size on two (scale out) repositories. Every repository gets the backup of a subset of all VMs and copy these to the second repository. And vice versa. So in theory, both repositories should be very similarly utilized. But when you look at volume properties, this is not the case. We see quite a large difference. So I used PowerShell to query VBR and sum all data of each VM on both repositories (I will post some code snippets next week). And I found out, VBR does not know about a notable amount of data (VBR-query showed much less used data than volume properties did).

So there seems to be backup data, VBR is not aware of. I call these files orphaned files. What are your experiences with orphaned files? Do your see them very often or not at all? Or are you not aware of their existence? Please let us know.


10 comments

Userlevel 7
Badge +2

Very interesting, are you using a backup copy job in pruning mode?

Userlevel 7
Badge +4

Very interesting, are you using a backup copy job in pruning mode?

Yes, periodic backup copies.

Userlevel 7
Badge +4

Finally I analyzed the difference of both SOBR (each about 500TB in size). On one of them I could find about 20TB of orphaned files. - about 3000 vib-files. The other one had no one! Sadly history does not go back that far, so I cant see what happened with the jobs.

I will (I promise) post some code snippets I used to analyze next week

Userlevel 7
Badge +4

Finally I analyzed the difference of both SOBR (each about 500TB in size). On one of them I could find about 20TB of orphaned files. - about 3000 vib-files. The other one had no one! Sadly history does not go back that far, so I cant see what happened with the jobs.

I will (I promise) post some code snippets I used to analyze next week

Here is the link for how to analyze used repository space using PowerShell:

 

Userlevel 7
Badge +4

[update]

I have some news about this. My customer opened a Support case. In an older build of 9.5 there was a bug, it causes VIB-files left on repository without any reference in Veeam DB. File was merged with full correctly but at deletion something went wrong and file was left behind. In my case, this behavior was corrected after the upgrade to v10. So we have to analyze which files we can delete at filesystem-level. Veeam Support do not provide such a procedure. 

Userlevel 7
Badge +3

Very interesting. :thumbsup_tone1:

Was there a KB Article published by VEEAM support? I think this will affect many customers...

Userlevel 7
Badge +3

I have checked my repos in the meantime and searched for such files.

Mostly I see files which were not deleted after retention was over with agent backups. I think this a different issue...

Userlevel 7
Badge +4

Very interesting. :thumbsup_tone1:

Was there a KB Article published by VEEAM support? I think this will affect many customers...

Have no info about a KB article. I will ask for. I don’t think it hits many customers. I have not seen any other suffering from this problem.

Userlevel 4

Which exact version of 9.5 caused this issue? Did you delete the orphans manually or did VBR delete them after the update. I assume the first though…

 

The only other reason I might have thought of is some sort of “immutability” function in your repo. I assume we will face things like this with the new V11 XFS repos as the underlying OS will prevent early deletes not in sync with the time-lock.

 

Cheers,

Mike

Userlevel 7
Badge +4

Which exact version of 9.5 caused this issue? Did you delete the orphans manually or did VBR delete them after the update. I assume the first though…

 

The only other reason I might have thought of is some sort of “immutability” function in your repo. I assume we will face things like this with the new V11 XFS repos as the underlying OS will prevent early deletes not in sync with the time-lock.

 

Cheers,

Mike

I don’t know the exact version of VBR that suffered from this bug. I must be a build before U4. The theory of Veeam support was, the bug “survived” update to U4. According to creation-date of orphaned files, just after upgrade to v10 we did not see any new orphaned files.

Yes, you guess right, VBR do not delete these files. We want to deleted them automatically. But I need to do some checks because we are talking about >800 files. 

Comment