Sharing the solution for the benefit of broader community.
Issue: Proxy was configured within the VM and that was causing a disconnect with cachestorgeaccount.
This was identified by Azure technical support team and the issue got fixed.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have 2 VM's and both are linux VM's. I see that the replication health within the disaster recovery tab within the VM itself shows as Critical .
When i started to check the events i saw that it was throwing 153017 event where it said that the machine was not able to upload the replication logs to the cachestorage account for the disk and possible reasons would be : The cachestorageaccount would have been deleted or the container used to storage replication logs would have been deleted . A firewall might be blocking access to this storage account from VM .
I also found that the agent version asked for an upgrade and the agent status was Critical . I basically went ahead and upgraded the agent version and now they are health .
Now still the replication health is Critical . And i see the below event :
Event name as Storage network access denied . Event id 152019
Replication is not progressing as the source/cache storage account 'xyz' is not accessible for disk 'myVM_OsDisk_1_erthyu'.
Possible causes
Access to the source/cache storage account may be blocked due to firewall settings on the source/cache storage account.
Recommendation
Disable firewall rules on the source/cache storage account to allow replication to progress.
I have looked went throw the Cachestorage account and under networking i see that it is enabled for all the networks. And even "Exception checkbox allow trusted Microsoft services to access storage storage being checked "
Any thoughts where can be the problem ? Should we restart the VM to resynchronize and if i am not resynchronize will not send the complete data over the secondary site , it will just send the checksums and Compair . And then changes will replicate . But why this is not working at first place .
Sharing the solution for the benefit of broader community.
Issue: Proxy was configured within the VM and that was causing a disconnect with cachestorgeaccount.
This was identified by Azure technical support team and the issue got fixed.
@Rajesh S .. Can you check if you have a proxy on the linux machine using the command
echo $http_proxy .. If yes just remove that and test .