MGN uses block-level replication and as such the migrated server is the exact server that is on-premises even from an active directory view. The amount of data that can be pushed across the wire is certainly bound by the available bandwidth. See the guidance at: Windows In-Place Upgrade. Also be sure to check out my blog on the AWS Architecture Site: Avoid affecting your production environment during migration with AWS Application Migration Service for domain-joined Windows specific scenarios with MGN.
- asked 6 months ago
- AWS OFFICIALUpdated 3 months ago
- How can I troubleshoot replication lag or a backlog on my Windows source server for Application Migration Service?AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
- EXPERTpublished 7 months ago
- EXPERTpublished 8 months ago