Job id folders

[lowlander]

When pointing multiple jobs to a SOBR, jobids will be created as the corresponding backup job. What is the impact when we delete only the jobid folder Via the object storage interface instead of the veeam interface ?

Will the capacity tier be updated correctly with a rescan ?

[lowlander]

To explain further

We use the SOBR where the performance tier is copied to the capacity tier. In the capacity tier we use object storage that uses the well known structure described in the helpcenter : https://helpcenter.veeam.com/docs/backu ... ml?ver=110

So basically we point multiple jobs to the SOBR and after the copy to capacity tier there are several folders created in the bucket structure. So that are basically the <backup_id> folders.

To rephrase the question what is the impact when one of the <backup_id> folders is being deleted via the awscli or object storage management interface, and can this be repaired within the VBR configuration when this happens ?

[veremin]

What type of repairment you expect? Backup server finding missing job folder in the object storage repository and rebuilding it from the scratch during the next offload window?

[veremin]

Got a verificaion from the QA team: if you remove a job folder from the object storage, you need to rescan SOBR afterwards or remove the job backup from the configuration. After that everything should work smoothly and new offload cycle should catch up and rebuild removed objects. Thanks!