Maintaining On-Prem Virtual Machine Drive Letters For Virtual Machines Protected by ASR :-
Case Scenario :-
- We are having an On-Prem Virtual machine with a Disk Drive D in which all the applications has been installed.
- Now this Virtual machine is also protected by ASR in order to failover this VM to Azure.
- With a condition that the Drive Letter should remain the same.
Below is the schema to understand it better
Issues Can Occur :-
- Generally when you failover an On-Prem Virtual machine to Azure by default a temporary storage gets added to the Virtual machine and that's get named as Drive D.
- The other free disk drive E will be named for the On-Prem drive containing all the applications as soon as you start your Azure Virtual machine.
- Now this creates a huge problem for the applications to performed efficiently.
Resolution Approach :-
- Now to fix this kind of issue we need to forcefully append the temporary storage at the end. So we need to log in to the Guest Virtual machine ( Not the Host Server ) & go to the Command prompt.
- Check the diskpart
- If SAN = offline shared / offlineall --- This indicates that the disk of the Guest Virtual machines is not maintained.
- So you need to bring those disks online ,initialize those disks properly & then set San Policy = onlineall
- This particular disk update is only for the Local Running machine. So we need to make sure that this changes should always get updated in ASR as latest Recovery point.
- Also Make sure to do Test Failover of those server before actual failover.