Gostev wrote:@Nightbird by design. This is how DDBoost-accelerated transforms are performed (new VBK is synthesized by referencing existing data already on the storage).
Why do a transform as the main .vbk file was already touch (for retention policy ?) as the can see with the file timestamp ?
For transform full weekly, monthly and so on I can understand, but here ??? create a compact.vbk to replace the main .vbk that was touch some minutes ago... time consuming and quite silly, don't you think so ?
This imply that a simple merge full for rentention policy (first .vib merge in the .vbk) is slower to make with ddboost that with cifs... missing something !