supposing you are using data locality policy, SOBR placement works for the initial plaement of the chain, and following incrementals stay in the same location. So, unless you have new VMs, that's the reason why the new extents are not used. Indeed, manually moving the chains and then rescanning the extents could do the trick.
EMEA Cloud Architect @ Veeam Software
Veeam VMCE #1