Skip to main content
Question

Background checkpoint removal. Backup server:

  • March 31, 2026
  • 4 comments
  • 25 views

Hi,

Over the past week, the checkpoint removal process has been completing with warnings. I receive notifications 2–3 times, and then it returns to normal and completes successfully without warnings.

However, for the past 4 days, I’ve been receiving the same warnings again. I’ve checked everything, and everything seems normal. When I review the statistics, there’s no clear reason for these warnings.

Could someone help me understand what might be causing this issue?

Thank you in advance.

4 comments

Andanet
Forum|alt.badge.img+12
  • Veeam Legend
  • March 31, 2026

Hi ​@Yaphet welcome in our Community. 

Please can you share more info about warnings and somethings about your backup infrastructure (Hypervisor, VBR Server, repository etc)? 
Thanks


coolsport00
Forum|alt.badge.img+21
  • Veeam Legend
  • March 31, 2026

Hi ​@Yaphet ...agree with Antonio. We need more info about your environment, job(s), etc. to try and help.

At the very least, you can look in your VBR logs in:
C:\ProgramData\Veeam\Backup\<job-name.log> to see if it shows anything more definitive. And, of course...you can always open a case with Veeam Support to get you sorted as well.

Best.


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

If you are using immutable repositories check the immutability period on this and then the retention in your job as that has to be +1 at least more for the number of days for the checkpoint removal to work correctly.  I saw this somewhere in documentation and made the change myself which seems to have fixed this.


Forum|alt.badge.img+3
  • Experienced User
  • April 1, 2026

Open a Support Case and let Veeam Support review the debug logs. (Use the 3rd radio option to export from the Backup Server itself)

 

Background checkpoint removal job is best thought of as a clean-up job for object storage. It can error / warn for too many reasons to list, but that it seems to come back clean on later runs leads me to think that the job encountered errors from the S3 server during cleanup, possibly due to it being busy but that is just a guess.

 

That it completes fine later means likely everything is fine as the checkpoint removal job is smart enough to clean up from failed runs, but it’s worth checking the logs to understand what produced the warnings / errors.