Slow replication with 12.1.2.172

[Marc.H]

+1 - Having the same issues - will try the workaround posted by Hannes

[Marc.H]

I can confirm after adding the rekey and removing the .ini everything is back to normal speed

[Alex_C9ku]

Good news, looks like QA managed to reproduce performance degradation on incremental runs on a particular ESXi version... they are investigating now.

Is there any news about this issue? It would be interesting to know what in the infrastructure is causing this problem and maybe we can customize our environment to use the improved VMware NBD.

[Gostev]

Basically the same settings that accelerate NBD processing dramatically on the source side (reading data) also slow it down on the target side (writing data). The workaround above (rolling back to the pre-12.1.2 settings) works and in 12.2 replication jobs will automatically use the "old" NBD settings on the target side so you don't have to choose between fast backups and fast replicas

[Gostev]

This should be fixed with 12.2 folks, no need for workarounds any longer. In fact it is best to remove them to get back to "vanilla" deployment as to avoid any surprises in future. Thanks

[masonit]

Basically the same settings that accelerate NBD processing dramatically on the source side (reading data) also slow it down on the target side (writing data). The workaround above (rolling back to the pre-12.1.2 settings) works and in 12.2 replication jobs will automatically use the "old" NBD settings on the target side so you don't have to choose between fast backups and fast replicas

Wouldn't this result in slow restore performance over NBD then?

\M

[Gostev]

No.

[Bejaminlee]

This should be fixed with 12.2 folks, no need for workarounds any longer. In fact it is best to remove them to get back to "vanilla" deployment as to avoid any surprises in future. Thanks

Hang on.

If we need to back these workaround out, can you outline exactly what we need to do please?

I found the workaround was half undone after the update which killed job performance. When I restored the workaround, I got expected performance back.

Are you saying now that if we remove the registry key and restore the INI to its previous location, we will be fine?

[Gostev]

Yes, these changes need to be reverted. I'm guessing config.ini might have already been overwritten for you during the backup proxy update to 12.2 but not sure, just don't be surprised if it was. The registry value definitely requires a manual edit though.

[Bejaminlee]

Alright, I am making these changes and restarting. I will report back