Skip to main content
Solved

"Failed to delete '...' per retention policy." but the file does not exist

  • August 13, 2024
  • 10 comments
  • 1354 views

  • Not a newbie anymore

Hello, when making a backup copy the following error comes up:

 

Failed to perform post-processing: Agent invoke failed with non retryable error.  

Failed to delete 'vm-1042.281cD2024-08-02T222720_EFBF.vbk' per retention policy     
 

However the backup does not exist in our cloud storage.

The backups from the 7 day retention are present but differently named.

 

Anybody know a solution?

Best answer by Andanet

Try a rescan of your storage and check for errors. 

As wrote Michael please add more info 

10 comments

MicoolPaul
Forum|alt.badge.img+23
  • August 13, 2024

We’ll need more information here. What cloud storage are you using for starters?


Chris.Childerhose
Forum|alt.badge.img+22
  • Veeam Legend, Veeam Vanguard
  • August 13, 2024

As per Michael what Cloud storage, what Veeam version, other details like retention settings, etc.

Please give us more information so we can try to assist.   Also check the logs here - C:\ProgramData\Veeam\Backup


Andanet
Forum|alt.badge.img+13
  • Veeam Legend
  • Answer
  • August 13, 2024

Try a rescan of your storage and check for errors. 

As wrote Michael please add more info 


  • Author
  • Not a newbie anymore
  • August 14, 2024

The rescan seemed to have solved the case. Thank you for the answers!


Chris.Childerhose
Forum|alt.badge.img+22
  • Veeam Legend, Veeam Vanguard
  • August 14, 2024

Great to hear you resolved it with a simple rescan.  👍


Andanet
Forum|alt.badge.img+13
  • Veeam Legend
  • August 17, 2024

Hi @JCLN I'm happy to know the solution was very simple 😁


After upgrading to v12.2 I am having a similar issue as you guys. I will go ahead and re-scan my repository. 


Chris.Childerhose
Forum|alt.badge.img+22
  • Veeam Legend, Veeam Vanguard
  • November 1, 2024

After upgrading to v12.2 I am having a similar issue as you guys. I will go ahead and re-scan my repository. 

Let us know if that solves the issue or if you run in to anything else.


  • Comes here often
  • July 21, 2025

Hi,

I’m experiencing the same issue and have already tried running rscan, but the problem still persists.
Are there any additional steps I should check?

Thanks,
Epul


Chris.Childerhose
Forum|alt.badge.img+22

Hi,

I’m experiencing the same issue and have already tried running rscan, but the problem still persists.
Are there any additional steps I should check?

Thanks,
Epul

Did you follow the solution as per the OP?  Can you post more information as requested?