I would be interested to hear experiences with replicating to Azure and the general performance. We have had several issues and continue to do so with the speed of replication and virtual standbys.
Issue 1 - Core Service on Azure VM crashing.
Originally we were running a core in Azure using the Rapid Recovery Core Virtual Machine in the Azure Marketplace - https://azuremarketplace.microsoft.com/en-us/marketplace/apps/quest.rapid-recovery-core-vm running Server 2016 OS.
This had 4vCPUs and 32GB of RAM, Azure storage account general purpose v2 (standard & hot tier).
Every week or so the core service would randomly crash, after back and forth with support and numerous log files we never really got to the bottom of it. CPU resource on the VM was around 70% so decided to increase to 8 vCPU and 64GB memory. The crashes became less frequent but were still happening, support still haven't got to the bottom of this issue.
The core versions have also been upgraded to the latest 6.7.
Issue 2 - Replication and Virtual Standby speeds.
While battling with issue 1 the general performance of the core is slow, replication is conducted from on-prem core on server 2019 OS, 16 CPU and 64GB Memory, 200MB internet line. The replication and roll up speeds on the core in Azure fluctuate massively from 100KBs/sec up to 7 MBs/sec. The resource on the source core is fine, there are no issues with high CPU or Memory usage.
One thing I noticed on the Azure storage account was that the success E2E latency on average was 135ms while server latency was 16ms -
So I have started from scratch and built a new core in Azure on Server 2019 with same spec using Azure Blob Premium storage, E2E latency seemed fine for the first few hours and was tracking server latency with a few ms, however it is now averaging 88ms while server latency is 5ms. This leads me to believe it's an application issue, thoughts appreciated.