We have a DD2500 with Veeam since 3 years now and we just buy a DD6300 to replicate our DD2500 on our recovery site.
We use one MTREE with 400TB pre-comp and the replication job says that there is 3.9PB of data to replicate and it announce 3 months to replicate it .... (with 2 10GB link). Why 3.9 PB ??
I think our problem is the same that all people have in this post unfortunately
What solution did you find to figure this issue ? Using multiple MTREE instead of big one would be helpful ?
@Gostev : When Veeam will provide a fix for this issue ? For V10 ?
After starting this thread, last year - I finally managed to get our DD replication backlog cleared last month, which had been there since the Veeam 9 upgrade.
At it's maximum, our backlog was over 1PB; however, this is the uncompressed figure, and we found it doesn't reduce in linear steps - but sometimes drops dramatically.
Following the advice on this thread, I created another four Mtree's, and assigned Backup Copy Jobs to those. It had the effect of starting the replication again from the beginning for those jobs, but used 4x the bandwidth as the replication jobs worked in parallel.
It's certainly a workaround rather than a fix, as each job still works through it's backlog slowly, but we usually see a point every week where all Mtree replication jobs are complete. Something unthinkable since Veeam v8.
The good feature of Mtree's that makes this possible, it the fact that you don't have to pre-define or reserve a capacity for them. They all share the same free capacity.