Hello @lak
Thank you for sharing this question on this community space.
I have read the case scenario stated on your post and I want to get more familiar with so, I got a couple of question, and they are.
- Which Linux Distribution is being used?
- Have you checked the Mobility service version supported for the Linux OS used?
- Is this the Classic or Modernized ASR featured used?
- Is this from on-premises to Azure or Azure to Azure replication task?
- Is this VMware or Hyper-V featured used or which one is?
I was wondering if you have kept in mind the following relevant notes that are down below:
For Linux OS, ensure to provide root credentials and for Windows OS, a user account with admin privileges should be added, these credentials will be used to push install mobility agent on to the source VM during enable replication operation. The credentials can be chosen per VM in the Azure portal during enable replication workflow.
Visit the appliance configurator to edit or add credentials to access your machines
Please ensure that for Linux versions, Azure Site Recovery does not support customized OS images. Only the stock kernels that are part of the distribution minor version release/update are supported
Any change to disk identity is not supported. For example, if the disk partitioning has been changed from GPT to MBR or vice versa, then this will change the disk identity. In such a scenario, the replication will break, and a fresh setup will be required.
For Linux machines, device name change is not supported as it has an impact on the disk identity.
In Modernized, resizing the disk size to reduce it from its original size, is not supported
I hope you can find this useful to overcome your concern.
Looking forward to your feedback,
Cheers,
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.