Hello @blackshelbygt500kr! Thank you for your comment. In a failover scenario, the subnet in Azure may or may not change depending on how the environment is set up. Generally, during failover, the same subnet is replicated in the Azure environment to ensure a smooth transition and minimize disruptions. However, specific configurations and requirements might vary based on the organization's needs. It's always a good practice to consult the Azure documentation or reach out to technical experts for a more detailed understanding of your specific setup. Hope this clarifies things for you!
Hello @charithareddy33, Thank you for your comment. The process in question could potentially be considered a lift and shift, depending on the specific details and context of the migration or transformation being discussed. In a lift and shift approach, applications or systems are moved from one environment to another with minimal changes to the underlying code or architecture. If this process aligns with that definition, then yes, it could be categorized as a lift and shift. If you have any further questions or would like more information, please feel free to ask. Thank you. Paddymaddy
Complete demo ASR for Azure Hyper-V
Paddy Maddy....Great Job....Crystal Clear step by step process makes easy to understand ASR for Hyper-V
very nice sir this help me a lot
Glad to hear that
This was a great tutorial. Would love to see an Azure to on-premises failback video
Are you duplicating the exact same on prem subnet to the Azure environment? Or does the subnet change when a failover happens?
Hello @blackshelbygt500kr! Thank you for your comment. In a failover scenario, the subnet in Azure may or may not change depending on how the environment is set up. Generally, during failover, the same subnet is replicated in the Azure environment to ensure a smooth transition and minimize disruptions. However, specific configurations and requirements might vary based on the organization's needs. It's always a good practice to consult the Azure documentation or reach out to technical experts for a more detailed understanding of your specific setup. Hope this clarifies things for you!
Very nice ....
Please tell me, can we consider this process as lift and shift
Yes you can
Hello @charithareddy33,
Thank you for your comment. The process in question could potentially be considered a lift and shift, depending on the specific details and context of the migration or transformation being discussed. In a lift and shift approach, applications or systems are moved from one environment to another with minimal changes to the underlying code or architecture. If this process aligns with that definition, then yes, it could be categorized as a lift and shift.
If you have any further questions or would like more information, please feel free to ask.
Thank you.
Paddymaddy
what is advantage for join option can you explain