Questions tagged with AWS Application Migration Service
Content language: English
Sort by most recent
Hello,
Setting up AMS with agentless discovery and replication onprem using vCenter 7.x works fine for the initial snapshot creation and replication but subsequently fails on any further snapshot creation/updates on the VM so the virtual machine shows as "stalled" in the AMS console. Checking all requirements, and the fact that it works initially, I am unable to decipher as to why subsequent snapshots are failing and there isn't much documentation on troubleshooting this so I was curious if someone had hit this before and might have some guidance?
Environment:
- vCenter 7.x
- Windows 2019 VM and Ubuntu 20 VM in testing - both show "stalled" after successful initial replication
- MGN client plugin 1.1.6
Thanks for any help!
Hi, I've ran MGN and recently disconnected the Data replication status. and now it's marked as archived. But is there any way to delete this archive? becasue I'm concerned that it may charge me extra fees if it's still in archive. Recourses related to MGN are all deleted such as EC2. Only MGN archive is still remaining.
I am unable to reach a windows ec2 instance after a migration using aws migration services. I have added an elastic IP and made sure the security group allows RDP connections. I have rebooted and stopped/restarted. I have checked all available logs I can find. I am able to take a screenshot and it looks like the correct server except the network icon has a red X over it and that is the only detail I can find that may provide any further insight. Please let me know if there is anywhere else I can check or any other troubleshooting steps I can perform. Thank you.
Instance:
i-0e01c4155e0a6fcb9
located in us-east-2
Can someone explain why I get this error and where I can look to correct it?
The "How can I solve this?" takes you to general troubleshooting and none of the troubleshooting topics have this error.
The source server .log file looks good until AwsReplicationVolumeUpdaterService. Looks like this service fails 5 times, then the process stops.
Here is an excerpt from the log:
exit_code: 1053, exception: None]
2022-08-09 07:16:13,008 DEBUG running command [agent_version: 1.5.20, installation_id: 0123456789, mac_addresses: xyz,xyz, _origin_client_type: installer, account_id: abc, _origin_instance_id: xyz, _origin_source_server_id: s-1234567890, command: sc, args: ['start', 'AwsReplicationVolumeUpdaterService'], full_message: ['sc', 'start', 'AwsReplicationVolumeUpdaterService']]
2022-08-09 07:16:43,263 ERROR command failed [agent_version: 1.5.20, installation_id: 0123456789, mac_addresses: xyz,xyz, _origin_client_type: installer, account_id: abc, _origin_instance_id: xyz, _origin_source_server_id: s-1234567890, command: sc, args: ['start', 'AwsReplicationVolumeUpdaterService'], full_message: ['sc', 'start', 'AwsReplicationVolumeUpdaterService'], stdout: [SC] StartService FAILED 1053:
The service did not respond to the start or control request in a timely fashion.
, exit_code: 1053, exception: None]
2022-08-09 07:16:53,266 DEBUG running command [agent_version: 1.5.20, installation_id: 0123456789, mac_addresses: xyz,xyz, _origin_client_type: installer, account_id: abc, _origin_instance_id: xyz, _origin_source_server_id: s-1234567890, command: sc, args: ['start', 'AwsReplicationVolumeUpdaterService'], full_message: ['sc', 'start', 'AwsReplicationVolumeUpdaterService']]
2022-08-09 07:17:19,873 DEBUG command finished [agent_version: 1.5.20, installation_id: 0123456789, mac_addresses: xyz,xyz, _origin_client_type: installer, account_id: abc, _origin_instance_id: xyz, _origin_source_server_id: s-1234567890, command: sc, args: ['start', 'AwsReplicationVolumeUpdaterService'], full_message: ['sc', 'start', 'AwsReplicationVolumeUpdaterService'], stdout: SERVICE_NAME: AwsReplicationVolumeUpdaterService TYPE : 10 WIN32_OWN_PROCESS
STATE : 2 START_PENDING (NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN) WIN32_EXIT_CODE : 0 (0x0) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x7d0 PID : 5564 FLAGS : , exit_code: 0]
Service successfully installed on source. "How to solve this?" does not appear to have anything relevant on this particular error.
Why am I getting this error in AWS and how do I solve it?
It keeps returning "failed to validate AWS credentials" when running the python installer script on my Ubuntu Linux.
I have allowed 443 and 1500 through the router and in ufw.
I have tested my AWS creds.
Hello everyone!
AWS MGN states on the documentation that it doesn't support 'paravirtualized source servers'. Is it pertaining to servers using paravirtualized NIC and PVSCSI controllers?
Reference: docs.aws.amazon.com/mgn/latest/ug/installation-requiremets.html
Thank you!
Hi, I have migrated a Redhat 7.2 linux machine that was previosly working on a VMWARE Host. I did that migration running the Application Migration Service Agent inside the linux machine, and although I was able to start the migrated EC2 instance on AWS, it did not started correctly. It seems the error may be related with the network interface, since when I do a config, I do not see a "eth0" device setup, I instead see a "virbr0" device, that seems to be a "bridge" or "virtualized" card. My suspect is that, since the Redhat 7.2 was running previously on a vmware, it had virtualized cards insted a normal eth0, and that virtualized card may be something specific of vmware that was not recognized by the Application Migration Service Agent when the migration was done. Is there any suggested why to use AMS (Application Migration Service) on such as environments ? How I can fix now that machine so the network is working ? Not sure if I can add now an "eth0" card to the actual EC2, or if I should delete the "virbr0" device and how--
Dear Experts,
We have windows file server in Data Center with approximately 3.5 TB of Data allocated in 4 disks in DC. Windows file server is on server 2012 in Data center. We are doing migration of this file server to AWS using AWS Migration Services(MGN). Business user is not ready to use Windows FSX as the option here therefore we migrating the file server. After migration, the server will be upgraded to 2019 and then the cutover will be done. Do you forsee any issue with migration with such a large amount of data? For replication disks we are using gp3 disk and replication is happening over the internet so replication process is quite slow. However, the query is that after the replication, do you forsee any issue with upgrade and cutover of the instance? Business is expecting to have all file shares permissions should be replicated to the target.
Thanks
I am working on building a design for an enterprise and looking for input.
**Use Case Scenario:**
An organization running the system uses a LAMP stack in On-Prem data center. They are building a new service using similar technologies, expected to have rapid growth in traffic in the next 1 to 3 months.
Organization wanted to have system address the following
• scalability
• self-healing infrastructure
• Lack of a DR capability.
• High availability, and is low cost.
• Security of data at rest and in transit.
Need to consider the data migration from onprem
**Objective **to Migrate to a new AWS platform while delivering business value along the way
Build a scalable, elastic and redundant architecture that allows application to organically scale with the increase of its use.
**Solution Options:**
System Design#1
And
System Design#2
Please review if services has been used wisely and provide your comments.
We are migrating from VirtualBox(6.1) virtualization to AWS for MGN testing.
The source server is Centos 6.8.
By installing a replication agent on the source server, it went smoothly with 'ready for testing' status.
However, after the 'launch test instance' action, the test instance created in the 'Test in progress' phase does not operate normally.
Status in Lifecycle is as follows.
- Launch status
Launched
First boot: Stopped
- Last test : Completed (Check through Job Id link)
Data replication status is as follows.
- Healthy
- Replication pregress : Initial replication finished
In the instance menu, the test instance status is running, but the status check is 'initialized' for more than 30 minutes, and the instance status check fails. (System status check is successful.)
Nevertheless, when I look at the instance screenshots, the prompts on the console screen look fine.
After allowing ssh and ping to the security group, ping and ssh connection are attempted from the bastion host, but it fails.
I don't even know if the replication of the whole instance is the problem, or just a part of the instance (eg the network) is the problem.
If you have a similar experience on MGN, please give me a hint.
Thank you.
Hello, I'm using MGN to migrate a Windows 2016 64 bit with 2 disks (each ~232 GB). The migration dashboard shows that the initial replication finished and that it's "ready for testing." However, when I try to launch a test instance, the conversion starts, but fails a few minutes later. The job log (under Launch history > Job:mgnjob...) doesn't provide a lot of context, the only feedback is "Conversion failed". I've tried launching test instances multiple times, all with the same result. In an attempt to get a little bit more data as to what's going on, I can view the system log for the converter instance as the conversion is progressing. I've included relevant snippets of the system log below. I'd appreciate any recommendations anyone can offer in terms of next steps for troubleshooting why the conversion is failing.
Included below are some snippets of the system log.
Start of the log:
------------------------------------------------------------------------------------------------
2022/06/21 17:17:34Z: Windows sysprep configuration complete.
2022/06/21 17:17:36Z: Message: Waiting for meta-data accessibility...
2022/06/21 17:17:36Z: Message: Meta-data is now available.
2022/06/21 17:17:38Z: AMI Origin Version: 2022.06.15
2022/06/21 17:17:38Z: AMI Origin Name: Windows_Server-2016-English-Full-Base
2022/06/21 17:17:38Z: OS: Microsoft Windows NT 10.0
2022/06/21 17:17:38Z: OsProductName: Windows Server 2016 Datacenter
2022/06/21 17:17:38Z: OsInstallOption: Full
2022/06/21 17:17:38Z: OsVersion: 10.0
2022/06/21 17:17:38Z: OsBuildLabEx: 14393.5192.amd64fre.rs1_release.220610-1622
2022/06/21 17:17:38Z: OsCurrentBuild: 14393
2022/06/21 17:17:38Z: OsReleaseId: 1607
2022/06/21 17:17:38Z: Language: en-US
2022/06/21 17:17:38Z: TimeZone: Coordinated Universal Time
2022/06/21 17:17:38Z: Offset: UTC 00:00:00
2022/06/21 17:17:38Z: AMI-ID:
2022/06/21 17:17:38Z: Instance-ID:
2022/06/21 17:17:38Z: Instance Type: m4.large
2022/06/21 17:17:56Z: Driver: AWS PV Driver Package v8.4.2
2022/06/21 17:17:56Z: Driver: Intel(R) 82599 Virtual Function v2.1.186.0
2022/06/21 17:17:57Z: Launch: EC2 Launch v1.3.2003639
2022/06/21 17:17:57Z: SSM: Amazon SSM Agent v3.1.1188.0
2022/06/21 17:17:57Z: RDPCERTIFICATE-SUBJECTNAME:
2022/06/21 17:17:57Z: RDPCERTIFICATE-THUMBPRINT:
2022/06/21 17:18:10Z: HibernationEnabled: false
2022/06/21 17:18:14Z: Message: Windows is Ready to use
2022/06/21 17:18:15Z: EC2LaunchTelemetry: IsTelemetryEnabled=true
2022/06/21 17:18:15Z: EC2LaunchTelemetry: IsAgentScheduledPerBoot=false
2022/06/21 17:18:15Z: EC2LaunchTelemetry: IsUserDataScheduledPerBoot=true
2022/06/21 17:18:15Z: EC2LaunchTelemetry: AgentCommandErrorCode=1
2022/06/21 17:18:56Z: MGN script started
2022/06/21 17:19:26Z: 2022/06/21 17:18:55Z: ACPI SPCR table not found. Bailing Out
2022/06/21 17:19:26Z: 2022/06/21 17:18:55Z: Opening port (COM1) handle to write to the console
2022/06/21 17:19:26Z: 2022/06/21 17:18:56Z: MGN script started
2022/06/21 17:19:26Z: Directory: C:\
2022/06/21 17:19:26Z: Mode LastWriteTime Length Name
2022/06/21 17:19:26Z: ---- ------------- ------ ----
2022/06/21 17:19:26Z: d----- 6/21/2022 5:18 PM CloudEndure
------------------------------------------------------------------------------------------------
Following that are some HTTP get requests that I will exclude since I believe the query parameters may include some sensitive information.
Next a series of "getting next command with token" in the log:
------------------------------------------------------------------------------------------------
Starting running http commands.
run_commands started
client_config threads have spawned
getting next command with token 3a44cf0cb475650494ed7aa694017179
command received
getting next command with token 142f6916cb537e313e48eb1c9c6e92f7
command received
------------------------------------------------------------------------------------------------
The last part of the log before the conversion fails is interesting. It references two services: UmRdpService and TermService. These are the Windows services for "Remote Desktop Service" and "Remote Desktop Services UserMode Port Redirector." So it *appears* that the conversion process has some issues with these two services, but that's as much as I've been able to glean.
------------------------------------------------------------------------------------------------
Failed running all commands : None
2022/06/21 17:22:03Z: http_commands_client.exe returned:
SERVICE_NAME: UmRdpService
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 3 STOP_PENDING
(NOT_STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x116
WAIT_HINT : 0x0
SERVICE_NAME: TermService
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 3 STOP_PENDING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x1
WAIT_HINT : 0xea60
2022/06/21 17:22:03Z: MGN script finished
------------------------------------------------------------------------------------------------