Hello,
Kirill from Object Storage QA team here. I'll try to clarify the mechanism of the Background Checkpoint Removal job.
The session itself is indeed running on the background constantly, but if no Checkpoint Removal tasks are assigned to it, the session is simply idling. You may observe the session log in the Shell Console to find out if any active Checkpoint Removal task in being processed at the moment.
In fact, the mechanism is very similar to the previous approach, when Checkpoint Removal was executed on Backup Job post processing. With the new approach, these tasks are executed after the Backup Job run within the scope of a separate session (Background Checkpoint Removal), allowing backup jobs to finish, effectively distributing the load.
Considering all the above, I can confirm it is safe to service the backup server if no Checkpoint Removal tasks are being executed by the Background Checkpoint Removal job.
Hope that helps!
Kirill from Object Storage QA team here. I'll try to clarify the mechanism of the Background Checkpoint Removal job.
The session itself is indeed running on the background constantly, but if no Checkpoint Removal tasks are assigned to it, the session is simply idling. You may observe the session log in the Shell Console to find out if any active Checkpoint Removal task in being processed at the moment.
In fact, the mechanism is very similar to the previous approach, when Checkpoint Removal was executed on Backup Job post processing. With the new approach, these tasks are executed after the Backup Job run within the scope of a separate session (Background Checkpoint Removal), allowing backup jobs to finish, effectively distributing the load.
Considering all the above, I can confirm it is safe to service the backup server if no Checkpoint Removal tasks are being executed by the Background Checkpoint Removal job.
Hope that helps!
Statistics: Posted by KirillChuxlancev — Sep 11, 2025 11:00 am
