Category: microsoft azure site recovery
shrav666 on Tue, 29 Oct 2019 14:00:22
Is anyone here to help me out with my issue?
(1)I have performed test failover (using Azure site recovery) yesterday and done RDP successfully. Everything went fine.
But today, when I did actual Failover of VM, I cannot do RDP. I get the below error while connecting to RDP:
Remote access is enabled via NSG, I see the remote computer on and running fine, but bit doubt on the network on which the VM is available as I see the below network symbol in the boot diagnosis image. How to solve this issue?
(2)I tried changing recovery point, but it failed. now I cannot do commit or fail back. Badly stuck in worst situation. Didn't expect this situation with Azure live failover. All the options are faded. Please suggest what can be done here???
Shane W on Tue, 29 Oct 2019 15:43:15
When you did the test failover, was it to the same vnet/subnet as the live failover?
shrav666 on Tue, 29 Oct 2019 15:45:42
In that, it was mentioned to perform commands to stop-AzureRMVM and start-AzureRMVM so that network issue can be solved. I have first run stop command, it completed within a minute. But when ran start command it is taking hell long time. The solution i found in that article resulted in the below error:start-AzureRmVM : Long running operation failed with status 'Unauthorized'.
ErrorMessage: The access token expiry UTC time '10/29/2019 3:33:55 PM' is earlier than current UTC time '10/29/2019 3:34:01 PM'.
At line:1 char:1
+ start-AzureRmVM -ResourceGroupName "RG" -Name "VM1"
+ CategoryInfo : CloseError: (:) [Start-AzVM], ComputeCloudException
+ FullyQualifiedErrorId : Microsoft.Azure.Commands.Compute.StartAzureVMCommand
Also strange thing found is when saw the status of VM on portal it is showing as running, but when used powershell to get the status of VM, provisining state as updating
Do anyone can share a solution?
Shane W on Tue, 29 Oct 2019 15:47:29
Have you tried to redeploy the VM to a new host?
shrav666 on Tue, 29 Oct 2019 17:02:28
As mentioned in my above post, i did the test failover yesterday. Yes it is to teh same vnet/subnet as the live failover.
Everything went well in my test failover.
shrav666 on Tue, 29 Oct 2019 17:03:31
I just clicked on redeploy option present in the VM blade. I did redeploy too, still the same issue.
Shane W on Tue, 29 Oct 2019 17:06:45
I understand you did a test failover yesterday i have not questioned this.
Have you tried to redeploy the VM that you cant connect to?
shrav666 on Tue, 29 Oct 2019 17:24:18
Thanks for your prompt reply. Yes I have done Redeploy of the VM. no change after that, still the same.
shrav666 on Wed, 30 Oct 2019 03:47:02
Please help me in providing solution
Anwesh Patukuri on Wed, 30 Oct 2019 06:56:21
It looks like a problem with the network interface can you add additional nic to the vm and remove the existing one and see if you are able to connect ?? Also just check the ip configuration of the vm from the run command (portal) or from serial console of the vm.
shrav666 on Wed, 30 Oct 2019 13:44:38
Yes, I guess the same. It is something issue with network. But fortunately, the RDP is working fine today and the everything looks good. RDP issue is solved automatically but we are left with 2nd issue.
(2)I tried changing recovery point, but it failed. Tried it many times to change the recovery point still the same error. All the options are greyed out. Now I cannot do commit or fail back. .