kkuszek wrote:It sounds less like it's broken as in support and more like it's just broken as designed.)
- Type: REG_DWORD
- Default value: 1 (percent)
- Description: defines the amount of free space reserved on the extents of SOBR, e.g. for merge (% of total extent size).
foggy wrote: data locality policy is not that strict and should place the backup on another extent if it has available space. There's an issue, however, where if there's not enough space to even update metadata file, the job will fail and chances are you're experiencing right this one. I recommend re-opening the case and escalating it to a higher tier for a closer investigation.
so the chances to see it in B&R have vastly improved now
Users browsing this forum: Google [Bot] and 13 guests