AWS MGN - STEP by STEP - ONPREM to AWS - ENGLISH

AWS MGN - STEP by STEP - ONPREM to AWS - ENGLISH

[@nitinruhela]

Nicely explained. Thanks for sharing this to understand the scenario like how to do that and what are the planning which we need to do carefully. If possible can you please share this csv file for reference. Really Appreciate!!

[@skillupwithstan]

Glad you liked it

[@bashirabdulrahman]

thank you good overview, but we wanted to know the prerequisite requirement on the source server side, specially when the server are hosted online cloud provider and if we are moving from other provider to AWS. we did get issue on connect AWS Replication Agent to Replication Server - stalled, it would be great if anyone can share a good source of video ot doc to refer

[@yairrodriguez475]

can you share the xls?

[@josephemeka]

This is exactly what I am looking for. Please can we get the csv file for reference? Thank you for sharing your knowledge.

[@padmanabhnargunde7945]

very informative demo.... can we also get such applications for trials/ learnings at our end??

[@rajiv7]

do u have aws account?

[@skillupwithstan]

Yes, you just have to create an AWS account to experiment this tool for free

[@pavanjoshi1]

The script that i have is not having the .py extension and it is stalled everytime in mgn console. do we need any specific configuration at aws network or service level?

[@user-tz7st3op8i]

Are you setting up site to site vpn or direct contact or any private link onprimises to cloud communication during migration

[@TuNguyen-gh4lv]

My server has been completed replicating and ready for testing. However, my on-prem server is still adding more data. How can I make sure all the data is synced before the cutover?

[@skillupwithstan]

Cutover generally involves the following phases: Ingestion freeze - Freeze the ingestion of on-premises applications and data into the database. This ensures that the on-premises version of the application doesn’t receive any new transactions or data during the cutover. Backup - Take the final backup of the on-premises system. If necessary, you can use this backup for the rollback in the event of an emergency. Data sync - Complete a final data sync between the on-premises and target (cloud) environments. Routing changes - Route users to the cloud environment (for example, updating DNS records or changing load balancer targets). Testing - Test and validate that everything is working prior to marking the migration as complete.

[@TuNguyen-gh4lv]

@@skillupwithstan Thank you so much. This is super useful

[@manuvenkatesh9032]

Sir, I need full knowledge on this. Please help! I have requested you on WhatsApp

[@skillupwithstan]

Enabled access for migration series..thank you for your interest 👍

[@samtej3130]

@@skillupwithstan how to do this ?